creator-registry

1# Creator Registry
2 
3The canonical creator-roster authority. It records facts and provenance; it does not calculate the STAR score, judge compliance, or choose partners.
4 
5## Quick Start
6 
7```text
8What rate, rights, and exclusivity facts are current for creator-7f42?
9Accept or reject the pending creator proposals for creator-7f42.
10Record the closed spring campaign rate and performance baseline with source/date.
11```
12 
13## Skill Contract
14 
15**Unit:** one pseudonymous creator aggregate ID with verified handle links. **Reads:** `memory/events/creators.ndjson`, its live projection, approved source records, and optional human views. **Writes:** canonical creator events via `scripts/registry-events.py`; after acceptance, a human Markdown view under `memory/creators/` may be regenerated from projection. **Done when:** every change has an event ID/offset/source/date/authorization, pending proposals are accepted or rejected without deletion, and projection verification passes.
16 
17Other skills may append only `operation: propose`. Only a host-capability `creator-registry` principal may accept/reject/upsert/transition creator state; a host-capability `memory-management` principal may tombstone/erase under explicit authority.
18 
19### Handoff Summary
20 
21Use [skill-contract.md](../../references/skill-contract.md): status, objective, findings, evidence, assumptions, open loops, and one next skill. Include event IDs and latest projection revision for changed records.
22 
23## Data Sources
24…