Missions / Engineering
Dependency upgrade with verified rollback path
Dependency upgraded with evidence of tests passing; rollback path verified executable
This mission design is in development. It has not been exercised end-to-end in a production repository.
Architecture summary
Context intelligence identifies dependency, version, and affected files. Execution agents perform the upgrade under control-plane gates. Evidence verification captures test results. Rollback path is verified before declaring success.
Stages
Discovery
Identify dependency, current version, target version, and affected import sites
Evidence: Dependency manifest and import analysis artifact
Risk assessment
Score change risk based on dependency graph and historical data
Evidence: Risk score with blast radius estimate
Implementation
Upgrade dependency version in manifest and run install
Evidence: Updated manifest and lockfile
Verification
Run tests and capture pass/fail evidence
Evidence: Test run results with coverage
Rollback preparation
Verify rollback path is executable
Evidence: Rollback script with dry-run output
Controls
Control-plane gate
Every stage passes through control-plane for approval
Evidence gate
Test results must pass before commit
Rollback gate
Rollback path must be verified before merge
Composition
- Capabilities used
- context-intelligence, execution-agents, evidence-verification
- Integration categories used
- source-control, ci-cd
Constraints
- No upgrade without verified rollback path
- Tests must pass for all supported versions
- Evidence of each stage required
See related design notes
- Designed for npm/yarn/pip ecosystems
- Rollback verification is the safety rail
- Scope limited to direct dependencies in initial implementation