Require expiry and ownership for emergency feature overrides
A disable-delivery flag added during a rehearsal remains set for weeks because its reason and owner exist only in chat.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Feature flags · Operational governance · Time modeling
Estimated field mix
- DevOps70%
- Site reliability30%
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 notification service uses environment files assembled by shell scripts. Defaults differ by machine, secret values appear in diagnostics, and emergency flags have no expiry. Build a typed local configuration compiler with fake secret references and synthetic environments; no real credentials or notification providers are supplied.
Setup prerequisites
- Configuration precedence
- Schema validation
- Least privilege
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Override records owner, reason, scope, creation, and expiry
- Expired override fails compilation instead of remaining active
- Normal configuration remains visible beneath the override
Implementation constraints
- Use synthetic operator identities; flags do not bypass authorization or audit.
Verification to include
- Apply an active scoped override and show its provenance.
- Compile expired and ownerless overrides and confirm blocking errors.
Deliverables
- Expiring override registry and policy tests
Rollout and recovery
Introduce reporting before rejecting legacy unowned fixture flags.
Value of the work
For the engineer: Practice configuration as a reviewed contract with safe diagnostics, provenance, and rollback.
For the team: Review environment changes before deployment and reduce outages caused by missing, stale, or silently defaulted settings.
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.