+ VisualBook
Publish here and the same manuscript is what VisualBook casts, storyboards and films. One source, two products.
A long-form video storybookLoomwright
Contact for pricingProduces
A finished book
Loomwright is where the book gets written. The manuscript sits beside the world it belongs to — the codex, the timeline, the maps, the ledger of who knows what — and the publish gate compiles your chapters into a real EPUB3 that the rest of the studio treats exactly like a book that arrived as one.
Requires Aardvark Studio Core (free) · Release 1.0.0
- Who it is for
- Authors writing inside a series world, and the editor, curator or co-writer who has to hold continuity with them.
- What it takes from the Core
- The workbench, the portfolio, the review queue and the Book Assistant. A book written here becomes an ordinary book in the Core the moment it publishes.
- What you have to run
- The Aardvark Studio server · An Anthropic API key
The change
Before, and after
Today, without it
- A manuscript in one tool, a series bible in a second, a wiki in a third.
- Continuity held in your head, and in a spreadsheet nobody else can read.
- A reveal you have to search the drafts for, because nothing records when the reader was told.
- An export for your editor that means re-writing the bible by hand.
With Loomwright
- The manuscript and the world are one document set, in one window.
- Continuity is checked against the ledgers rather than remembered.
- Publishing compiles the EPUB3 and hands the studio a book it already understands.
- Three exports leave the building — and the reader's copy knows what the reader may not.
How it goes
The path is short and it only goes one way. You write chapters in the binder, against a world that is already there. Continuity findings are raised as you write and cleared by a person, never by a heuristic. When the book is ready you press Publish…, and the compile turns your chapters into a real EPUB3 while the pre-seed hands the studio the structure you already decided by writing it.
On the far side of that gate your manuscript stops being prose in an editor and becomes an ordinary book — one the breakdown, the casting, the storyboard and the assembly stages work on exactly as they work on a book that arrived as a file. That is the whole point of the gate: everything downstream stops caring where the book came from.
Where it stops for you
2 gates, and who holds each
- 1
Continuity findings
Author or Curator
Findings are raised against the reveal and knowledge ledgers, and cleared by a person.
- 2
Publish to production
Author
The compile mints the EPUB3 and pre-seeds the chapter, scene and cast work the pipeline would otherwise derive again.
The world, once, for the whole series
A portfolio holds one world and every book in it reads the same codex. Entities, the timeline, maps and travel, graphs and boards — authored where they are used rather than kept in a document nobody opens twice.
- Entities with facets that change across the story
- A timeline the books are pinned to
- Maps and travel times that make a journey checkable
- Boards and graphs for the shape of a plot
Screenshot slot
Codex Navigator — the portfolio's world, one entity open
Continuity you can prove, not recall
The reveal ledger records when the reader was told something; the knowledge ledger records which point-of-view character knows it. Findings are raised against both and cleared by a person, so a contradiction is a decision rather than a discovery in a review.
- Reveal ledger — what the reader knows, and from which chapter
- POV knowledge — what each character knows, and when they learned it
- Findings raised against the manuscript as it stands
Screenshot slot
The manuscript binder with the scene rail
A manuscript with a publish gate
Write in the binder, snapshot as you go, and publish when it is ready. The compile renders your chapters into an EPUB3 and files it as the book's source; the pre-seed hands the pipeline the chapter list, the scene breakdown and the cast, so the studio does not derive again what you already decided by writing.
- Scene-level editing with autosave and snapshots
- Import an existing manuscript rather than retyping it
- Publish is a reviewed stage like every other
Screenshot slot
Continuity findings raised against the reveal ledger
Narration coverage, scene by scene
A book written here has no audiobook to lift narration from, so every authored scene carries a narration slot and one table shows which are filled. Synthesise them through your organisation's TTS endpoint, or record a narrator and import the result — both paths end in the same place.
- One coverage table for the whole book
- Per-scene slots, so a re-write re-narrates one scene and not a chapter
Three exports, and one of them keeps secrets
The series bible holds everything, for you and your editor. The reader or GM companion holds only what somebody who has read up to a book you choose is allowed to know. The JSON dump holds everything in a shape that is not ours, because a world you cannot take with you is not yours.
- Series bible — the whole world
- Reader/GM companion — spoiler-bounded to a chosen book
- JSON dump — portable, no lock-in
Sample output
What comes out of it
These are slots. No sample from a real title has been cleared for publication yet, and a mock-up of one would be the exact thing this page is trying not to do.
Screenshot slot
Codex Navigator — the portfolio's world, one entity open
Screenshot slot
The manuscript binder with the scene rail
Screenshot slot
Continuity findings raised against the reveal ledger
What it needs
Be clear about the hardware
- required
The Aardvark Studio server
One container, deployed once. Every product needs it.
- required
An Anthropic API key
Continuity analysis, world scaffolding and the assistant all call it.
- optional
A text-to-speech endpoint
Only if you want the studio to synthesise narration for authored scenes. Record a narrator and import the audio instead and nothing here changes.
- optional
A GPU
Nothing in Loomwright renders an image. No GPU is needed to write, publish or export.
Roles it adds
Who can do what
Loomwright Author
Writes the manuscript, narrates scenes, and publishes to production.
Loomwright Curator
Owns the world and the ledgers — the continuity half, separated on purpose.
Worth knowing
Loomwright's licence is enforced by visibility: without it the Authoring departments, panels and help topics are absent. Its HTTP routes are not seat-gated today, and the app shows no seat count for it.
With the others
Loomwright on its own is complete
Nothing below is required. Each line is what happens if you already own the other one.
+ LitCaster
A published book is a book LitCaster can cut an episode from, the same as one that arrived as an ePub.
A published podcast episode+ LookBook
Independent of LookBook. Neither needs the other.
A published casting styleQuestions
About Loomwright specifically
Ready to try it?
The Core is free and does not need this product. Start there, then ask us about a licence.
- Do I need a GPU to use Loomwright?
- No. Nothing in Loomwright renders an image. The server and an AI provider key are the whole requirement; a TTS endpoint is optional and only for synthesised narration.
- I already have a finished book. Do I need this?
- Probably not for that book. The free Core ingests an ePub and its audiobook directly. Loomwright is for the book that is not written yet, and for the world the next one has to agree with.
- Can I get my world out again?
- Yes. The JSON dump is an export of the whole portfolio in a shape that is not ours, and it needs no book open to produce.
- What happens to my manuscript if the licence lapses?
- The product is removed at the next sign-in and the Authoring surfaces go with it. A book you already published stays a book: the compiled EPUB3 is the Core's, not Loomwright's. Export the world before you let a licence go.