Prototype: declarative PostWriteReconcilePlan - #189
Draft
kyleve wants to merge 1 commit into
Draft
Conversation
Derive post-write fan-out steps from PostWriteOutcome and execute them sequentially in DayJournal. Exploratory follow-on to #184. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Prototype (draft) — stacked on #184
Exploratory follow-on to TLA+ protocol expansion for Where. Not merge-ready — validates whether a declarative post-write fan-out plan makes
PostWriteReconcileeasier to digest and extend.Hypothesis
Post-write behavior is a fixed pipeline with a policy fork (sample ingest vs day-data change vs issue-only). That fork should be a pure plan builder;
DayJournalshould only execute steps.What this adds
PostWriteReconcilePlan—PostWriteOutcome,ReconcileStep, andforOutcome(_:)DayJournal.execute(_:)— sequential step runnerPostWriteReconcilePlanTests— asserts plan shape without WidgetKit mocksNon-goals
DailySummaryReconcilerorsetPrimaryRegions(still in TODOs)Verification
PostWriteReconcilePlanTestsDayJournalTests(full suite on prototype branch)Next step if this lands
Adding
DailySummaryReconcilerbecomes extendingforOutcome/ adding a step — not touching every write call site.