This is a written answer, not code.
algosystem is detached from the rest of the platform: nothing in the organisation imports it, and it imports nothing of ours. I want it to become the Python analytics tool people run on trade-ngin's results (the next issues here). Before that, I need to know where it stands.
Questions, each answered in writing on this issue
| # |
question |
what I know |
what I need |
| 1 |
Who uses it today, and for what? |
pull requests #32 and #33 (September 2026) show two people working on it; no repository in the organisation imports it |
names and uses, including any use outside GitHub |
| 2 |
Which copy is canonical: this repository, or libs/algosystem in AlgoGators/algogators? |
this main is d929556f (2026-08-14); the monorepo copy was last touched 2026-08-15; 48 files differ, mostly typing changes; the standalone has the CI and the import-linter contract |
one answer, and the other copy frozen with a note saying so. My starting position: this repository is canonical until the monorepo import |
| 3 |
Does anything in algosystem read equities_data.sharadar_ohlcv_1d or the adj_* columns of equities_data.ohlcv_1d? |
the code uses yfinance and its own schema; the data team is waiting on a written answer before dropping the first (AlgoGators/data-ngin#112 item 17) and repairing the second (AlgoGators/data-ngin#107) |
yes or no for each, for the code and for any script off the repository |
| 4 |
The backtest schema. #4 and pull request #32 rename it to research. The plan for the monorepo removes algosystem's own schema and db commands, because the engine's database is the record |
both collide by table name with trade-ngin's backtest.* and differ in columns |
who needs the private store, and for what. Until this is ruled, #4's interim rule stands: never run db init or create_all against new_algo_data. Pull request #32 waits |
| 5 |
Licence |
none: no LICENSE file, no licence field in pyproject.toml |
a proposal; I rule |
| 6 |
Release |
PyPI has 0.1.9 from 2026-01-17, which predates the restructure and the whole validation package; #6 (Trusted Publisher) is open |
what a release needs, in order |
| 7 |
CI |
the weekly OSSF Scorecard run on main fails; pull request #33's tests fail on Python 3.10 |
cause and fix for each |
| 8 |
Model-drift monitoring (#5) |
deferred; AlgoGators/trade-ngin#50 is its pair and #5's own comment says #50 can be closed |
whether #5 stays here |
Done when
Each row has a written answer on this issue and I have ruled on rows 2, 4 and 5.
This is a written answer, not code.
algosystem is detached from the rest of the platform: nothing in the organisation imports it, and it imports nothing of ours. I want it to become the Python analytics tool people run on trade-ngin's results (the next issues here). Before that, I need to know where it stands.
Questions, each answered in writing on this issue
libs/algosystemin AlgoGators/algogators?mainisd929556f(2026-08-14); the monorepo copy was last touched 2026-08-15; 48 files differ, mostly typing changes; the standalone has the CI and the import-linter contractequities_data.sharadar_ohlcv_1dor theadj_*columns ofequities_data.ohlcv_1d?backtestschema. #4 and pull request #32 rename it toresearch. The plan for the monorepo removes algosystem's own schema anddbcommands, because the engine's database is the recordbacktest.*and differ in columnsdb initorcreate_allagainstnew_algo_data. Pull request #32 waitspyproject.tomlmainfails; pull request #33's tests fail on Python 3.10Done when
Each row has a written answer on this issue and I have ruled on rows 2, 4 and 5.