Context: Identity
Terms describing who performs work and who owns semantic decisions.
Agent
| |
|---|
| Definition | Logical collaborator identity used in workflow coordination (for example implementer, reviewer). |
| Context | Identity |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Related terms | Tool, Role |
Role
Agent Profile
| |
|---|
| Definition | Structured logical collaborator identity and behavior guidance, identified by a stable profile ID, that can govern assignment, handoff, role-scoped behavior, and tool-native custom-agent/subagent projection. |
| Context | Identity |
| Status | candidate |
| Applicable to | 3.x |
| Examples | architect-alphonso, researcher-robbie, implementer-ivan, reviewer-renata |
| Use when | Describing who the collaborator is, what role boundaries it follows, and how it should be selected or handed off to. |
| Do NOT use when | Describing the generated file or host configuration that exposes the profile to Claude Code, Codex, Copilot, Cursor, Windsurf, or another tool; use Tool Surface instead. |
| Related terms | Agent, Role, Tool, Authored Intent, Resolved Binding |
Authored Intent
| |
|---|
| Definition | Who or what a work package was designed to be run by — the authored/recommended role, agent_profile, and model. Authored once at tasks-finalize; frontmatter-canonical and static for the life of the WP; never mirrored into events. |
| Context | Identity |
| Status | candidate |
| Applicable to | 3.x |
| Use when | Describing the recommended assignment a WP was planned with — the design-intent for who should run it. |
| Do NOT use when | Describing who or what actually resolved and ran the WP; that is the Resolved Binding, which is event-sourced. Never treat authored intent as “what ran”. |
| Canonical authority | Exactly one source per datum — static → frontmatter. (Umbrella rule shared with Resolved Binding.) |
| Related terms | Resolved Binding, Agent Profile, Role, Field-authority ADR |
Resolved Binding
| |
|---|
| Definition | Who or what actually resolved and ran a work package at a given lifecycle transition — the resolved role, agent_profile (+agent_profile_version), model, and provider. Event-log / snapshot-authoritative, folded latest-wins; it shifts across the lifecycle (implementer→reviewer, model swap). Produced by resolve_profile / resolved_agent() / the dispatch resolution — never a re-read of the frontmatter string. |
| Context | Identity |
| Status | candidate |
| Applicable to | 3.x |
| Use when | Describing who or what is actually running a WP at a lifecycle transition, or the latest-wins reduced value across pick-up/claim/reassign. |
| Do NOT use when | Describing the planned/recommended assignment; that is the Authored Intent, which is frontmatter-canonical. A WP with no resolved-binding events has an empty resolved binding — never the authored value masquerading as resolved. |
| Canonical authority | Exactly one source per datum — dynamic → event log (reduced snapshot). (Umbrella rule shared with Authored Intent.) |
| Related terms | Authored Intent, Agent Profile, Role, Field-authority ADR |
See the Agent Profiles reference for the full built-in roster.
Audience Persona
Internal Audience Persona
External Audience Persona
Mission Participant
| |
|---|
| Definition | Human or tool-backed collaborator participating in a mission and, when execution is active, in one or more mission runs. |
| Context | Identity |
| Status | canonical |
| Applicable to | 1.x, 2.x |
Mission Owner
| |
|---|
| Definition | Participant responsible for tie-breaking unresolved semantic conflicts when collaborators disagree. |
| Context | Identity |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Rule | Tie-break only after normal participant resolution fails |
Human-in-Charge (HiC)
| |
|---|
| Definition | The human who remains responsible and accountable for decisions made during a mission. Agents assist and propose, but the HiC owns the final call. This principle ensures that automation supports human judgment rather than replacing it. |
| Context | Identity |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Related terms | Mission Owner, Collaboration Mode, HiC cross-reference |
engagement
| |
|---|
| Definition | The client relationship a Mission is carried out under — the real-world party whose work the Mission delivers. Because Missions are named after the work, a mission slug is a client engagement name, and so are the issue titles derived from it. The term therefore names a third party, not a unit of work: disclosing a mission identifier discloses who the client is. This is the whole ground of the project-egress consent boundary — only the project that owns a record may consent to that record leaving the machine, and inability to determine which project owns it is never consent. |
| Context | Identity |
| Status | canonical |
| Applicable to | 3.x |
| Examples | The local tracker providers (beads, fp) declare that what they send carries mission and engagement identifiers (LOCAL_SUBPROCESS_EGRESS_IDENTIFIER_KINDS in src/specify_cli/tracker/local_service.py): an issue title passed to the tracker executable can carry an engagement name. So the project’s committed tracker.egress key in .kittify/config.yaml must grant egress before they run, and an absent key refuses (src/specify_cli/tracker/egress_verdict.py). The hosted tracker path that named the term the same way was removed with the hosted surfaces in #6164. |
| Use when | Explaining why a mission identifier is confidential, or naming the party that a slug, branch name, worktree name or issue title discloses. |
| Do NOT use when | Referring to the unit of work itself — that is a Mission. Or to the project’s own identity — that is project_uuid, a UUID4 that spec-kitty init mints locally and writes to .kittify/config.yaml under project.uuid (src/specify_cli/identity/project.py); it names no client. |
| Related terms | Mission, Mission Owner, Mission Participant, project_uuid, repository_label |