Where the ensemble runs.
Self-hosted. One image, signed, the same in development and production. You bring the goal and the provider account; everything below stays on your side of the wire.
| Surface | What it is | What it gives you |
|---|---|---|
| The workspace | One isolated tree per pursuit, built from a baseline. Destroy it and rebuild it, or promote it into a new baseline. | Context you can reset without losing the specialists or what you taught them. |
| The foundry | A domain brief goes in; a full specialist comes out: an oath written for that field, then hashed. | An accountable actor, not a role template. |
| The plan | Phases, steps, a line-up and the gates. Signed against the exact specialists it names. | Change the plan or a specialist and it will not run. |
| The run | A durable transcript, live telemetry, an operator stop, and spending ceilings that halt rather than warn. | You can watch it, price it, and end it. |
| The record | A hash-chained ledger of every action, cost and decision, with a per-run erase for data-subject requests. | “Who did that” always has an answer. |
Finished work, not chat.
A run ends in a document, an application or a page, rendered to your own brand kit if you upload one, with its sources, its cost and its author attached.
Briefings, memos, reports.
Rendered to a print master, with the masthead, the running feet and the marking your own kit defines.
Dashboards and trackers.
Interactive, shareable with colleagues, and exportable with their assets inlined.
Decks and one-pagers.
Built from the same templates a person would use, so what ships looks like the company.
Four things your team can do with it.
Documents that look like you sent them.
Upload your brand as a folder and every document that workspace produces carries your stylesheet, fonts and page setup, and the specialists writing it are told where your rules are.
Your brand kit →Workflows your own team writes.
Plans, specialists and integrations to your own systems, written as files, uploaded in the console, reviewed and approved before anything installs.
Your own packs →It runs where you say, at the version you chose.
One signed image on your servers, your storage, your provider account. No phone-home, no licence server, nothing that can reach in and stop it.
Self-hosted and control →Start a run from the software you already use.
A signed plan is an endpoint: post the inputs, poll or be called back, collect the document. Scoped keys, spend ceilings and the same record as a run started by a person.
Trigger it from your systems →See it on your own node.
We walk the console, open the posture view against a real deployment, and answer whatever your reviewer sends back.