Persona
A persona is the Git-backed definition that a runtime imports. It names the domain, describes the work its teams can perform, and brings together their playbooks, data definitions, and review expectations.
Definition and installation
Section titled “Definition and installation”Portable files
Section titled “Portable files”A persona root identifies the domain and declares its teams and capabilities. The root Git revision covers local files. Linked repositories are resolved through references/registry.json. assets/chat-config.json carries the published persona configuration, while assets/ontology.json and assets/studio-teams.json describe domain objects and Studio teams when those features are present.
| Identity | What it identifies | When it changes |
|---|---|---|
persona.meeting-desk |
Portable persona definition | When intentionally creating a new persona identity |
| Root Git revision | Exact published snapshot | With a new publication |
| Workspace ID | One installation and its local state | When creating another workspace |
Workspace responsibilities
Section titled “Workspace responsibilities”Two installations of Meeting desk can import the same root revision and use different calendars and publication targets. The importing workspace resolves those bindings and assigns its own members. Run history, credentials, and approvals belong to each installation. An update changes the definition a future run can select. Existing run evidence retains the identity and revision it used.
Example configuration
Section titled “Example configuration”The Meeting desk fixture uses this portable envelope. The prompt supplies domain instructions. Calendar access comes from the playbook’s connector requirement and workspace binding.
{ "schemaVersion": 2, "resourceKey": "persona.meeting-desk", "publishedConfig": { "name": "Meeting desk", "systemPrompt": "Review upcoming meetings from authorized sources and share only approved summaries." }}See the full Meeting desk files, ontology, and what a workspace stores.