channel Channel

Channel-level privacy status. Public, unlisted, and private are the three states common to YouTube, Twitch, Vimeo, and most creator platforms; values map onto each platform's native enum at the connector boundary.

Most-recent-synced statistics for the channel. Snapshot semantics: every field is valid as of the parent record's `provenance.synced_at`. Long-horizon growth curves (year-over-year subscriber deltas, lifetime view trajectories) are reconstructed from the daily audience-snapshot history rather than from successive channel re-syncs.

Cross-platform discriminator on `Channel`. Identifies the host platform a channel lives on. Open-ended by design: new platforms extend the enum without breaking the channel shape — connectors map each platform onto the existing platform-agnostic field set (`platform_channel_id`, `platform_uploads_id`, `provenance`, statistics, breakdowns) without renaming or restructuring.

Classification of a synced field's data sensitivity. Drives subject- rights workflows and cache-purge retention decisions.

ISO 3166-1 alpha-2 country code.

ISO 8601 date (YYYY-MM-DD).

Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`

Retention policy applied to a synced record. Tiers are named after the discipline they impose; the connector layer maps each upstream surface onto the appropriate tier. - `thirty_day_strict` — atomic records that auto-purge or refresh at the thirty-day boundary. The dominant tier on platforms whose Terms of Service impose a thirty-day cache discipline on derived data (e.g. YouTube Developer Policies §III.E.4 for Data API outputs). - `thirty_day_aggregate_with_lineage` — atomic record purges at thirty days; the aggregate computed from it may be retained when accompanied by explicit `derived_from` + `derivation_method` lineage. - `auth_lifetime` — atomic record retains against active OAuth authorisation; tears down on token revocation or tenant deletion. Used for analytics surfaces whose ToS explicitly exempt them from the thirty-day rule (e.g. YouTube Analytics API per §III.E.4). - `creator_authored` — data the tenant originates rather than fetches; no upstream-platform retention constraint applies. - `metadata_indefinite` — structural identifiers and immutable timestamps the upstream ToS explicitly permits to retain.

Source attribution for a synced field. Records the kind of upstream surface that produced the value; combined with the parent record's `platform`, this fully attributes any value back to its origin. Open-ended by design: new connector kinds (e.g. monetary or content- owner APIs) extend without breaking changes. The platform discriminator (`Channel.platform`) carries the brand identity; this enum carries only the kind of API surface the value came from.

Provenance metadata stamped on every synced atomic record across the creator pillar. Per-record granularity; the `retention_tier` reflects the strictest tier of any field on the record so the cache-purge job can decide conservatively. Field-level retention distinctions are documented in each entity type's struct doc-comments — the schema documents the static taxonomy, the data carries only the per-fetch state.