02 — TERMINOLOGY: New Client Kit
Locked vocabulary for the New Client Kit. These terms have specific meanings in this system. This file wins if any other file uses different terminology.
Workspace Terms
| Term | Definition | NOT This |
|---|---|---|
| Client workspace | The entire repo for a single client. Contains all client-specific files, identity files, and directory structure. One workspace = one repo = one client. | Not "project" (a project is a subdirectory within the workspace) |
| CLAUDE.md | The identity file at the repo root. Tells Claude who the client is, what the engagement looks like, where files are, what frameworks to use, and what rules apply. The single source of truth for how Claude operates in this workspace. | Not "config" or "settings" (those are .claude/settings.local.json) |
| WORKFLOW.md | The processing instructions file at the repo root. Documents the weekly rhythm, pre-processing requirements, and reference material for the 9-step post-session cascade. The cascade skills in .claude/skills/ drive execution; WORKFLOW.md is the human-readable documentation. | Not "playbook" or "runbook" |
| Reference data | The canonical source of truth for all proper nouns — names, companies, tools, team members, transcript corrections. Lives in reference-data/. Overrides every other source. | Not "context" or "background" |
| Sessions folder | Permanent record of session transcripts, JSON analysis files, and recaps. Files land here and never move. One transcript + one JSON per session. | Not "inputs" (inputs is for non-session material) |
| Inputs folder | Staging area for external non-session material — client docs, status updates, constraint briefs. Files move to archive/ once processed (extracted and incorporated into a deliverable). | Not "sessions" or "uploads" |
| Drafts folder | Active production staging — email drafts, agendas, in-progress work. Files move to ready/ when finished or archive/ if abandoned. | Not "outputs" or "builds" |
| Ready folder | Finished work waiting to be sent or published. Files move to archive/ when delivered. | Not "outputs" |
| Archive folder | Final state for all retired, consumed, or abandoned work. Nothing leaves archive. | Not "trash" — these are records |
| Reference core | Four identity files (soul.md, offer.md, audience.md, voice.md) in reference/core/. Client portrait — who they are, what they offer, who they serve, how they sound. Separate from reference data. | Not "reference data" (reference data is proper nouns/tools/names) |
Brand & Customization Terms
| Term | Definition | NOT This |
|---|---|---|
| Brand kit | Three files that define a client's visual and verbal identity: HTML reference (brand guide), brand skill (production rules), brand QC (quality gate). All three live in brand/. | Not a single file — always 3 files |
| Client-specific skill | A markdown file in skills/ that extends a vault framework with client-specific rules. It references the vault framework — it does not duplicate it. | Not a copy of the vault skill |
| Client-specific QC | A markdown file in qc-agents/ that layers client-specific quality checks on top of vault QC. Additive, not replacement. | Not a standalone QC — always layers on vault QC |
Workspace Maturity Terms
| Term | Definition |
|---|---|
| Minimum viable workspace | A workspace that works using vault frameworks only. Has the full directory structure, CLAUDE.md, WORKFLOW.md, settings, reference data — but empty brand/, skills/, qc-agents/ directories. JB (Jenn Barr) is the live example. |
| Fully mature workspace | A workspace with brand kit, client-specific skills, and client-specific QC agents. RC (Ruben Cruz) is the live example. All three categories populated. |
File Naming Terms
| Term | Definition | Example |
|---|---|---|
| Preferred name | The client's first name, used as the prefix for all client-specific files. Lowercase in file names. | ruben, jenn |
| Client slug | 2-3 lowercase character code derived from client initials. Used only in the repo name. | rc, jb |
| Repo name | Always follows aos-client-XX pattern where XX is the client slug. | aos-client-rc, aos-client-jb |
Workflow Terms
| Term | Definition |
|---|---|
| Post-session cascade | The 9-step auto-advancing skill chain in .claude/skills/ that processes session inputs into all living documents. Steps: recap-email → recap-internal → recap-json → update-cpm → update-masterplan → update-projectplan → update-blueprint → draft-actions → session-agenda. Each step auto-advances to the next. Human review gate between every step. Installed during Mode 1 (Day 0 scaffold). |
| Cascade skill | A skill file in .claude/skills/[step-name]/SKILL.md that handles one step of the post-session cascade. Contains: what to read, what to produce, where to push, auto-advance instruction. At Day 0, references vault frameworks for processing logic. After Mode 3, may reference client-specific production skills instead. |
| Human review gate | A mandatory stop point between cascade steps. Claude produces output, then stops. Kathryn reviews and approves before the next step runs. Every step has one. No exceptions. |
| Session opener | The /start skill in .claude/skills/start/. Vault-inbox check, file move review, workflow position check, and kanban state confirmation before any production work begins. |
| Kanban flow | The file lifecycle: sessions/ (permanent) · inputs/ → archive/ · drafts/ → ready/ → archive/. Every file has a stage. Files move forward, never backward. |
| Weekly update | The processing sequence triggered by session inputs. Runs the 9-step post-session cascade. Kathryn says /recap-email and the cascade auto-advances through all steps with human review gates. |
| Processing session | A single Claude Code session where Kathryn processes a client's weekly inputs through the cascade. May process one or multiple session transcripts. |
Mode Terms
| Term | Definition |
|---|---|
| Day 0 | The day a client signs. Mode 1 runs on Day 0 to create the workspace. |
| Session 1 | The first advisory session with the client. Mode 2 runs after Session 1 to populate the workspace. |
| Maturity upgrade | Any Mode 3 action — creating a brand kit, adding a skill, adding a QC agent. Each is independent and incremental. |