Studio
Studio is the authoring console for the agent estate: where a skill is written, an agent is minted, a team is laid out, a brief is published, and a running crew is watched.
It is a personal, home-scoped surface. Its peers are the data platform console, the security operations console and the core system console; Studio is the one an agent author lives in.
What is in it
| Section | What you do there |
|---|---|
| My Skills | Author and version executable capabilities |
| Cookbook | Browse the Algorithm Library and run a solve by hand |
| Field Manuals | Write, publish and read the briefs that admit an entity to a space |
| My Functions | Masks, transforms and lambdas, and the endpoints they publish as |
| My Blueprints | Agent archetypes, and the connectors available to them |
| My Models | The model catalog available to your work |
| My Agents | Mint an agent identity, and bless a standing one |
| My Teams | Compose billets and the management tree into a formation, then run it |
| Coding Teams | The built-in coding crew library |
| Crew Monitor | Live and recent crew runs |
| Identity & Keys | The cryptographic material behind your entities |
Three things worth calling out
Minting an agent is a real cryptographic act. The wizard creates a directory entity with its own key material, not a configuration row. What comes out is a principal that can be delegated to, authorized, audited and charged.
Blessing is separate from creating. Promoting a standing agent requires its own permission, and approving that promotion requires another one still. Whoever can propose is not automatically whoever can approve.
Team composition is visual and validated. Billets are edited as seats, the management tree is laid out directly, and skills are bound per seat. The authority contract is checked as you author, so a seat that asks for more than its manager holds is refused there rather than failing confusingly mid-run.
Field manuals
A field manual is the brief an entity reads on joining a space, and it applies to agents exactly as it applies to people.
Manuals resolve as an ordered union, workspace manual, then space manual, then role handbook, most specific last. Only published manuals brief, and a section with a grade floor is withheld from a reader below it.
A manual also carries a parts list: the tools its sections declare. Those are pre-loaded onto the reader's belt at session start. It is a floor, never a ceiling, and never a grant.
Four refusals on this surface are governed rather than errors, and are rendered with their reasons:
| Refusal | Why |
|---|---|
| Publishing below the grade floor | Publishing is an authority, and it has a bar |
| Flipping to published through an edit | Publication has its own path; it is not a field you set |
| Editing a section while published | Content is frozen. Withdraw, revise, republish, so new content passes the floor again |
| Reading a briefing outside your space | The brief is scoped to where you are working |
The frozen-while-published rule is the one that matters most: without it, a manual could clear the bar and then be quietly rewritten underneath it.
Gated twice, on purpose
Studio hides an entry you cannot use and refuses the direct URL. Hiding alone is not access control, and refusing alone leaves a menu full of dead ends. Doing both means the navigation tells the truth and the boundary still holds.
Related topics
- What you compose in the team editor: agent teams.
- What the Cookbook browses: the Algorithm Library.
- Watching a crew after you launch it: observing an agent.
- The capabilities you author: agent skills.