Use when live product annotations or reviewer notes must become hard reconciliation rows before a goal loop, ticket swarm, or QA pass may claim readiness.
Use when a merged Squad slice or Squad-style release candidate is ready for delivery work: deploy-readiness verification, artifact and manifest checks, updater feed verification, release-note assembly, human-triggered release handoff, and rollback or re-release receipts.
Use when today's real calendar availability needs to become a concrete ticket execution calendar backed by the issue-tracker dependency graph.
Use when today's execution day is already in motion and calendar blocks, issue-tracker due-work, and review waves need to be reflowed because a blocker cleared, a lane slipped, or review landed differently than planned.
Use when turning a live browser-backed design review into durable Design Contract tickets, then handing approved route clusters into implementation-contract compilation.
Use when feature ideas are scattered across team chat, meetings, and an issue tracker and we need one durable ledger for beta thesis, explicit non-goals, parking-lot features, kill-list candidates, and undecided gaps.
Use when a product owner gives a /goal-style long-running product outcome that should loop through discovery, implementation-contract materialization, readiness QA, telemetry review, and blocker re-planning.
Use when approved Squad Design Contract clusters or implementation-readiness rows need to become seam-locked child contracts under the active Implementation Contract parent before ticket-to-human-review execution.