spec-kitty-glossary-context

# spec-kitty-glossary-context Maintain semantic integrity by curating the project glossary, detecting term drift, and ensuring that all mission artifacts use canonical terminology. Use this skill when the user wants to inspect, update, or enforce glossary terms. Do not use it for purely operational tasks like advancing the runtime loop or repairing an installation. --- ## How the Glossary Works The glossary is a **semantic integrity runtime** — a 5-layer middleware pipeline that intercepts mission step execution, extracts terms from inputs/outputs, checks them against stored definitions, and can **block generation** if terminology conflicts are unresolved. ### Data Model **Terms** have a `surface` (normalized to lowercase), `definition`, `scope`, `confidence` (0.0–1.0), and `status` (draft/active/deprecated). **Seed files** (`.kittify/glossaries/{scope}.yaml`) provide initial definitions. **Event logs** (`.kittify/events/glossary/*.events.jsonl`) record all runtime mutations as append-only JSONL. State is reconstructed by replaying seed files then events. ### 4 Scopes (narrowest wins) | Precedence | Scope | Use For | |:---:|---|---| | 0 (highest) | `mission_local` | Feature-specific jargon | | 1 | `team_domain` | Team/org conventions | | 2 | `audience_domain` | Industry/domain standards | | 3 (lowest) | `spec_kitty_core` | Framework terms (lane, work package, mission) | ### The 5-Layer Middleware Pipeline When a mission primitive executes (via `@glossary_enabled` ...