Production evidence and Studio intake

The Content Studio may research, reason, script, generate, compose, and publish, but it should begin from an exact immutable intake rather than re-querying mutable practice state throughout production.

Intake contents

• member and Pursuit/Sprint references appropriate to the authorized project;
• exact package release and capability versions;
• Attempt/revision identities and Measurements;
• progression and finish-line evidence;
• current Story Events and explicit retractions;
• capture identities, media anchors, clock provenance, and evidence gaps;
• overlay/narration presentation references;
• checksums and sealing time;
• privacy and use constraints.

What is deliberately absent

• Station credentials;
• OBS passwords;
• provider API keys;
• connector grants;
• arbitrary account history;
• mutable live activity handles;
• claims not supported by committed evidence.

Idempotent handoff

Sealing the same eligible source set with the same request identity returns the same intake. If corrected evidence requires a new intake, preserve the relation to the superseded one rather than mutating bytes that editorial work may already reference.

Package author quality bar

A sophisticated creator package should let an editor answer:

1. What was the goal?
2. What was the starting point?
3. Which moments materially changed the story?
4. What result was authoritative after correction?
5. Where is the corresponding media?
6. Which periods are missing or uncertain?
7. Which domain context will still require external research?

The package supplies trustworthy domain facts. It does not attempt to replace editorial judgment or exhaustive topic research.