docs: plan domain-core - #4
Merged
Merged
Conversation
3 tasks
5 tasks
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.
Plan tree for E1 — Domain core (first epic of the rewrite). Lands the durable
plan on
developbefore any code, so each leaf branch inherits it.Goal
Build
trading_bot/domain/— the pure, zero-I/O, mypy-strict vocabulary everyother layer speaks: exact-Decimal money, venue-neutral instruments, the
Orderaggregate + lifecycle state machine, broker-confirmed
Fills,Positionfromfills, the strategy
Signal, pure PnL/KPI, and the error hierarchy. The legacytree is mined for domain knowledge, not copied.
Leaves
After merge:
/execute-leaf domain-core nextruns leaf 01.