Skip to content

Runs and collaboration

A runtime loads the persona, checks available capabilities, and coordinates work through the selected harness. The harness handles agent reasoning and tool use. The workspace owns the run state, accounts, permissions, and shared history. Gabriel captures the run’s playbook definitions and limits at start, then checks current permissions before dispatch. The way a runtime connects to a harness is implementation-specific in this draft. See the run sequence.

Surface Role in a run
Context Shared pages, organization context, and available team knowledge. The team can work from a brief alongside the goal.
Conversations Team discussions and threads that people and authorized agents can participate in.
Outputs Shared results and artifacts produced by work, such as a brief or an accepted record update.
Activity The history of runs, decisions, and accepted outputs, including links back to relevant records and evidence.

For example, a teammate can open Lane’s accepted outreach result, follow the link to the producing goal, and inspect the approval for that send. A result and its evidence are workspace data. The persona describes the steps and fields that can produce them.

Live sync delivers resource changes to open views. Presence describes who is online and where they are working. In Gabriel’s Studio, following another member can change which view you see. Actions still require your own permissions. Presence is a proposed profile in this draft.

See capability reporting and binding, live sync, and presence and following.

A goal has started preparing a brief. One teammate opens the waiting approval while another follows their view. Each sees records their own role can read. The authorized reviewer inspects the proposed destination and content, then makes the decision from their own session.

Work → current tasks and attempt state
Approvals → proposed effect and reviewer decision
Outputs → accepted artifacts or published records
Activity → events and diagnostics used to investigate the run

Reload authoritative run and approval state after a lost connection. Inspect the existing attempt before trying again. When delivery is uncertain, the operator verifies the destination before authorizing a retry. Following and presence remain session context.

See run states, context and conversations, and live sync and presence.