Policy mode controlling warning/block behavior for semantic conflicts.
Context
Execution
Status
canonical
Applicable to
1.x, 2.x
Modes
off, medium (default), max
Clarification Prompt
Definition
Targeted question emitted when conflict severity/confidence requires human input before continuing generation.
Context
Execution
Status
canonical
Applicable to
1.x, 2.x
Burst policy
Cap to top 3 high-priority conflicts per prompt burst
Generation Boundary
Definition
Point where text/code generation would begin and semantic gate policy is enforced.
Context
Execution
Status
canonical
Applicable to
1.x, 2.x
Block condition
Unresolved high-severity semantic conflict
Middleware Pipeline
Definition
An ordered chain of processing steps that run before a mission step produces output. Each layer in the chain can extract terms, check for semantic conflicts, gate generation, prompt the Human-in-Charge for clarification, or resume from a checkpoint.
A mechanism that lets a glossary pipeline pause at a generation boundary and pick up where it left off in a later session. The pause point and its context are saved so no work is lost.
An optional YAML file (.kittify/glossaries/{scope}.yaml) that pre-loads domain glossary terms before the runtime starts extracting new ones. Gives teams a head start by defining known terminology upfront.
The level of Human-in-Charge involvement during a mission step or workflow. Determines how much real-time oversight the HiC provides versus delegating to agents.
The HiC works alongside agents in real time — conducting interviews, pair-developing, micro-prompting, or making decisions as they arise. The HiC is present and actively steering.
Agents operate independently during execution, but the HiC reviews results at defined checkpoints before work is accepted or advanced. The HiC is absent during execution but present for review.
The agentic stack operates asynchronously without the HiC present. Work proceeds until a final Accept/Decline decision point, where the HiC returns to approve or reject the outcome. Also known as "AFK mode."
The resolved set of Charter and Doctrine artifacts active for an operation. Owned by the Governance bounded module. Resolved once per operation and passed down; never re-derived mid-operation.
The resolved set of workspace root, branch name, feature directory, and WP identity for an operation. Owned by core/execution_context.py (Open Host Service facade). Resolved once per operation via resolve_action_context; never re-derived from CWD by individual command surfaces.
The resolved set of infrastructure credentials and endpoints for an operation, including git remote URL, CI endpoint, and any external service tokens. Owned by the Execution module.
The Actor realized inside the Execution domain — the execution-bound realization of an Actor that performs actions within a mission run, producing or consuming communication artefacts (commits, PRs, comments). Named concept in docs only; no code type until a concrete actor-kind-mismatch bug triggers materialization.
Context
Execution
Status
canonical
Applicable to
3.x
Materialization trigger
First concrete actor-kind-mismatch bug, or first feature requiring cross-log (status/retrospective/run) actor identity join
A durable artifact produced or consumed by an Effector during a mission run (for example, a commit, a pull request, a review comment). Distinct from planning artifacts (spec, plan, tasks) which are produced before execution begins.
Context
Execution
Status
canonical
Applicable to
3.x
Examples
git commit, pull request, PR comment, CI run result