launch-registry
Launch Registry
The canonical per-launch truth SSOT — the sixth protocol-layer skill, peer of entity-optimizer (SEO/GEO), creator-registry (influencer), offer-claims-registry (paid), and consent-registry (email), and the record the RAMP R1 (stage-truth) veto and the M embargo/coordination sub-items are judged against. It CURATES the launch record — registry, not gate: no class: auditor, no cap fields, no veto scoring, no LQS roll-up. It stores dated facts; launch-readiness-auditor judges R1 against those facts, exactly as email-quality-auditor judges S2 against consent records.
One durable dossier per launch moment holds: the tier (T1 flagship / T2 targeted / T3 changelog-level) and launch type (new-product / feature / relaunch / partnership), the lifecycle stage on the one-way state machine draft → concept → alpha → beta → general-availability (+ archived; GA is one-way — a rollback is recorded as a dated incident note, never a silent stage rewrite), the authoritative launch date/window and every embargo / partner date commitment, the channel submission ledger (platform, planned/submitted-at, live URL, status, outcome metrics), the asset-manifest version pointer (which kit version shipped where), the declared RAMP goal column (B2B / dev-tool / mobile), and the post-launch outcome snapshot from the retro. A standing calendar.md lists every past and planned launch moment — the fact base for the launch-stacking guardrail.
Why launch needs its own SSOT: the announcement email flow, the paid flighting, the creator campaign, and the community submissions must all agree on one date, one stage, one embargo — without a registry that truth drifts across handoffs, and the gate has nothing to judge stage-truth against.
Scope seams — who keeps what:
- The R1 stage-truth verdict and the LQS stay with launch-readiness-auditor; this registry supplies the stage record and date/embargo facts — never a go/no-go or a "ready" label. No stage record on file =
NEEDS_INPUT, not pass-by-default (the same red line as the R1 row in RAMP). - Deciding the tier, type, and timeline stays with launch-tier-planner; picking the window stays with launch-window-planner. This registry records what was decided, not what to decide.
- Executing channel submissions stays with community-launch-runner and press-media-relations; they drop dated submission-ledger updates into
memory/launch-registry/candidates.md, and this registry promotes them in batch (see Instructions step 6). - Claim wording and offer terms stay with offer-claims-registry; consent records with consent-registry; product entity facts with entity-optimizer. This registry owns launch dossiers, the calendar, and the submission ledger only.
- Archival stays with memory-management — the sole WARM → COLD executor; dossiers retire after the outcome snapshot lands, never on a timer.