Channel Registry

The canonical per-channel truth SSOT — the seventh protocol-layer skill, peer of entity-optimizer (SEO/GEO), creator-registry (influencer), offer-claims-registry (paid), consent-registry (email), and launch-registry (launch), and the record the ECHO E1 (channel-truth) veto and the H2 (UGC permission) veto are judged against. It CURATES the channel record — registry, not gate: no class: auditor, no cap fields, no veto scoring, no SQS roll-up. It stores dated facts; social-quality-auditor judges E1/H2 against those facts, exactly as launch-readiness-auditor judges R1 against stage records.

One durable dossier per brand-owned handle (<platform>-<handle-slug>.md) holds: the platform + handle URL, the access governance block (credential holder, 2FA state, agency access, approval ladder), the declared objective + ECHO goal column (community-devtool / B2C-brand / B2B-founder-led), the versioned bio/link-in-bio inventory, the voice-card pointer (per-platform register from voice-dossier.md), the dated platform-rule snapshot pointer (references/platforms/* card + last-verified date), the cadence commitment (with counterparty and deciding source), the lifecycle state on the machine proposed → warming → active → paused → retired (dated, evidenced transitions; warming → active requires participation-warmup graduation evidence; reactivation is a new dated transition, never a rewrite), an append-only activity ledger, and outcome snapshots. Four standing files sit beside the dossiers: voice-dossier.md (the voice record every Craft skill reads first — the per-platform adaptation of the brand voice canon owned by narrative-registry, which it points up to and never redefines), ugc-permissions.md (the ECHO H2 fact base), advocate-roster.md (the ECHO H1/C2 fact base), and calendar-commitments.md (the over-posting guardrail fact base).

Channel-first, not person-shaped: this registry's unit is the handle, never the human. Person data appears only as minimal, non-authoritative rows in advocate-roster.md (handle, disclosure line, opt-in date, voluntary-basis evidence) and ugc-permissions.md (creator, content ID, scope, expiry, evidence link), cross-pointed to creator-registry (canonical creator records) and consent-registry (email subjects). Converting an organic UGC permission to paid/ad use requires a creator-registry record plus contract-helper terms first — the ugc-permissions.md row gains a paid-scope field only when that record exists. Public posting, tagging, or branded-hashtag use is never permission; organic consent never covers paid use.

Scope seams — who keeps what:

• The E1 channel-truth verdict and the SQS stay with social-quality-auditor; this registry supplies the state, voice, cadence, and permission facts — never a go/no-go or a "healthy channel" label. No dossier on file = NEEDS_INPUT, not pass-by-default (the same red line as the E1 row in ECHO).
• Deciding which channels to run stays with channel-portfolio-planner; building the voice record stays with voice-dossier-builder; designing the warming ramp stays with participation-warmup-planner. This registry records what was decided, not what to decide.
• Collecting UGC permissions stays with engagement-inbox-manager (its UGC curation-and-rights mode); it drops dated permission entries into memory/channels/candidates.md, and this registry promotes them.
• Paid/collab creator person records stay with creator-registry; claim wording with offer-claims-registry; email consent with consent-registry; launch dossiers with launch-registry. This registry owns channel dossiers and its four standing files only.
• Archival stays with memory-management — the sole WARM → COLD executor; a channel retires on a dated retired transition, never on a timer.

Quick Start