Terms used across engineering docs. Prefer these definitions over ad-hoc re-explanations in each page.
| Term | Definition |
|---|---|
| Runtime harness | .sdlc/ plus materialization — operational infrastructure for governed cognitive execution |
| Runtime adapter | {specialization_layer}/ — binding to a specific agent environment (Cursor, Claude, etc.) |
| Materialization | Deterministic projection of DSL declarations into verifiable files, gates, and manifests |
| Procedural DSL | .sdlc/sdlc.yaml — executable operational specification |
| Playbook | Atomic domain procedure (.pb.yaml) — provisioned on demand, not loaded at session start |
| Skill | SDLC orchestration composition (.cursor/skills/) — may declare playbook dependencies |
| Gate | Deterministic script verifying a stage transition; agent claims do not satisfy gates |
| Hydration scope | Fixed INDEX sections loaded at session start; playbooks excluded until provision |
| Worktree | Isolated git checkout per Plane ticket — mandatory for feature/fix implementation |
| Cognitive trace | Run manifest + trace UI — where the engineering process is visible |
| Runtime trace | events.jsonl — what the agent did (tools, hooks, spans) |
| target_root | Application path bound by workspace config (e.g. app/) |
| Baseline | Versioned SDLC pack snapshot — consumer vs authoring layers (ADR-014) |
| Learn pipeline | /sdlc:learn — acquire domain capability as registered playbooks without contaminating agents |
If a term is missing, add it here before introducing it in another doc.