narrative-registry

1# Narrative Registry
2 
3The L1 strategy authority: one complete, versioned narrative canon per brand. Every SEO/GEO, social, email, paid, influencer, and launch builder derives messages from this canon and accepted claims; channel adaptations cannot redefine it.
4 
5## Quick Start
6 
7```text
8Show current canon version and proof/claim pointers for brand-acme.
9Record canon v3 as one complete atomic replacement, superseding v2.
10Review pending narrative proposals and reject partial/internally inconsistent versions.
11```
12 
13## Skill Contract
14 
15**Unit:** one brand canon aggregate ID. **Reads:** `memory/events/narrative.ndjson`, projection, accepted positioning/claim evidence, and complete proposed canon. **Writes:** narrative events through `registry-events.py`; `canon.md`/`versions.md` are generated views. **Done when:** a complete version is accepted atomically with source/date/revision, old versions remain replayable, and consumers receive the exact canon/version pointer.
16 
17Narrative skills submit complete `propose` events. Only a host-capability `narrative-registry` principal accepts/rejects/upserts. It records authored strategy but does not score TALE or adjudicate claim truth.
18 
19### Handoff Summary
20 
21Include brand ID, canon version/revision/event ID, superseded version, claim/proof pointers, unresolved contradictions, and one next skill.
22 
23## Data Sources
24 
25- Accepted positioning truth and named alternatives.
26- Complete message hierarchy/narrative authored by Narrative skills.
27…