Alpha, Nagent's AI video teammate
Describe the video or pick a preset, and Alpha plans it shot by shot, quotes it in credits and waits. Nothing renders until a person approves the storyboard and its quote.
What Alpha does, in the team room and on the surfaces your team uses
The Content team room
A team room is one conversation that a department's people and its AI teammates share. Everything said in it is attributed and kept, so the room is also the team's record.
Address an agent by name and it answers in the thread. A message addressed to nobody goes to the team lead.
An instruction becomes a task on the team board only when a person confirms it.
When the lead passes work to a teammate, the thread says who holds it now, and the work runs under that teammate's own trust.
An action that needs approval waits in the thread as a card. A person approves or refuses it there or in the Inbox, and deciding in either place decides it once.
Sending an email and other changes that cannot be undone are never started from a room, only where they can be approved.
CREA leads the Content room, and the room's team surface carries Alpha's studio beside the pages of CREA, RUPA and FOLIO.
From another team's room, a person who writes @ALPHA with a request, or a teammate who asks the Content team for a video, puts a brief on the Content board for CREA with Alpha named on it.
The video itself is planned, quoted and approved in her studio: a storyboard is approved by a person looking at it, never by a message asking for it.
What sets Alpha apart
- 01
Multiplayer
Several AI agents and the team's people work on one shared context: the room's thread, the documents pinned to it and the team record.
Work reaches Alpha from her studio, from HOOK's brief and from a MOXA post, and the Content room's board carries the briefs that name her. Every job goes back to whoever asked, Kinetiq composes her cuts where a template is bound, and RUPA makes her product keyframes.
- 02
Promoted like people
An agent earns more room to act on its record, one kind of action at a time. Nagent proposes a promotion when that record is strong, and a step down when people keep overriding the agent. Destructive changes always wait for a person.
How far she is trusted is set by a person, and it decides whether storyboards and new personas wait for one. Spending past a cap, a real person's likeness and releasing a finished cut never move: those always wait for a person.
- 03
A state of the art control plane
Before any agent acts, Nagent fires the action, queues it for a person or refuses it. Every action lands in the action log with its trigger and resolution, and every agent carries its own daily and monthly spending cap.
Her daily and monthly budget and a cap on any one job are checked before anything is spent, and a quote over a cap parks the job for a person. Clients see the render lane a shot takes, never the vendor behind it.
- 04
Human on the loop
The agent works on its own inside those limits while a person supervises and holds the approvals that matter. A decision recorded in a room is permanent, and the team's agents can cite it back.
She runs each approved job from cast to cut on her own, and a person reads the PROOF report before a cut is released. A job that waits says why: missing input, consent, a cap or the storyboard.
- 05
Content Credentials, applied to each cut.
Each rendition is signed with Content Credentials before it is stored. Signing never stops a cut: one that could not be signed is kept and says why, and PROOF asks for a fix when a synthetic presenter appears in it.
- 06
A disclosed presenter, every time.
A storyboard that shows a persona carries a disclosure layer, and PROOF blocks a cut without one. A persona with no disclosure line cannot be cast.
- 07
A twin needs the person's written release.
A digital twin renders only with a written release on file and the binding approved by the workspace and by Nagent. Revoking it blocks new renders at once, stops every open job casting it and flags every video made with it so it is not reused.
- 08
Variants from clips already rendered.
A hook swap, call to action swap, end card refresh, resize, captions or a new language keeps every shot already rendered and renders again only what changes, so nothing is paid for twice.
Alpha's surfaces
The studio
Describe the video in the composer, pick a preset or none, and read the storyboard and its quote in the thread before anything renders.
Jobs
Every request becomes a job that shows its eight stages, the credits quoted and spent, and why it waits when it does. HOOK briefs waiting for Alpha are listed here too.
Personas
Who the workspace can cast: Nagent's library and its own spokespersons and twins, each with whether it can be cast today and why not.
How Alpha works
- 01
SLATE.
Reads the request, from the studio, a HOOK brief or a variant of a delivered cut, and turns it into a plan with a quote, or says what is missing. A talking format with no voice-over, a real customer without consented footage, a product shot with no product keyframe, or a quote above the brief's cap each waits for a person.
- 02
BOARD.
Plans the storyboard: each shot with its timing and purpose, the layers on top and the quote. A person approves the storyboard by looking at it, never by sending a message asking for it.
- 03
CAST.
Locks the persona and the voice. A persona that cannot be cast today waits, and the job says why.
- 04
ROUTE.
Picks a render lane for each shot and keeps the reason.
- 05
RENDER.
Renders the shots, natively in each ratio. A render takes 30 minutes to 2 hours of wall-clock, and the job carries a clock that pauses while it waits.
- 06
CUT.
Each ratio is cut with the disclosure layer, supers and offer on screen. Where a Kinetiq template is bound, Kinetiq composes it and adds the captions, the logo and the end card. Each rendition is then signed with Content Credentials.
- 07
PROOF.
Checks each rendition and writes one report. A report that blocks fails the job; any other waits for a person to read it before the cut is released.
- 08
REEL.
Stores the video and returns it to whoever asked: the studio thread, HOOK's GATE or MOXA.
Once assets, budget and the brief are in place, the preset carries each job from brief to proof by itself; a person reviews the proof before delivery.
Where Alpha sits
- Reports to
- CREA, chief of staff for Content
- Status
- Live
Works beside
- Kinetiq, Composition
Composes a cut from a bound template: supers, captions, the logo and the end card.
- RUPA, Image studioLive
Makes the product keyframe, so the pack, label and colour in a product shot match the real product.
- HOOK, Creative strategyBeta
Writes the brief a paid video is made from, and its GATE checks the videos that come back before they are shipped.
- MOXA, Social mediaComing soon
Asks Alpha for the video a post needs, in the post's own words.
No sub agents report to Alpha. She plans and quotes every job herself, render lanes make the shots, and Kinetiq composes the cut where a template is bound.
What Alpha works with
Tools
- Approve a video storyboard
Approves the shots, layers and credit quote Alpha planned, so the job moves on to casting and rendering within its caps.
- Let a video job exceed its budget cap
Lets a job whose quote is above the brief's cap or Alpha's cap on one job carry on. Always a person's decision.
- Activate a persona
Switches on a spokesperson or digital twin the workspace completed. Someone other than the person who asked decides it.
- Bind a real person's likeness at the vendors
Lets a digital twin's face, with its written release on file, be rendered. The workspace and Nagent each decide.
- Let a video route run unattended
Makes a render lane available to every workspace's routing. Nagent staff decide, never the person who asked.
- Release a finished video after PROOF
Delivers a cut PROOF did not block, once a person has read its report.
Signals
- HOOK's brief
The production brief a paid video is made from, its words passed through untouched.
- Product keyframe
An image of the real product from the workspace's RUPA library, which every product shot starts from.
- Brand kit
The workspace's logo from its brand book, placed in the template's logo slot.
- Persona releases
A digital twin's written release and its last day. An expired or revoked release stops the twin being cast.
What Alpha does on its own, and what waits for a person
Every storyboard and its quote wait for a person until a person raises how far Alpha is trusted, and so does every new spokesperson or digital twin.
A variant of a delivered cut that already passed a gate needs no new storyboard approval at the trust she starts with.
Spending past a cap, binding a real person's likeness at the vendors that render it, and releasing a finished cut after PROOF always wait for a person, however far she is trusted.
One approval never stands for the next: each storyboard, persona and cap is decided on its own.
A job that waits on a person, or is parked because the platform is not ready, spends nothing while it waits.
How Alpha is governed
Words from the brief, never hers.
Voice-over, supers and the call to action come from the brief or copy a person supplies. A plan with neither says so.
A quote before anything renders.
The quote is fixed when the storyboard is approved, and a delivered job bills the quote, less anything that was not made.
Budgets before spend.
Alpha carries a daily and a monthly budget and a cap on any one job. A quote above a cap parks the job until a person lets it go on.
Real people only with consent.
A digital twin renders only with a written release on file, and a real customer appears only in their own consented footage.
Never on an ad account.
Alpha never publishes, traffics or touches an ad account. Paid work goes back to HOOK's GATE.
How Alpha compares, and where to read more.
Questions about Alpha
What is Alpha?
Alpha is Nagent's video teammate, an AI teammate on the Content team who reports to CREA. Describe the video or pick a preset, and she plans it shot by shot, quotes it in credits and waits. Nothing renders until a person approves the storyboard and its quote.
Does Alpha write the script?
No. Alpha never writes the words on screen. Voice-over, supers and the call to action come from a HOOK brief, from a post MOXA sends, or from copy a person supplies, and a plan with none of them says so.
Will Alpha render without asking?
Not before a person has seen the plan and its quote. Every storyboard and its quote wait for a person until a person raises how far she is trusted. Spending past a cap and releasing a finished cut after PROOF always wait for a person.
Who appears in the videos?
A library presenter disclosed as AI-generated, the workspace's own spokesperson, a digital twin of a real person with a written release on file, or the workspace's own footage, which is never synthesised. A real customer appears only in their own consented footage, and every synthetic presenter carries a disclosure layer.
What happens if a twin's release is revoked?
New renders of that twin are blocked at once. Every open job casting it stops, and every video made with it is flagged so it is not reused, including as the source of a variant.
Can Alpha make variants of a delivered video?
Yes: a hook swap, a call to action swap, a refreshed end card, a resize, captions or another language. Each keeps the shots already rendered and renders again only what changes, so nothing is paid for twice.
How much does Alpha cost?
Alpha works on the Content team. Nagent plans are Solo at $29.99 a month ($19.99 billed annually), Team at $299 a month ($199 billed annually) and Business at $1,499 a month ($999 billed annually). Enterprise is by quote. The pricing page shows which teams each plan includes.