Issue states were reviewed on 29 October 2026. The linked issue records the exact delivered, deferred, or retired scope. Closed research trackers can contain bounded implementations and explicit exclusions; their disposition remains part of the contract.
Delivered research capabilities have current contracts
The Python project and Compiled project exercise separately authored research definitions over recorded observations. The book develops their decisions, and Reference supplies exact API and configuration contracts.
| Capability | Delivered source scope | Contract and disposition |
|---|---|---|
| Research interfaces | Caller-owned Python methodology and YAML/CLI Compiled Research | Research book, interface contract |
| Features and market state | Native indicators, feature families, validated parameters, and a stateful seven-label regime classifier | Feature design, #504, #252, #346 |
| Model families | Binary, sequence, regression, quantile, linked-learning, and rule architectures with model-specific restrictions | Model choice, #297, #369 |
| TabPFN controls | Supported classifier parameters and separately retained real-checkpoint execution | Optional model campaign, #444, #628 |
| Perturbation | Population, feature, representation, target, and model axes | Robustness research, #341 |
| Search and feedback | Grid, random, Sobol, mutable queues, five reducers, and correlation/forest analysis | Search, feedback, #343, #344 |
| Linked learning | Bounded residual, feature, weight, pseudo-label, and direction/sizing mechanisms | Linked models, #342 |
| Captured state and failure policy | Trusted .uel snapshots and restricted budgeted serial candidate-error recording |
Run and recover, #224, #602 |
| Analysis tables | Polars result tables with explicit correlation grouping columns | Log, #643 |
| Execution interpretation | Snapshot/event policies, explicit multiclass/multilabel mapping, independent exits, funding, and observed-cost comparisons | Trading behavior, #490 |
| Chronological assessment | Walk-forward fits, retained return tracks, advisory DSR/PBO, and experiment-family reports | Walk-forward, research evidence |
| Selected behavior | Python fitted-state adapters, native reconstruction, compatible Cohorts, and Bayesian Python voting | Selected behavior |
| Protected research | Reservation-bound exclusion, supported workflow composition, frozen selection, and restricted final assessment | Final holdout, workflow compatibility |
| Configuration integrity | Exact schema version, structural and callable validation, parameter consumption, and source-bound artifacts | Manifest, #632 |
| Tradeline scope | Recorded disposition of multiclass and directional-conditional research requests | #605 |
Remaining work follows its recorded authority
| Priority | Remaining work | Authority |
|---|---|---|
| Research integrity | Statistical acceptance policy beyond the current advisory reports | A new issue or PRD must define the additional scientific claim and its evidence. |
| Platform trust | Release provenance and supply-chain audit follow-up | #626 |
| Test authority | Required-gate and test-authority audit follow-up | #625 |
| Audit disposition | Remaining findings in the master register | #693 |
| Dependency maintenance | Retype the Arrow facade seam when the pinned dependency passes version 23 | #681, following #680 |
| Verification methods | Further parser and frame-contract property testing or fuzzing | Additional scope requires a filed issue or PRD; existing checks remain in force. |
An open tracker identifies work requiring disposition. Its presence does not make every listed historical finding an unimplemented product capability. Delivery follows the repository's issue, review, test, and release requirements.
Product boundaries assign downstream responsibility
Limen researches Bitcoin models and strategies through Python functions and YAML/CLI definitions. Origo owns upstream source-of-truth market-data infrastructure. Nexus and Praxis own downstream operational decisions and venue orders. The execution reference specifies the research accounting supported inside Limen.
The documentation reader and prose editor support the book's reading and contribution workflows. Their deployments have separate evidence and activation requirements, described in Edit and verify the book.
Historical Explorer, Rust, transformer, and experimental parallel branches retain their own revision and development status. Current behavior belongs in the book only when it exists in the released source and has its stated execution evidence.
Roadmap changes preserve delivered meaning
Roadmap review accompanies a new PRD or a material delivery and occurs at least quarterly. A completed item moves to its delivered contract with the exact disposition retained. New intent identifies its issue, prerequisite, and evidence requirement before it becomes a delivery commitment.
The docs hub provides the reading sequence. Developer home provides contribution and release procedures.