Config area of the server: venue profiles, known gaps, model kinds (#175)
docs: correct monorepo installation and deployment paths Document workspace-aware Git installs, component environments and the main protocol baseline. Remove separate-GUI and root-container paths. Co-Authored-By: pi <pi@opencode.ai>
docs: describe the monorepo layout The protocol is a folder of this repository, not a submodule of it, and the backend is one component beside it. Co-Authored-By: pi <pi@opencode.ai>
Server: the container image and its compose deployment (#177) No reverse proxy is shipped; TLS is the operator's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run, Architecture, Decisions, C4 model, Quality, Glossary, Library: runs fork from a forkserver (#178)
Architecture, CLI, C4 model, Quality, Glossary: the server's results area (#172)
Architecture, Library, CLI, Quality, Glossary, C4 model: the server and its connections (#171)
Check the protocol submodule out as sbt2-protocol/
Generate the protocol's code offline with locked tools (#183)
Architecture, Quality, Glossary: the protocol moves to its own repo, sbt2-protocol, pinned as the proto/ submodule (#179)
Name the protocol package sbt2.protocol.v1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Protocol: the .proto package, buf checks and Python codegen (#170)
Config folder: --config/SBT2_CONFIG, venue profiles out of the package (#151)
Results: subpackages of sbt2.core.results and their layers (#162)
Data root: required --data or SBT2_DATA, known gaps in known_gaps.toml (#152) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run, CLI: launch runs uncapped by default, with the systemd scope opt-in (#153)
docs: describe the uv workspace and the sbt2 namespace packages (#145) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Benchmarks: variants, factory, buy-and-hold convention, nautilus statistics; type-only imports
M4 scope: nautilus sizing and RiskEngine, one drawdown guard in the base's order gate Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop provenance, code identity, result identity and the data fingerprint
docs: sources live in data; the catalog is a reader and writer package (#52) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Splits: train / validation / test, with only test locked The optimiser tunes on train and ranks on validation; validation runs as often as you like; the lock becomes the test lock. Walk-forward is deferred until M10. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Library: settle the open questions and bring every page in line Two parts (in-sample / out-of-sample) replace train / validation / test; Holdout by fraction or date, no embargo; only the final out-of-sample part is locked, per lineage by date overlap; every run stored; code identity replaces the git SHA; one root replaces data/ and config/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Library: target design for sbt2 as a published package, open questions Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: thin nautilus strategy base; asset profiles keyed by nautilus Strategies are nautilus Strategy subclasses on a thin sbt2 base that submit their own orders; the plain-Python pipeline (intents, reconciler, adapter) is gone (PR #18). Asset profiles are keyed by nautilus's AssetClass + InstrumentClass and venue profiles name them with nautilus enum names (issue #19). Results notes that annualization must be passed as nautilus's period (default 252) and that benchmark-relative stats come from nautilus. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move to nautilus v2: native funding, portfolio equity snapshots, run-time bars, public catalog writers, nautilus tearsheets Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop the ingest manifest: coverage, instrument types and fingerprints come from nautilus's catalog Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Index as a DuckDB view over per-run summaries; drop the pre-flight memory estimate Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop results staging: runs write straight to their folder, a failed run crashes the program Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop lockbox and access log, keep strategies in this repo, remove host OS from deployment Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>