docs(specs): console PRD — the strategy console (O11) - #400
Merged
Conversation
Operator additions: run simulations from the console with full results display (verdict, gates, DCA benchmark, tier matrix); the tried-vs-used ledger answering 'which strategies are in use, which were tried, and WHY are the tried ones not used' — every rule with its lifecycle status and the machine's recorded reason (the specific failing promotion floor, insights distance, disabled/demoted context), sourced from the engine's own verdicts; add-a-strategy with parameter help at each field; and retry (re-backtest + re-promote, --force typed; rules enable as the documented restore path). C4 (#390) owns it; menu tree updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operator additions to the console PRD, owned by C4 (#390): O11 — the strategy console: (1) simulations run from the console with results displayed (GO-LIVE/TRAIN-MORE verdict, gates, DCA benchmark, tier matrix; report linked from the Research readers); (2) the tried-vs-used ledger — every strategy with its lifecycle status AND the machine's recorded reason it isn't in use (failing promotion floor, insights distance, disabled/demoted context); (3) add-a-strategy in-console with parameter help at each field; (4) retry — re-backtest + re-promote (
--forcetyped) andrules enableas the restore path. All through the C1 services. Docs-only. Refs #390.