02 — TERMINOLOGY: Kit Builder
Locked vocabulary for the Kit Builder. These terms have precise meanings in this system.
Kit Structure Terms
| Term | Meaning | NOT This |
|---|---|---|
| Kit | A 6-file production system that produces a specific type of deliverable | Not a template. Not a checklist. Not a single file. A kit is the complete system. |
| Golden example | The reference output — file 03. The standard that all future production is measured against | Not a template with blanks. It's a fully populated, finished deliverable. |
| Output skill | The production instructions — file 05. Step-by-step process for generating the deliverable | Not a description of what the output is. It's HOW to make it. |
| Quality checklist | The QC gate — file 04. Point-scored, with a pass threshold | Not a suggestion list. It's a gate. Below threshold = don't ship. |
| Start-here | The orientation file — file 00. What this is, operating modes, file inventory | Not instructions for production. That's the output skill. |
| Context | The inputs file — file 01. What data is needed, validation rules | Not background information. It's the specific inputs required to run the kit. |
| Terminology | The vocabulary file — file 02. Locked definitions for terms used in the kit | Not a glossary of general terms. Only terms that have specific meaning in THIS kit. |
Operating Mode Terms
| Term | Meaning |
|---|---|
| Mode 1: Build | Create a new kit from a golden example |
| Mode 2: Improve | Update an existing kit based on production experience |
| Mode 3: Convert | Turn a written protocol into kit format |
Self-Improvement Terms
| Term | Meaning | NOT This |
|---|---|---|
| Self-improvement loop | The cycle of: run kit → QC → fix kit → next run is better | Not autonomous self-modification. Kathryn approves changes. |
| QC failure | Output scored below the pass threshold on the quality checklist | Not "it's bad." It means specific checklist items failed with point deductions. |
| Manual fix | A change Kathryn made to the output by hand after production | A signal that the kit needs updating. Every manual fix should become a kit fix. |
| System suggestion | An improvement Claude identifies during QC or wrap-up that wasn't explicitly requested | Requires Kathryn's approval before implementation. Never auto-applied. |
| Propagation | When a change to one kit file requires changes to other kit files to stay consistent | Golden example changes often propagate to output skill and quality checklist. |
File Naming Conventions
| Element | Convention | Example |
|---|---|---|
| Kit directory | content/frameworks/[kit-name]/ | content/frameworks/blueprint/ |
| Kit files | NN-[kit-name]-[file-type].md or .html | 00-blueprint-start-here.md |
| File numbers | 00 through 05, zero-padded | 03-blueprint-golden-example.html |
| Golden example format | .html for HTML deliverables, .md for markdown deliverables | Matches the output format |
Relationship Terms
| Term | Meaning |
|---|---|
| Derives from | Kit B reads Kit A's output as an input. Blueprint derives from project plan. |
| References | Kit B points to Kit A for shared definitions but doesn't consume its output. |
| Coordinates with | Kit B calls Kit A during its process. New client kit coordinates with CPM and master plan kits. |
| Extends | A client-specific skill adds to a vault kit without replacing it. |
Terms NOT Used in Kits
These are SC / external terminology. We don't use them:
| External Term | Our Equivalent |
|---|---|
| Agent | Kit |
| 5-file structure | 6-file kit (we split context and terminology) |
| Process file | Output skill (file 05) |
| Agent builder agent | Kit builder (this kit) |
| Chief of staff | (TBD — separate concept) |