RAAVE is an Ai-driven editor that mines raw podcast footage for the best moments and builds polished episodes, with the host keeping final approval.
From raw footage to finished episode: RAAVE mines the recording, cuts the noise, and delivers a polished podcast, the same way it produces Navy Sea Stories.
The overview explains why RAAVE exists, and what it is already proving on Navy Sea Stories. The technical view explains how the app keeps an agent focused on the right deliverables.
After setup is done and the final system configuration is approved, RAAVE is designed for semi-autonomous operation with your own agent.
A studio for your agent — not a standing production staff
Making a weekly show takes more than a cutting tool. It takes an editor, an audio engineer, a rights checker, a copywriter, and a publisher. Those are real roles, with real hard costs. RAAVE is built so that work can be done by the Ai agent you already trust, inside a system that will not let unapproved work go public on its own. One person can run it, or a small crew can. The design flexes to the use, rather than locking a show into a single way of working.
What it would cost to hire people instead
A weekly show needs a video editor, an audio engineer, a rights checker, a copywriter and an uploader. That is the work RAAVE and a bring-your-own Ai agent handle for Navy Sea Stories.
Five full-time hires
An estimated $376,000 to $679,000 a year to fill all five roles with full-time employees, including benefits and other employer costs.
[1][2]
Basis: US national wage estimates for May 2025, from the 25th to the 75th percentile, for the closest occupation to each role: film and video editors, sound engineering technicians, paralegals and legal assistants (rights checking), writers and authors (copy), and audio and video technicians (uploading).[1] Wages are divided by 0.685, because wages and salaries are 68.5 percent of employer costs for full-time private-industry workers.[2] Software and management time are not included.
- U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025 national estimates (SOC 27-4032, 27-4014, 23-2011, 27-3043, 27-4011). bls.gov/oes/tables.htm
- U.S. Bureau of Labor Statistics, Employer Costs for Employee Compensation, June 2026 (released September 9, 2026). bls.gov/news.release/ecec.nr0.htm
Navy Sea Stories is how we know it works
Navy Sea Stories is a weekly opinion show made by US Navy veterans, most of them submariners, who served, lived a civilian life, and now question the things they see happening to our Nation. No scripts. It is built for candid conversation about the hard things: veterans who served through difficult, dangerous duty speak freely, bring supporting evidence to the show, and keep it from getting personal. It is not a news or fact-checking program, and each crew member says their own opinion out loud.
The show has gone out every week since November 2025 — 52 straight weekly shows through November 3, 2026. Episode 053 was recorded live on Veterans Day, November 11, 2026, from 6 to 10 PM CT, starting the show’s second year. That is the use case RAAVE is proven on.
Hundreds of hours of recorded episodes are public on the show’s YouTube channel.
NSS makes two kinds of source recordings, and both get the same treatment after the fact:
Live Shows
A live session is recorded as it happens. Nothing is edited during the live show. Afterward, that raw recording is used to produce 20- to 30-minute Editions.
Recorded episodes
Some episodes are recorded specifically, not as a live show. They receive the same edition treatment — the same checks and the same paths to the audience.
The most current work is the best example
The latest published editions come from Episode 052, recorded on November 3, 2026, and cut into seven editions. The last of that series, 052g, published on Veterans Day, November 11[3] — the same day Episode 053 was recorded live, from 6 to 10 PM CT. Editions from that live recording are produced afterward, not during the show.
Episode 053
Recorded live on Veterans Day, November 11, 2026, from 6 to 10 PM CT, starting year two. The live recording is the source for the editions that follow.
Live: YouTube, Rumble, X, and Kick. Recorded: YouTube and Rumble, plus Spotify, Substack, and Amazon Music & Audible.
- Navy Sea Stories, “What Does the Moon Have to Do With a Submarine?” (052g), published November 11, 2026. YouTube · Substack
Built out of a real lesson, not a hypothetical one
The show took a real copyright strike once. Rights-awareness is why the tool carries the name it does — not a marketing flourish, the actual founding constraint. Every clip, from the moment it is cut, carries its own rights status and its exact remediation decision as a permanent part of the record.
“The more brutal it is, the more I want it in. Period.”
— the standing editorial rule this tool was built to protect, not dilute
The room that keeps the agents and the owner aligned
TownSquare is the companion system to RAAVE. RAAVE is the studio your own agent works in. TownSquare is the room where that agent, any additional agents you add, and you as Editor-in-Chief stay aligned. Agents post short updates when work is ready, blocked, or delivered, and point to the file that holds the details. You watch, and you are pulled in only for direction or approvals. Nothing public goes out, and nothing already public is taken down, except on your word.
We proved this in real production on Navy Sea Stories, including live wake-ups so the right agent could pick up a task without someone watching its screen. TownSquare is a proven, working prototype. NSS is the first use case, and the idea is simple: the agents do the work, the app keeps them on the deliverables, and a human signs off.
Nothing ships until a human says so
Every piece of work starts as a proposal. A piece only leaves the building after the owner reviews it and approves it in their own words, and that approval is logged. Each episode also carries a standing never-public list — ranges that no render is allowed to include.
The raw files stay on the show’s own machine.
The technical overview explains how the app keeps the agent on those deliverables, step by step.
An agent has no training to make a show. RAAVE is the framework it works inside.
On its own, an Ai agent can talk, write, and suggest. It does not arrive already trained to produce a show’s actual deliverables: editions of the right shape and length, shorts, copy written as an invitation to listen, a rights-aware cut, and a file that has passed the gates. RAAVE is the framework that makes that work possible. The agent and the human define those deliverables together, from what Navy Sea Stories has already proven in use. The app then keeps the agent focused on that work, in the right order, with evidence at each step, and with a human as the only approver.
The Agent
- Dissects the raw recording and learns the structure of the conversation before anything is cut.
- Proposes the edits, the editions, the shorts, and the copy — with a plain-language reason for the choices that matter.
- Hands work to the next specialist agent in a written package, instead of leaving the job in a private chat.
The App
- Supplies the show’s memory, its rulebook, and the institutional record of every guest, story and rights decision.
- Runs the gates, the render, and the publishing pipeline, so a proposal comes out as a finished, checked file.
- Holds the last word for a human: nothing public ships until the owner approves it in their own words, and that approval is logged.
What follows is what that framework does on a real show. It is in weekly use on Navy Sea Stories. This describes what the system does, not how it is implemented.
From a raw recording to the week’s deliverables
A source recording may be a live show or a session recorded specifically for the show. In either case, the edit happens after the recording exists. A live show is not edited while it is on the air.
01
The recording arrives
A session can arrive as a single mixed audio track. RAAVE saves production time by recognizing returning speakers, so they're named automatically. It only recognizes voices; it never recreates them. A live show is never edited while it is on the air; its editions are made afterward.
02
Find the moments worth keeping
Before anything is cut, RAAVE maps the conversation and surfaces the stretches worth building around. Editions are organized around a question, not a topic, and typically run 20 to 30 minutes. A human picks the hooks.
03
Edit with a reason
For recorded episodes, multi-camera editing follows the conversation, keeps picture and sound in sync, and gives a plain-language reason for every cut. Live editions are not cut between cameras.
04
Clean up the sound
Spoken fillers are removed without changing the timing, and every change is logged for review.
05
Finish, write, and make the shorts
Music sits under the speech, and the finished file is checked against the approved audio. Titles and descriptions are written as an invitation to listen and shaped for each platform. Vertical Shorts and promotional posts are built from the same approved material.
06
Check, then deliver
The plan, the finished file, and the upload text are each checked before anything goes out, and nothing ships without the owner’s approval. Live editions go to YouTube, Rumble, X, and Kick. Recorded editions go to YouTube and Rumble, and also to Spotify, Substack, and Amazon Music & Audible.
What the agent and the human define together
The deliverables are not a generic export preset. They are defined by the owner and the agent together, from the show itself. On Navy Sea Stories, that definition already includes:
Editions
Typically 20 to 30 minutes, ordered by context rather than tape order, with the show bumper opening each one. A single session can become several editions. Main Episodes and Deep Dives are the long forms; Shorts are the cliffhanger or gut-punch line, on their own vertical path.
Copy
Titles, descriptions, captions and posts, written as an invitation to listen and built the same tiered way as the pieces they point to.
Gates
Checks on the plan, the file, and the upload text; the owner’s logged approval; and the never-public list. A proposal is the process. A human sign-off is what makes it a finished file.
Rulebook
Every real correction becomes a standing rule in a learnings log, so each new edit starts smarter than the last one. The ruleset is specific to the show, and distinct from the software that runs it.
Nine textures give the show a shared language for what a moment actually is — Heartfelt, Tough Love, Contentious, Warmth, Funny, Angry, Scared / Vulnerable, Credibility, Profound — so a choice between clips has a stated reason behind it. The archive remembers guests, recurring formats, cited answers to “have we told this story before?”, and flags personal or family material for the owner.
A companion system for the agent team
TownSquare is a shared coordination board for a bring-your-own-agent setup. Each agent has a known role and posts under that role. The board is RAAVE infrastructure, separate from the editor, and available to any show that runs on RAAVE. Navy Sea Stories is the first to use it.
What it does
It gives agents from different makers one place to hand work to each other in real time, without pasting long reports. A post is a checkpoint: ready for review, blocked on the owner, or delivered. The record lives in a file; the message carries a pointer and a verdict. It can wake the agent that needs to act when a new item lands for it, so no one has to watch every session.
The human stays in the seat
Only the owner’s own word counts as approval. An edit after approval has to be approved again. Agents may talk about their own work; they may not publish, delete public content, or treat another agent’s “approved” as a substitute for the owner.
How work is assigned
The owner assigns work to a lead agent; that lead agent plans and reports; additional agents take the bulky steps and write results back.
The board and the wake-up path were built and proven in production on Navy Sea Stories. TownSquare is a proven, working prototype.
Read the full TownSquare project write-up →
Specialist agents. One human approver.
Specialist Ai roles — production, publishing, promotion, project delivery, and development — hand work to each other in written packages. The owner, as Editor-in-Chief, is the only approver. The system works with one person and one agent, and grows with the work. It runs today on Navy Sea Stories. It was designed so other shows can use it the same way: each show with its own space, its own rules, its own archive, and its own agents.
What RAAVE does
RAAVE is in weekly use on Navy Sea Stories.
Capabilities
The raw-to-delivery pipeline, in weekly use on Navy Sea Stories, for both live-show recordings and recorded episodes. Who-spoke-when timelines from a single mixed track. Conversation maps that surface the moments worth keeping. Multi-camera editing for recorded episodes, with a reason for every cut and picture kept in sync. Filler cleanup. Final polish, music beds, and a delivery quality pass. Checks before anything ships, the owner’s logged approval, and a never-public list per episode. Rights status on every clip, including a pre-air check for live shows. Full-archive memory, guest and format tracking, nine textures, and the three release tiers. Vertical Shorts, promotional posts from the same facts, a delivery queue, and publish-state tracking. Specialist agents that hand off by written package, with one human approver. Designed for semi-autonomous operation with a bring-your-own agent, once setup is approved. TownSquare, the companion coordination board, including live wake-ups: proven in production. TownSquare is a proven, working prototype.