System

How a video is governed

An autonomous media operation is only as trustworthy as its constraints. This one refuses to publish on uncertainty, and can explain every decision it made.

The problem this is built to solve

Fluency is cheap now. Consistency is not.

A language model can produce ten thousand words of plausible content about God that quietly contradicts itself — affirming God's grace in one paragraph and a transactional deity in the next. At volume, that drift is not a proofreading problem. It is a governance problem.

So theology here is not a style guide. It is a versioned data artifact that is rendered into a role-specific policy pack, injected into every agent call, and checked against the artifact that comes back. The agent never operates from memory of doctrine, and the audit engine can only downgrade an agent's claimed status — never upgrade it.

The gate

Six audit points, one outcome: publishable or not.

01

Task

Director issues a task carrying the constitution version and hash. No hash, no work.

02

Policy pack

Role-scoped, document-kind-scoped, itself hashed. Injected into the call.

03

Result

Strict schema: status, scripture, claims, uncertainties, interpretive notes.

04

Audit

Detectors, terminology, corpus verification, citation completeness, attestations.

05

Gate

Any blocking status blocks READY_TO_PUBLISH at the state-machine level.

06

Record

Findings, hash and reviewer are stored. Overrides are recorded, never silent.

Twelve agents, one with a publish button

Separation of duties applies to software as much as to finance.

CodeAgentResponsibility
AGENT-00Channel DirectorOwns strategy, calendar, budget and enforcement. No editorial authority of its own.
AGENT-01Research & DiscoveryFinds real audience questions. Never fabricates search volume.
AGENT-02Biblical ResearchResolves references and quotations against a licensed corpus; assembles context.
AGENT-03Theological HermeneuticsTests every interpretation against Jesus' revelation of God. Records attestations.
AGENT-04ScriptwritingSpoken-word script with hook, argument, Scripture, application, call to action.
AGENT-05Cinematic ProductionStoryboards, camera, lighting, transitions, symbolism. No misleading reconstruction.
AGENT-06Voice & AudioConsistent narrator identity, pacing, normalisation, music bed.
AGENT-07Thumbnail & BrandingMultiple concepts, mobile-readable, honest to the content.
AGENT-08SEO & GrowthTitles, descriptions, chapters, playlists. No claim the video does not deliver.
AGENT-09ShortsTwenty per month with independent hooks — not contextless clip extraction.
AGENT-10PublishingThe only agent with upload rights, and only for artifacts that already passed the gate.
AGENT-11AnalyticsRetention, traffic, pillar performance. Separates observation from causation.

Failing closed

Six of the seven audited statuses block publication. Silence is never treated as verification.

Blocking statuses

THEOLOGY_CONFLICT SCRIPTURE_UNVERIFIED HISTORICAL_CLAIM_UNVERIFIED THEOLOGY_UNCERTAIN NEEDS_THEOLOGICAL_REVIEW

Passing statuses

THEOLOGY_VERIFIED THEOLOGY_VERIFIED_WITH_QUALIFICATIONS

Scripture is checked, or it is not published

Every reference is resolved and every quotation compared against a licensed translation. If no licensed corpus is installed, the result is SCRIPTURE_UNVERIFIED and publication is blocked. A system that quotes from memory will eventually misquote Scripture on camera.

Installed: Berean Standard Bible (BSB), 31,086 verses, licence: Public Domain. Verses the edition omits are reported as omitted rather than as wrong references.

Workflow

Eighteen persistent states. Stages are resumable and idempotent; a failed stage never restarts the project.

IDEA_CREATEDRESEARCHINGRESEARCH_VERIFIEDTHEOLOGY_VERIFIEDSCRIPT_GENERATEDSCRIPT_VALIDATEDSTORYBOARD_READYGENERATING_ASSETSVIDEO_ASSEMBLYVIDEO_QCPACKAGING_READYREADY_TO_PUBLISHSCHEDULEDPUBLISHEDANALYZINGCOMPLETEDFAILEDNEEDS_REVIEW

Architecture

A modular monolith, deliberately. At four long-form videos and twenty Shorts a month with one operator, distributed services would add failure modes without adding capacity.

LayerTechnologyWhy
API & orchestrationPython, FastAPITyped contracts at every boundary; trivially testable
PersistencePostgreSQLTraceability chain from idea to published video
GovernanceVersioned JSON + hashingPolicy changes are auditable, never a code deploy
DashboardNext.jsInspect why a video passed or failed
MediaFFmpeg, provider adaptersNo hard coupling to a single generation vendor
HostingCloudflare PagesStatic, fast, no runtime to patch

Further reading

The architecture, database schema, agent protocol and cost model are all documented.

Documentation index →

What does not exist yet

Generation, upload and analytics integration. The gate was built first, on purpose: adding generation before governance produces content that cannot be certified.

Roadmap →