Repository navigation
docs(c7): the card stopped resolving through a different anchor, so say what does differ - #110
Merged
lessevv merged 1 commit intoSep 13, 2026
Conversation
…ay what does differ C7's prose explained the net-worth series/card divergence as the card "resolv[ing] through a different anchor path". That stopped being true when the card moved off Forecasting's BalanceAnchorResolver onto the ledger's AccountBalanceQuery -- the sentence has been wrong since, independently of any code change made now. The anchor is not the difference and has not been for some time. The difference is the DAY each surface asks about: the card asks about today, a series point about its bucket's last day, which for the bucket the current period is still inside is a date in the future. Both surfaces now also count the same rows -- beatrax moved the series off clearedBalanceAsOf() onto currentBalanceAsOf(), which is what every other surface that states a balance already read. No acceptance criterion named cleared, so nothing here changes: C7-R8 still requires the divergence to be documented, and there is still a divergence to document. Spec: C7-R8 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Wessel Verheij <info@nightworks.io>
lessevv
enabled auto-merge (squash)
September 13, 2026 14:17
|
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.



The sentence
C7 has explained the net-worth series/card divergence like this:
That clause stopped being true when the dashboard card moved off Forecasting's
BalanceAnchorResolveronto the ledger'sAccountBalanceQuery. Both surfaces have read the same anchor for some time, so the sentence has been wrong independently of any code change — it would still be wrong if nothing were touched.What actually differs
The day each one asks about. The card asks about today; a series point asks about its bucket's last day, which for the bucket the current period is still inside is a date in the future. A
this_monthreport read on 13 September samples 30 September.After
Why "count the same rows" is now true
beatraxmoves the series offclearedBalanceAsOf()ontocurrentBalanceAsOf()— the seam every other surface that states a balance already reads (dashboard card, forecast anchor, calendar past-day line, pot ledger). Before that change the series was the only non-reconciliation caller of the cleared variant, and the chart could contradict the number printed directly above it.No acceptance criterion changes
No
C7criterion named cleared. C7-R7 governs on-demand sampling, C7-R8 requires the divergence to be documented — there is still a divergence (the date), so C7-R8 still binds and is still met. The behaviour table row "The most recent net-worth point versus the dashboard card | May differ; documented." is unchanged and still correct.Spec: C7-R8