launch-registry

1# Launch Registry
2 
3The canonical launch-record authority. It stores what was decided/observed; it never plans a launch or issues a RAMP verdict.
4 
5## Quick Start
6 
7```text
8Register launch widget-2 with tier/type/stage/date/access model and source evidence.
9Transition widget-2 from beta to general-availability at revision 4.
10Review pending launch-day submission proposals without clearing history.
11```
12 
13## Skill Contract
14 
15**Unit:** one launch moment/aggregate ID. **Reads:** `memory/events/launches.ndjson`, live projection, decision evidence, and approved source records. **Writes:** owner events through `registry-events.py`; per-launch dossiers and `calendar.md` are regenerated views. **Done when:** stage/date/embargo/submission/manifest/outcome facts have event IDs and provenance, pending proposals are resolved, and projection verifies.
16 
17Mobilize/prove skills submit `propose`; only a host-capability `launch-registry` principal accepts/rejects/upserts/transitions. `launch-readiness-auditor` consumes the result but cannot mutate it.
18 
19### Handoff Summary
20 
21Include aggregate ID, current revision/state, accepted/rejected event IDs, authoritative dates/embargo, unresolved conflicts, and one next skill.
22 
23## Data Sources
24 
25- User-approved tier/type/access-model and launch plan decisions.
26- Window/date and embargo/partner commitments.
27- Early-access graduation evidence and direct access/eligibility observations.
28- Timestamped channel submission/status proposals.
29…