Show finance what changed since their last review
After clarification, a requester changes both the explanation and amount. The review page says Updated without identifying which lines changed.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Diff presentation · Immutable data · Review workflows
Estimated field mix
- Frontend100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Beacon operations team buys equipment through a browser form. Finance checks totals, departments, and quotes. Scope is one currency per request and an approval API contract; payments and accounting integration are excluded.
Setup prerequisites
- Synthetic department and cost-center directory
- Draft, submission, and approval API fixtures
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FORM-102 · Make the total match the submitted line items
- FORM-101 · Point requesters to the field that needs fixing
- FORM-103 · Clear an orphaned cost center when department changes
- FORM-104 · Save drafts without overwriting a second browser tab
- FORM-105 · Show attachment quarantine and upload recovery clearly
Acceptance criteria
- The view compares two explicit immutable revisions.
- Stable line IDs identify additions, removals, and old/new values.
- Collapsing unchanged fields keeps total difference and revision identifiers visible.
Implementation constraints
- Use the shared money calculator; array position is not a line identity.
Verification to include
- Reorder unchanged lines and confirm no false replacements appear.
- Remove one line and increase another; verify both changes, total difference, and a missing-baseline error.
Deliverables
- Revision comparison view and change-set fixtures
Rollout and recovery
Add a comparison tab; hide it on regression while preserving both original revision pages.
Value of the work
For the engineer: Practice form modeling, exact totals, revision handling, and collaboration under failure.
For the team: Inspect whether a developer protects business workflows from duplicate, lost, or misleading submissions.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.