Intensive Concept Brief Kit — Terminology
Locked Terms (Practice Builders Language System)
| Term | Means | NOT |
|---|---|---|
| The Intensive | 3-session, build-along workshop. Entry event. | Bootcamp, course, training, webinar, masterclass |
| The Groundwork | Pre-work — setup + foundation building before an Intensive | Onboarding, homework, prerequisites |
| The Field Guide | Step-by-step companion for Intensives and monthly builds | Workbook, handbook, manual, playbook (Ronnie's) |
| The Site Survey | Entry assessment — 10 questions across 3 areas | Quiz, diagnostic (that's the AOS term), assessment (too generic) |
| The Build Order | Personalized priority sequence from the Site Survey | Roadmap, curriculum, learning path |
| The Toolkit | Skill/tool library that grows monthly | Library, marketplace, prompt collection |
| Practice Growth OS | The full system participants build (Practice Brain + skills) | Platform, app, software |
| Practice Brain | CLAUDE.md + reference files — the foundation skills read from | Database, profile, account |
| Skill | A Claude .md file the user uploads and runs | App, tool, bot, GPT, template, prompt |
| Install | Adding a skill to Claude (one-time) | Set up, configure, onboard |
| Run | What the user does with the skill | Use, try, test, execute |
| Build | What participants do in sessions — install + customize + run | Learn, practice, train |
| Practice | The user's business | Company, firm (OK occasionally), business (too generic) |
| Practice owner | The person in the room | Founder, entrepreneur, solopreneur, business owner |
Metaphor Family
Building / construction — professional end. Architects and builders who plan and execute. No language borrowed from Ronnie (Agent OS, Brain Builder). No language borrowed from AOS (deploy, constraint, capability — those are the premium tier).
Session Voice
The Intensive is teaching through building, not lecturing.
- Sessions are guided builds, not presentations
- "Here's what we're building" not "Here's what I'm going to teach you"
- Every session produces a working artifact they can use that day
- Kathryn demonstrates on her own data first, then everyone builds on theirs
- Quick wins are shared — social proof builds inside the room
Concept Brief Voice
The concept brief is an internal validation document.
- Direct, structured, decision-oriented
- Tables over paragraphs
- Flag gaps explicitly — "Gap" and "Content interview required" are the right words
- IP sourcing must cite specific file paths
- Methodology depth ratings on every source (Deep/Partial/Needs Review/Gap/Reference)
Forbidden Constructions
| Don't Write | Write Instead |
|---|---|
| "Students will learn..." | "They build [specific artifact] on their own data." |
| "This module covers..." | "Session 2 — Prove: run the Proof Engine on a completed engagement." |
| "Key takeaways include..." | [State the artifact they walk away with.] |
| "Interactive workshop experience" | "Build-along. Everyone builds on their own data." |
| "Cutting-edge AI tools" | "Claude skills installed on their machine." |
| "Transform your practice" | [Name the specific outcome.] |
| "Comprehensive system" | [List what's in the system: brain + 3 skills + deployment plan.] |
Two Vocabularies
The Intensive Concept Brief uses Practice Builders vocabulary (above). When referencing AOS concepts for internal context (IP sourcing, methodology depth), use AOS vocabulary. But participant-facing language in session titles, promises, and artifacts uses Practice Builders vocabulary only.
| Context | Vocabulary |
|---|---|
| Session titles, promises, participant artifacts | Practice Builders (build, install, run, practice, toolkit) |
| IP sourcing, methodology notes, internal flags | AOS (deploy, constraint, capability, diagnostic) |
| The dual conversion pitch at Session 3 close | Both — PB for "keep building," AOS for "build it for me" |