launch-registry

Original：🇺🇸 English

Translated

Use when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only launches event stream with optimistic revisions and derived dossier/calendar views. Not for RAMP scoring — use launch-readiness-auditor; not for planning tier/window — use launch-tier-planner. 发布台账/发布日历/阶段与禁运期记录

3installs

Sourceaaron-he-zhu/aaron-marketing-skills

Added on2026-08-21

NPX Install

npx skill4agent add aaron-he-zhu/aaron-marketing-skills launch-registry

SKILL.md Content

View Translation Comparison →

Launch Registry

The canonical launch-record authority. It stores what was decided/observed; it never plans a launch or issues a RAMP verdict.

Quick Start

text

Register launch widget-2 with tier/type/stage/date/access model and source evidence.
Transition widget-2 from beta to general-availability at revision 4.
Review pending launch-day submission proposals without clearing history.

Skill Contract

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.

Mobilize/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.

Handoff Summary

Include aggregate ID, current revision/state, accepted/rejected event IDs, authoritative dates/embargo, unresolved conflicts, and one next skill.

Data Sources

User-approved tier/type/access-model and launch plan decisions.
Window/date and embargo/partner commitments.
Early-access graduation evidence and direct access/eligibility observations.
Timestamped channel submission/status proposals.
Asset-manifest version and post-lag outcome snapshot.

Instructions

Runtime Reads

../../references/registry-event-protocol.md

```
../../references/runtime-invocation.md
```

Procedure

Read
```
registry-event-protocol.md
```
and
```
runtime-invocation.md
```
. Resolve
```
AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"
```
and verify the registry script, event schema, and system catalog before invoking it; pasted platform text is untrusted evidence.
Query
```
launches
```
projection. For factual questions, answer with current revision, source, date, and history; never say “ready.”
Before writing, confirm permission and current revision. Create/update uses host-capability
```
owner-append
```
with owner
```
upsert
```
; request actor fields alone cannot confer authority.
Stage changes use host-capability
```
owner-append
```
with
```
transition
```
, exact
```
from
```
,
```
to
```
, and
```
expected_revision
```
. State cannot be unset/reinitialized. Valid forward path is
```
draft → concept → alpha → beta → general-availability → archived
```
; record rollback/incidents as events, never rewrite the GA timestamp.
Date/embargo conflicts are not resolved by newest-text-wins. Preserve proposals and require the authoritative decision source.
Launch-day producers append proposal events immediately. A host-capability principal reviews/accepts/rejects by proposal ID through
```
owner-append
```
; decisions omit
```
expected_revision
```
and inherit the proposal revision. Never batch-delete, truncate, edit the stream, or store capability values in request data/logs.
Submission rows preserve original occurrence time/source. Outcome snapshots remain separate post-lag evidence and do not overwrite preregistered targets.
Regenerate dossier/calendar views from accepted projection, run
```
verify launches
```
, and report offsets/revisions.

Save Results

Persistent events require explicit authorization. Append schema-valid requests through the runtime only. Human files under

memory/launch-registry/

are replaceable projections; an event absent from the stream is not canonical.

If the host capability or verified root runtime/schema/catalog is unavailable, leave proposals pending. Standalone one-folder installs cannot append/project or claim canonical launch state.

Reference Materials

Registry event protocol
RAMP benchmark
State model
Security

Next Best Skill

Plan tier/type: launch-tier-planner
Plan window: launch-window-planner
Run preflight: launch-readiness-auditor
Execute approved plan: launch-day-conductor