Context: Governance
Terms describing rule ownership, precedence, and policy controls in Spec Kitty.
Charter
ADR (Architectural Decision Record)
| |
|---|
| Definition | Immutable record of a significant technical/domain decision, with context and consequences. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Location | docs/adr/<era>/, filed by the era of the decision (1.x to 4.x); new ADRs land in docs/adr/4.x/ |
Glossary Strictness Policy
| |
|---|
| Definition | Governance rule for how semantic conflicts are treated (warn vs block) under each strictness mode. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Default | medium |
Clarification Burst Policy
| |
|---|
| Definition | Intended rule for limiting clarification interruption by prioritizing the highest-impact conflicts and capping the prompts per burst. No cap or prioritization is implemented today: the clarification step prompts for every unresolved conflict in turn (src/glossary/clarification.py). |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Cap | None implemented (an earlier design named 3 prompts per burst) |
Precedence Rule
| |
|---|
| Definition | Ordering used when policy settings conflict. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Operational order (strictness) | CLI override > step metadata > mission config > global default |
Pack Level
| |
|---|
| Definition | The level a Charter Pack occupies, declared by the pack_level field in the pack’s pack.yaml — one of built-in, org or project, in ascending precedence (ADR 2026-10-11-2). The level is no longer inferred from where a pack is wired in; a pack states its own level. The three level names have one authority, kernel.pack_tiers, and the level token and the provenance/layer value share a single spelling, built-in (the former no-hyphen builtin provenance spelling is folded away). Loading refuses a pack whose declared level disagrees with where it is configured (PACK_LEVEL_MISMATCH). A pack.yaml that omits the field, or an org pack with no pack.yaml, is reported as PACK_LEVEL_MISSING. During the deprecation window of ADR 2026-10-11-2 that is a non-blocking diagnostic: loading warns and uses the configured level, and charter pack validate reports a pack.yaml without the field as an advisory. Once the window closes it becomes a refusal. |
| Context | Governance |
| Status | canonical |
| Applicable to | 4.x |
| Related terms | Charter Pack, Precedence Rule |
Charter Interview
| |
|---|
| Definition | A guided question-and-answer process that walks the HiC through their project’s preferences, constraints, and artifact selections. Answers are saved to answers.yaml and used to compile the charter. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Related terms | Charter, Charter Compiler, Human-in-Charge (HiC) |
Charter Compiler
| |
|---|
| Definition | The processor that takes the HiC’s interview answers and their selected doctrine artifacts, and combines them into a finalized charter document and supporting governance files. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Related terms | Charter, Charter Interview, Charter offering |
Governance Resolution
| |
|---|
| Definition | The result of checking the HiC’s active charter against the charter offering — confirming that the referenced paradigms, directives, and tools actually exist and are compatible with each other. |
| Context | Governance |
| Status | canonical |
| Applicable to | 1.x, 2.x |
| Related terms | Charter Compiler, Charter offering |
Activation Chokepoint
| |
|---|
| Definition | The single activation filter applied by charter.activation.resolver.ActiveCharterService (the activation-aware wrapper). It enforces the project charter’s per-kind activation state on a doctrine service’s paradigms, procedures, and agent_profiles surfaces, so every profile-resolving path passes through one consistent filter rather than re-implementing activation logic. The factory charter.activation.active_charter_service_builder.build_active_charter_service is the single construction seam that routes callers through this chokepoint. |
| Context | Governance |
| Status | canonical |
| Applicable to | 3.x |
| Related terms | Activated vs Available Profile, Abstract Base Profile |
Activated vs Available Profile
| |
|---|
| Definition | An available profile is any agent profile present in a layer of the charter offering (built-in, org pack, or project layer). An activated profile is an available profile that the project charter has explicitly turned on via activated_agent_profiles. Three-state semantics: when the key is absent, every available profile is activated; an explicit empty set activates none; an explicit set activates only the listed IDs. Since 4.0.0rc8 a profile listed in deactivated_agent_profiles (an Exclusion) is subtracted from that set unless an org pack requires it (Effective Set). Only activated profiles are directly selectable by default surfaces; available-but-not-activated profiles surface only under --all/--show-available. |
| Context | Governance |
| Status | canonical |
| Applicable to | 3.x |
| Related terms | Activation Chokepoint, Abstract Base Profile |
Effective Set
| |
|---|
| Definition | The artifacts of one kind that are actually in force: the kind’s allow state minus its Effective deny. The allow state is the activated_<kind> list when present, nothing for [], and, when the key is absent, every available artifact (for skill, the org-required ones plus the built-in defaults, empty today). The effective deny is the kind’s Exclusions, matched by stem, declared id or DRG URN, minus the Required floor, so a deny never removes an org-required artifact. The governance selection overlay follows the same rule: selected_<kind> plus the required floor, minus the effective deny. Both are computed once, in charter.activation, from the Activation ledger (ADR 2026-10-19-1 Decision 2). |
| Deny-writer rule | Four explicit operator commands change an exclusion list: charter deactivate <kind> <id> adds the id; charter activate <kind> <id> (also with --only) removes it; charter activate ... --cascade ... --include-deactivated removes the ids the walk reaches; charter activate --preset <name> --force removes the ids the preset lists. A fifth recorded choice, the project-intent rename (#6565), only moves one entry from the legacy mission-type-scope-directive stem to project-intent-directive and never adds or removes a denial (DenyListChoice, src/charter/activation/activation_ledger.py). Presets without --force, the interview, org-required promotion, synthesis, mission-type seeding and every migration apart from that rename leave exclusions alone; a denied id they list stays out and is named in a warning. The activation-ledger write refuses (DenyListWriteRefused) any change to an exclusion list made without one of these choices. |
| Context | Governance |
| Status | canonical |
| Applicable to | 4.x |
| Related terms | Activation ledger, Exclusion, Effective deny, Required floor, Activated vs Available Profile |
Abstract Base Profile
| |
|---|
| Definition | An agent profile that is referenced via a specializes_from lineage edge but is not itself activated in the project charter. It acts as a shared-element store that concrete profiles inherit from; it is not directly selectable as a runtime persona. Resolving a profile whose lineage traverses an abstract base (an ancestor not in the activated set) yields a lineage warning rather than an error. |
| Context | Governance |
| Status | canonical |
| Applicable to | 3.x |
| Related terms | Activated vs Available Profile, Activation Chokepoint |