The content studio
An AI persona with a real identity, a content pipeline, and a publishing calendar.
Scenario
An AI influencer or branded persona lives or dies on consistency: the same voice, the same opinions, the same running story, post after post. A chat window forgets; a Neuralis agent doesn't. The persona is an agent whose identity files are the character — and the studio around it is a pipeline that turns ideas into a publishing calendar.
The team
| Agent | Job |
|---|---|
| The persona | The character itself: voice, backstory, opinions, running threads — held in its identity files and refined every time it learns what lands |
| Producer | Turns the content plan into briefs, queues persona sessions, assembles final posts |
| Trend scout | Watches the niche with web research tools and proposes timely angles |
The persona's identity files are the studio's most valuable asset: the agent rewrites them as the character develops, and because they live in the agent's data zone they are versioned, searchable, and yours.
The wiring
- The content archive is a synced source — every published piece, every draft, every audience note. The persona searches its own history before writing, which is exactly how it stays consistent over hundreds of posts.
- Media generation attaches as skills: image and video generation services with public APIs are a skill script plus a scoped credential each. The persona asks for its own artwork; the key never appears in any prompt.
- Publishing goes through platform MCP servers where they exist, or through the machine desktop's logged-in browser sessions where only a web UI exists — drafts first, a human tap to send.
The rhythm
- Daily — Trend scout: niche scan, three angle proposals into the plan doc.
- Per calendar slot — Producer: brief the persona, collect the draft and media, stage the post for review.
- Weekly — Persona: a "character session" reviewing what resonated and updating its own identity files — the character grows on schedule.
The Calendar shows the whole pipeline as a rota; a missed slot is visible, not silently skipped.
Governance
Personas speak publicly, so the floor is review-before-publish: staged posts
need a human approval, the persona's outbound surface runs on a Safe
profile, and media spend sits under a per-agent spend cap. Be transparent
with audiences that the persona is AI where platform rules or law require
it — the audit log gives you the receipts of what was generated, when, and
under whose authority.
Extend it
Run several personas as several agents in one studio project — they share the production crew but never each other's identity files (per-agent data is private by default). The marketing team playbook is the natural superset when the persona serves a brand.