Publish configuration only against the revision reviewed by the operator
Two operators edit the same draft; the last publisher activates changes based on a stale review.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Optimistic concurrency · Audit logs
Estimated field mix
- Platform engineering60%
- Database engineering40%
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 internal reporting platform changes feature and timeout settings through environment edits. Partial rollouts leave API and worker processes interpreting different values.
Setup prerequisites
- Create local API and worker configuration consumers.
- Use fabricated settings without secrets.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require expected draft revision and reviewed hash.
- Commit publication and active selection together.
- Return a conflict with safe revision metadata on stale publication.
Implementation constraints
- Record actor and reason in an append-only audit record.
Verification to include
- Publish an unchanged reviewed snapshot.
- Race two publishers and assert one accepted active transition.
Deliverables
- Optimistic publication command and race test
Rollout and recovery
Enable publication for a synthetic operator role; disable writes if audit persistence fails.
Value of the work
For the engineer: Practice configuration contracts, compatibility and failure recovery.
For the team: Review controlled configuration delivery with inspectable blast radius.
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.