Source kit / Store
Not available to buy while the refresh is verified
The planning, rights, captions, QC and sign-off records behind a long-form history channel, packaged as a source kit you run on your own machine.
An agent-ready workflow kit for turning production intent into structured, reviewable packets with explicit sources, rights, QC, captions, metadata, and human approvals.
Drawn to Empire · Episode 1 · April 29, 2026
The Coup That Made Charlemagne Possible | Pepin the Short
Drawn to Empire / What the workflow produced
Drawn to Empire is the YouTube channel Greyforge produced in spring 2026 through its internal ForgeVideo lane: three long-form narrated episodes on the family that produced Charlemagne. Every episode moved through the same packet: sources and claims, script, storyboard and assets, a rights ledger, captions and metadata, QC, then named human approvals.
The kit packages that records-and-validation discipline. It does not render, edit or upload video, and it does not include the private production assets. Human judgment about the story, the cut and the release stays with you.
The channel is complete at three episodes. Production through the internal lane ended in May 2026, so the videos are the reference for what the packet discipline produced, not a preview of an ongoing service.
What ForgeVideo does
Every record a serious release needs lives in one project directory with its own schema, and strict validation checks the relationships between them, not just their shape.
A packet holds brief, research, script, storyboard, assets, rights, captions, metadata, timeline, QC and release records. Release moves through blocked, in review, approved, published or withdrawn, and a fresh packet starts blocked on purpose.
Claims reference sources and script beats reference claims. A dangling reference fails validation instead of slipping into the cut, and every source carries a class, a status and an access date.
Documentary history, technical explainer, interview and podcast, and commentary essay templates seed the beat structure, storyboard and asset plan for the format you are making.
Each asset binds to a rights decision: approved, approved with conditions, replace, unknown or prohibited. Unknown and prohibited block the handoff. A recorded decision is a decision, not legal clearance.
Caption files, title and description candidates, timing checks and QC evidence live in the packet beside the exact revision they describe, so a later edit cannot quietly orphan them.
Editorial, rights, caption and final operator approvals are recorded against the project digest. Change anything and the approvals go stale until someone reviews again.
How it runs
Everything runs locally with Node.js 20 or newer. Only the update check touches the network, and it never downloads code.
Pick a template. The initializer refuses a non-empty destination, and forced replacement moves the previous directory to a timestamped backup first.
node src/cli.mjs init --title "My Project" --out work/my-projectResearch, sources, claims, script, storyboard, assets, rights, captions and metadata are JSON records with schemas. Use the six agent skills or edit by hand.
Structural validation checks shape. Strict validation refuses broken references, unresolved rights, stale approvals and an untouched packet.
node src/cli.mjs validate --strict --project work/my-projectNamed approvals bind to the digest. The handoff bundle lists the media, the supporting records and the next human decision.
node src/cli.mjs handoff --project work/my-project --out work/handoffThe deliverable
Before choosing
Requirements
Platform status below comes from the product catalog. A pending check does not establish a supported release.
Node.js 20+
Verification pending
Node.js 20+
Verification pending
Node.js 20+
Verification pending