Personas and workspaces
A persona describes the domain a team works in. It gives names and meanings to things such as prospects, meetings, and pilots, and declares the work the team can do. A workspace is an installation of that definition with its own members, records, connections, and run history. Two workspaces can load the same version of Lane and work with different accounts and prospects.
Map the organization’s apps
Section titled “Map the organization’s apps”Start with the domain specialist and the work the team needs to do. List the apps the organization uses, count them by process or team, and record which system is authoritative for each record. For each app, identify the record types, stable identifiers, fields, read and write operations, and the team or account that can grant access. Include gaps when an app offers a read but lacks a supported write.
For Lane, the inventory might connect these records to a shared model.
| App | Source record | Ontology entity |
|---|---|---|
| Notion | Prospect row and current stage | Prospect |
| Gmail | Outreach thread or reply | Outreach |
| Google Calendar | Scheduled event | Meeting |
The ontology gives each entity stable fields and defines relationships such as a prospect having multiple outreach messages and meetings. A feed or playbook mapping names the source fields and connects them to those definitions. The specialist confirms what the fields mean and which identifiers are safe to use when records from different systems refer to the same prospect. The workspace supplies the actual connections.
See the ontology contract and the two ways to use mapped data.
The portable definition
Section titled “The portable definition”| File | What it contributes |
|---|---|
SKILL.md |
Instructions for working in this domain. |
assets/chat-config.json |
Published persona and command references. |
assets/ontology.json |
Entities, attributes, and relationships. |
assets/studio-teams.json |
Teams, playbooks, pinned agent placements, and team resources. |
references/registry.json |
Stable keys, pinned revisions, and fingerprints for portable linked resources. |
references/workspace.json |
The generated authoring graph, when present. |
assets/persona-evals.json |
Expected behavior and cases that check it. |
See the folder tree, registry, definition files, and example files.
Importing and updating
Section titled “Importing and updating”The runtime resolves references and verifies each linked definition before use. Resource keys identify the same definition across installations. The runtime supplies local identifiers and stores operational state in the workspace. The draft describes import verification and capability reporting. Workspace binding is proposed.
In Gabriel, creating a persona, editing a workspace team, and publishing a persona revision are distinct actions. A workspace can adopt a published update while keeping its own records and accounts. The persona-builder and persona-workspaces skills cover those authoring and installation flows.
Example from inventory to installation
Section titled “Example from inventory to installation”Map one source
Section titled “Map one source”Start with a domain specialist and choose a question the workspace should answer. For an upcoming-meetings brief, identify the calendar as the source for meeting time and status. Give the ontology a stable Meeting entity, then map the provider’s event identifier and time into that definition. Record who owns the source and what people are permitted to see.
Organization calendar → Meeting ontology → calendar read requirement ↘ team list and meeting boardVerify a second installation
Section titled “Verify a second installation”Import the same reviewed persona revision into a second workspace. Bind a different authorized calendar. Run the same team goal and verify that the new team sees only its own source records and writes to its own destination. Repeat the check after adopting a changed definition.
See ontology, workspaces, and resource binding.