← All Productions

Facts Over Feeds: A Governed Production Pilot

Warrant · Media Foundry Pilot · 001 · rights approval

Premise

Show how a Summit production object moves from evidence packet to publishable omnimedia package without losing provenance.

Audience Promise

Listeners leave with a concrete workflow for publishing faster while preserving evidence, rights, and approval discipline.

Review Dashboard → Source Appendix → API JSON →

Claims (3)

ClaimRiskStatusEvidence
A strong production apparatus must preserve source traceability before a public narrative ships.mediumapproved1
The sample archive packet includes a procurement timeline with vendor briefings and a conflict-screen request.lowapproved2
One canonical production object can plan podcast, video, newsletter, social, transcript, and source-appendix outputs.lowapproved1

Sources (2)

Council public works minutes excerpt
Council public works minutes excerpt, lines 12 and 18. · legal_record · high reliability
Producer interview log excerpt
Internal producer interview log at 00:04:11-00:04:29. · interview · medium reliability

Script (3 lines, ~42s)

[HOST] 12s

Most media stacks can cut a clip. Fewer can show the source trail behind every claim before the clip leaves the building.

[NARRATOR] 14s

In this Summit pilot, the episode plan, evidence ledger, voice metadata, rights notes, and distribution plan all live inside one production manifest.

[HOST] 16s

The fixture record shows vendor briefings and a conflict-screen request, so the package can generate a source appendix alongside podcast and social outputs.

Segments (2)

1. Cold open: provenance or speed? 45s
Set up the production-system problem.
2. The production object as operating system 180s
Explain canonical manifests and derivative outputs.

Distribution (4 targets)

Warrant RSSSummit YouTubeSummit NewsletterInternal Archive

Outputs (7)

podcast episodetrailershort clipnewsletter issueshow notestranscriptsource appendix