Detect plan drift between review and execution
A plan is reviewed, then regenerated with additional deletions before execution.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Integrity · Change control
Estimated field mix
- Cloud infrastructure50%
- Security30%
- Developer tooling20%
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 application team manages a small database, cache, and object store. Reviewers struggle to distinguish harmless configuration changes from destructive replacements.
Setup prerequisites
- Author synthetic infrastructure plans and state snapshots; use local files only and no cloud credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BIAC-101 · Normalize infrastructure resource actions for review
- BIAC-102 · Redact sensitive plan values while preserving review context
- BIAC-104 · Reject public exposure introduced by default configuration
- BIAC-103 · Flag replacements of persistent resources with recovery requirements
- BIAC-105 · Validate backup retention changes against declared recovery policy
Acceptance criteria
- Bind approval intent to plan digest and target identity.
- Check state serial and configuration revision.
- Reject modified or stale plans.
Implementation constraints
- No actual cloud apply is performed in this exercise.
Verification to include
- Accept an unchanged synthetic reviewed plan.
- Change one action and reject the execution intent.
Deliverables
- Plan binding verifier.
Rollout and recovery
Require regeneration and review on drift; preserve prior plan artifacts.
Value of the work
For the engineer: Practice infrastructure risk analysis, plan integrity, and least-privilege change workflows.
For the team: Give infrastructure reviewers concrete change scope and recovery consequences.
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.