Follow Lane, a persona for introductions and pilots, in Gabriel Operator’s Playbook Studio. The tour shows how one team works with its agents, connectors, approvals, and records.
Open a persona in Gabriel and choose a team. Studio shows the team in up to ten tabs. Each view combines definitions from the persona with live data from the workspace.
Choose a tab to see what people do there, what it reads from the folder, and which part of the specification covers it.
Playbook Studio · Prospect to pilot
Prospect to pilot · 7 agents
Lead researcherexa
→
Outreach coordinatorgmail · approval
→
Meeting schedulergooglecalendar
→ …
delegates after each milestone ↓
Pilot briefshared page
CRM stewardnotion · approval
Kim
Goal · plan reviewed by Sam
Run one prospect-to-pilot journey
Research and qualify one prospectLead researcher
Send the reviewed outreach emailWaiting for your approval
Book the agreed meetingMeeting scheduler
Capture the consented meetingMeeting scribe
Pilot brief
Written by Sam
Lead researcher · live section · updated 2 min ago
CRM steward proposes an additionAcceptDismiss
Outreach coordinator · send · write
Send one reviewed email
To
prospect@northwind.example
Subject
A two-week pilot for Northwind
Account
Gmail · Sam
ApproveRequest changes
ChatsMeetingsCalendar
In a call with Sam, Prospect to pilotteam in call
Kim@Outreach coordinator did Northwind reply?
Outreach coordinatorYes, this morning. They asked for Tuesday. The Meeting scheduler is checking times.
Values are write-only. Each is sent only to the service it was saved for.
14runs
31credits
6approvals
Sam approved “Send one reviewed email”
Outreach coordinator sent 1 email through Gmail
CRM steward published a milestone to Pilot prospects
Canvas
See the team as a graph: each agent, the playbook it runs, who hands work to whom, and the service each one needs. Open an agent to read or edit its playbook. Colleagues in the team show as cursors, and you can follow one to see exactly what they see.
From the persona folder
teams[].bots, teams[].connections (hand-offs and delegations) and playbooks[].requirements in assets/studio-teams.json.
Give the team a goal. It plans the work from its playbooks, you review the plan before anything starts, then follow each run step by step. Credits and model calls are capped per run.
From the persona folder
The playbooks’ steps, inputs and outputs, and automationPolicies for work that repeats on a schedule, each with maxCredits and maxModelCalls.
The team conversation, where people and agents talk. Tag a playbook with @ and only that one answers. Start a call: the team joins as a voice, answers when called by name, and rings people in. Meetings and a calendar sit alongside.
From the persona folder
Nothing beyond the team and its playbooks.
Kept by the workspace
Messages, calls, meetings and read marks. Updates arrive live.
The views people use to follow and move the work, here a grid of pilot prospects with each one’s stage. Custom apps from a creator’s registry are installed here too.
From the persona folder
Team resources: the app app.lane.prospect-pilot over the list list.lane.prospect-pilot, whose pipeline has 12 stages.
Kept by the workspace
The records, and the installed packages with their saved state.
The tour uses Lane. Its folder holds a library of 17 playbooks and two teams. The tour shows the second team, Prospect to pilot.
persona-lane/ the persona folder
Playbook library 17 playbooks
meeting-watcher
brief-researcher
briefing-caller
meeting-scribe
pilot-research
and 12 more
Shared by every team in the folder.
Meeting follow-through team
Agents
6, each runs one playbook
Apps
3 views over lists
Lists and pipelines
1 list, 1 pipeline
Prospect to pilot team
Agents
7, each runs one playbook
Apps
1 view over a list
Lists and pipelines
1 list, 1 pipeline
App registry outside the folder
Starts in a teamBuilt there, because that team needs it.
Kept in a registryIts creator’s own, with numbered revisions and a fingerprint.
Installed into a workspaceThe creator selects a team they can manage and chooses who can open the app.
Prospect to pilot has seven agents. Each runs one playbook from the library, and each declares the services it may call:
Agent
Needs
Steps that wait for approval
Lead researcher
exa: search
None declared
Outreach coordinator
gmail: send, reply, reply-status
Send
Meeting scheduler
googlecalendar: availability, book
None declared
Meeting scribe
recall: schedule-consented, completed-transcript
Capture
Follow-up writer
gmail: send, reply, reply-status
Send
Onboarding reviewer
Nothing
None declared
CRM steward
notion: update, through the team’s app
Notion update
The first six hand work to each other in order. Each of them also delegates to the CRM steward after every milestone, so the record is kept up to date as the journey goes.
The team’s one app, Pilot prospects, is a grid over the list list.lane.prospect-pilot. Its pipeline has 12 stages, from Identified through Contacted, Meeting booked and Onboarding review to Converted, plus Dead and Needs you.
How the team takes one prospect from research to onboarding, as the people on it see it. Each step names the tab where it happens; choose it to open that tab in the tour above.
Sam connects Exa, Gmail, Google Calendar and Recall.ai, each with Sam’s own account. Notion is connected once, for the team’s app, because the CRM steward writes there for everyone.
Sam gives the team its goal. The team plans the work from its seven playbooks. Sam reads the plan and starts it.
The Lead researcher qualifies one prospect and hands the result to the Outreach coordinator. Kim, who is also on the team, follows Sam’s view to watch.
The Outreach coordinator drafts the email and stops: its send step needs approval. Sam reads the exact email, the recipient and the account it will use, and approves it.
Kim asks in the team conversation, “@Outreach coordinator did Northwind reply?”. Only the tagged agent answers. Later Sam and Kim talk it over on a call, and ask the team out loud what to do next.
The prospect’s row in Pilot prospects moves on as the work does: Contacted, Responded, Meeting booked. A step that needs a person moves the row to Needs you.
The team keeps a shared brief. Sam writes the background; the agents keep their live sections current and propose additions, which Sam accepts or dismisses.
The Meeting scribe captures only the meeting the prospect consented to, after approval. The Follow-up writer sends a reviewed follow-up. The accepted notes and the follow-up appear in Outputs.
Every run, what it cost and who approved each step is in Activity.
The same round, drawn as the parts of the format:
ConnectorAn operation contractrequirements
AgentAn agent with a playbookbots
ListShared recordsresources · list
AppThe view people useresources · app
1An agent’s playbook reads from a service through a connector requirement.
2The agent works on what it read and prepares a result.
3A step that needs approval waits for a person’s decision.
4A publish step writes the accepted fields to the team list.
5The runtime announces the change, and every open view of the list updates.
6A person moves the record on in the app. The transition can start the next playbook.
Studio is built for several people and several agents on one team at the same time.
Presence. Everyone working in the team shows as an avatar, and on the canvas as a cursor with their name. A click shows as a ripple in their colour.
Following. Choose someone’s avatar to follow them. Your screen shows what theirs shows: the same tab, the same agent or page open, the same part of the canvas at the same zoom. Following only shows; it never starts anything for you, and your own access still applies.
The team conversation. One conversation per team, beside every tab. People talk to each other; an agent answers only when it is tagged. Pictures can be attached or pasted.
Calls and meetings. A call puts the team in as a voice. It answers when someone calls it by name, asks a playbook to answer in its own voice, and rings people in. Anyone in the call can take the team out and bring it back. Meetings have their own call and their own conversation.
Shared pages. Pages in Context are edited together, live. What people write and what agents maintain stay apart.
Agents as colleagues. Everything Studio does is also a tool on the persona’s server. The Coach, Gabriel’s assistant beside every page, and any connected agent can create a team, add an agent, start a goal or read why an agent is blocked, with the same permissions and the same approvals as a person clicking.
The format covers the parts these features read: teams, playbooks, requirements, lists and apps. Apps and connectors specifies them, together with the event stream that keeps every open view current and the shape of presence.
Choose a persona to trace one workflow from input through preparation, human review, and outcome. The examples summarize the inspected workspace definitions and related validation notes. They identify what the workflow can prepare or rehearse and where a live operation depends on an approved connection or a human handoff.
This illustrated walkthrough traces Lane from its files in Git to an approval in a running workspace. The homepage walkthrough shows how playbooks compose into teams and personas.
What does it take to hand real work to an AI?
Scroll to see how a persona is put together.
Start with an assistant.
A model, a prompt and a few tools. That is enough to answer questions.
A role needs more.
To do a job it has to know the domain, keep records, follow a procedure, ask before it acts and prove it still works.
When definitions live in a platform’s settings, it is harder to review and reuse them.
Put the domain definitions in a folder.
A persona is defined in Git with a SKILL.md and a set of declarative definition files.
The root files and linked definitions can be reviewed together in Git.
Pin linked definitions.
Portable linked definitions have stable resource keys. The registry records their fingerprints and revisions. The generated workspace graph describes the wider authoring repository.
A runtime checks the fingerprint first and refuses anything that does not match.
Give it a team.
The Studio file declares teams, their agents and playbook pins, connector requirements, and list-backed views. A goal runs in the team’s workspace.
A custom interface is a separate package. A workspace installation binds it to a team’s accounts and data.
Bind it at run time.
The definition declares the required capabilities, connector operations, and approval roles.
The workspace supplies them. Each installation can bind its own model, accounts, and people.
Ask before acting.
A playbook can stop at a step until a person decides.
A runtime that cannot enforce that holds the step. It does not carry on without the answer.
Run it where you need it.
Hosted, on your own hardware, or offline on a device.
Each runtime reports which steps it can execute and blocks the rest. It never swaps in something else.