[EPAC-2308]: Sync ComputeBillVersionDiff catalog with all-pair generation#828
Merged
riddim-developer-bot[bot] merged 1 commit intoJun 15, 2026
Conversation
…tion The bills-indexer use-case policy was updated by EPAC-2302 to emit BillDiff records for every valid ordered version pair (with adjacent pairs still emitted unconditionally for smoke/evidence compatibility), but the use-case catalog still described consecutive-pair generation only. Update the ComputeBillVersionDiff entry's Goal, Outputs, and add a Pair selection rule to match the implementation. Clarify LoadBillVersionDiff's Outputs to distinguish HTTP 200 with `clauses: []` for no-change comparable diffs from nil/unavailable behavior for unsupported pairs. Catalog-only; no code or behavior changes.
riddim-developer-bot
Bot
deleted the
symphony/epac-2308-sync-computebillversiondiff-catalog-with-all-pai
branch
June 15, 2026 12:31
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.
Summary
docs/architecture/use-case-catalog.mdstill describedComputeBillVersionDiffas consecutive-pair generation, but EPAC-2302 changed the implementation to emitBillDiffrecords for every valid ordered version pair (with adjacent-pair artifacts still emitted unconditionally for smoke/evidence compatibility). The catalog now matches the implementation.ComputeBillVersionDiffentry's Goal and Outputs, and adds aPair selection rulecallout describing thei < jiteration, the adjacent-pair carve-out (preserves consecutive-pair artifacts even when text is missing), and the "both sides have parsed clause text" gate for non-adjacent pairs.LoadBillVersionDiffOutputs to explicitly distinguish HTTP 200 withclauses: []for the no-change comparable case fromnil/ HTTP 404 for the unavailable case, matchingbackend/bills/internal/usecase/bills.go.No code or behavior changes.
Closes EPAC-2308.
Verification
scripts/ci/check_catalog_drift.sh— passes locally (no implementation paths or iOS port rows touched).backend/bills-indexer/internal/usecase/compute_bill_version_diff.goandbackend/bills/internal/usecase/bills.goto confirm the new wording matches the actual policy.Simulator verification is skipped: this PR touches only architecture documentation; no app, API, CLI, or script output changes.
Test plan
pr-buildgreen.