What problem does it solve? Deciding whether an application is ready to hand over to a support team at go-live requires consolidating scattered readiness, security, and code-review findings into one go/no-go decision, which is error-prone when done manually. ## Core Features & Use Cases - Ledger ingestion: Reads the latest prod-readiness report, security ledger, code-review ledger, deployment architecture, and pipeline definitions to derive go-live blockers and fast-follow items. - Never-fabricated findings: Missing inputs degrade to explicit ⚠ TODO rows with a "run /X" note instead of silently passing, and every finding ID is copied verbatim from its ledger. - Structured checklist output: Produces a Markdown Transition Acceptance Checklist with Section A blockers, Section B fast-follows, knowledge-transfer items, handed-over artifacts, a grounded recommendation, and a sign-off table. - Use Case: Before a go-live date, run the checklist to confirm no open Critical/High security findings exist, the rollback demo is scheduled, and the operational runbook is linked for the incoming support team. ## Quick Start Ask the assistant to generate the go-live transition acceptance checklist for this project using the latest readiness, security, and code-review reports.
