Verify unknown enum values do not crash old clients
A new fulfillment status reaches a client compiled against the previous enum.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Compatibility · State modeling
Estimated field mix
- Quality engineering60%
- API design40%
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
A fictional fulfillment API serves a web checkout and warehouse adapter. Provider tests pass while consumers fail on subtle response and error changes.
Setup prerequisites
- Author two small local consumers and one mock provider with versioned synthetic responses.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Define unknown-status behavior for each consumer.
- Preserve the raw value for safe diagnostics.
- Avoid treating unknown as delivered or cancelled.
Implementation constraints
- Unknown states must not trigger irreversible actions.
Verification to include
- Handle every documented status.
- Feed a future status and verify conservative behavior.
Deliverables
- Forward-compatible enum checks.
Rollout and recovery
Deploy tolerant readers before adding new provider values.
Value of the work
For the engineer: Practice executable contracts, meaningful negative tests, and compatibility triage.
For the team: Expose integration regressions before deployment without requiring every system to run together.
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.