Skip to content

Context: Identity

Who is this for (2)

Context: Identity

Terms describing who performs work and who owns semantic decisions.

Agent

DefinitionLogical collaborator identity used in workflow coordination (for example implementer, reviewer).
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Related termsTool, Role

Role

DefinitionResponsibility assignment for a step or work package (implementer, reviewer, planner, etc.).
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Related termsAgent, Agent Profile, Authored Intent, Resolved Binding

Agent Profile

DefinitionStructured 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.
ContextIdentity
Statuscandidate
Applicable to3.x
Examplesarchitect-alphonso, researcher-robbie, implementer-ivan, reviewer-renata
Use whenDescribing who the collaborator is, what role boundaries it follows, and how it should be selected or handed off to.
Do NOT use whenDescribing 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 termsAgent, Role, Tool, Authored Intent, Resolved Binding

Authored Intent

DefinitionWho 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.
ContextIdentity
Statuscandidate
Applicable to3.x
Use whenDescribing the recommended assignment a WP was planned with — the design-intent for who should run it.
Do NOT use whenDescribing 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 authorityExactly one source per datum — static → frontmatter. (Umbrella rule shared with Resolved Binding.)
Related termsResolved Binding, Agent Profile, Role, Field-authority ADR

Resolved Binding

DefinitionWho 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.
ContextIdentity
Statuscandidate
Applicable to3.x
Use whenDescribing 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 whenDescribing 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 authorityExactly one source per datum — dynamic → event log (reduced snapshot). (Umbrella rule shared with Authored Intent.)
Related termsAuthored Intent, Agent Profile, Role, Field-authority ADR

See the Agent Profiles reference for the full built-in roster.


Audience Persona

DefinitionArchitecture-level stakeholder persona used to model needs, constraints, and success criteria for Spec Kitty usage and adoption. A doc page also names one as its reader in its audience: frontmatter.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Locationdocs/context/audience/
Related termsMission Participant, Human-in-Charge (HiC), Internal Audience Persona, External Audience Persona

Internal Audience Persona

DefinitionPersona representing contributors or runtime actors who directly shape or operate Spec Kitty from inside the delivery boundary.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Persona catalogInternal Audience Index, Lead Developer, Maintainer, System Architect, Spec Kitty CLI Runtime, AI Collaboration Agent, Project Codebase
Related termsAudience Persona, Mission Participant

External Audience Persona

DefinitionPersona representing evaluators and decision-makers outside the delivery boundary who assess Spec Kitty value, fit, and adoption risk.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Persona catalogExternal Audience Index, Project Owner, External Tech Lead Evaluator, External Architect Evaluator, External Product Manager Evaluator
Related termsAudience Persona, Mission Owner

Mission Participant

DefinitionHuman or tool-backed collaborator participating in a mission and, when execution is active, in one or more mission runs.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x

Mission Owner

DefinitionParticipant responsible for tie-breaking unresolved semantic conflicts when collaborators disagree.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
RuleTie-break only after normal participant resolution fails

Human-in-Charge (HiC)

DefinitionThe 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.
ContextIdentity
Statuscanonical
Applicable to1.x, 2.x
Related termsMission Owner, Collaboration Mode, HiC cross-reference

engagement

DefinitionThe 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.
ContextIdentity
Statuscanonical
Applicable to3.x
ExamplesThe 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 whenExplaining why a mission identifier is confidential, or naming the party that a slug, branch name, worktree name or issue title discloses.
Do NOT use whenReferring 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 termsMission, Mission Owner, Mission Participant, project_uuid, repository_label