Capability Guide: Baseline, Impact, and Operations¶

Purpose¶

Govern release state, evaluate change impact, and produce actionable readiness plans.

Modules In Scope¶

• baseline_mgmt
• impact_assessment
• ops_mgmt

When To Use This Guide¶

• preparing release candidate governance reviews
• evaluating downstream effects of baseline changes
• converting impact findings into readiness actions/milestones

Release Governance Flow¶

sequenceDiagram
    autonumber
    participant Base as Baseline
    participant Impact as Impact
    participant Ops as Operations
    participant Gov as Governance

    Base->>Impact: release candidate
    Impact->>Ops: impact implications
    Ops->>Gov: readiness and milestones
    Gov-->>Base: release decision feedback

Step-by-Step¶

1. Build release candidate and compare against prior state.
2. Package release candidate with relevant trace/evidence context.
3. Perform impact assessment against dependent artifacts.
4. Create/update readiness actions and milestone dependencies.
5. Submit governance decision package.
6. Feed decision outcomes back into planning.

Artifacts Produced¶

• baseline history/compare records
• release pack details
• impact findings/reports
• readiness backlog and milestone plans

Integration Consumers¶

• governance stakeholders (decision authority)
• delivery teams (execution planning)
• assurance/verif teams (evidence completeness feedback)

Validation Checklist¶

docker compose run --rm app sh -c "pytest baseline_mgmt/tests impact_assessment/tests ops_mgmt/tests -v"
./scripts/run_smoke_tests.sh

• release candidate trace set is complete
• impact findings are scoped to current candidate
• readiness dependencies are explicit and actionable

Common Failure Modes¶