00 — START HERE: Knowledge Transfer
Setup and orientation for the Knowledge Transfer kit. Read this to understand what it is, what it does, what files it needs, and how to use it.
What This Is
The Knowledge Transfer kit captures the tacit knowledge locked in one person's head — the judgment, watch-outs, and standing rules a successor can't guess — and turns it into a transferable capture document: structured, every line traced to source, every gap flagged instead of guessed, and held to a QC gate.
It is the AI-native execution of the Knowledge Transfer Process (KTP) — specifically the "define each critical task in detail" exercise — with the capture done from a narrated recording instead of a hand-typed interview.
Audience: internal (advisor + the successor/operator who inherits the work). The capture doc is a working document the operator maintains, not a client deliverable. Format: .docx (rendered by the engine — hand-editable by non-technical operators in Word / SharePoint / Canopy). Lifecycle: living document — created once, updated as the successor runs it and the process evolves.
Operating Modes
| Mode | Trigger | What It Produces |
|---|---|---|
| Create | A key person is transitioning / a critical process lives in one head | A capture document per process or per subject |
| Update | The successor ran it; a gap got filled or a rule/watch-out changed | The same capture doc, regenerated (only the changed sections move) |
| Improve | You changed the output by hand, or QC missed something | Updated kit files (template, skill, or quality gate) |
Create
Inputs: a narrated recording/transcript of the expert doing the work (Educate & Delegate — "record the task as it naturally happens"), plus any prior doc (an old SOP, a partial blueprint). The engine mines the source into the template, flags every gap, and runs the gate. See 05-output-skill.md.
Update
The capture doc is living. Edit the content, regenerate — the engine is deterministic, so only the section you changed moves. See 05 (Update).
Improve This Kit
The self-improvement loop. After running this kit:
- Did I change the output by hand? → update the golden example + output skill.
- Did QC miss something? → update the quality gate (
04) + the engine'sqc.py. - Should the kit do something it doesn't? → update the output skill / template.
What This Does NOT Do
- Does not invent. Every line traces to the source recording or the prior doc. Unknowns are flagged ("Fill this out"), never guessed.
- Does not run the capture session for you. Getting a good recording is a facilitated step — see
06-facilitation-methodology.md. - Does not produce a client-facing deliverable. The capture doc is internal. (Client-facing progress = the Blueprint kit.)
- Does not replace the SOP build. It captures judgment; turning that into trained, deployed procedure is the deploy cycle.
- Is not domain-locked. The template ships a general capture structure; bookkeeping is the worked example. Adapt the labels per domain.
File Inventory
| # | File | What It Is |
|---|---|---|
| 00 | 00-start-here.md | This file — orientation, modes, loop |
| 01 | 01-context.md | Inputs per mode, validation, gap protocol |
| 02 | 02-terminology.md | Locked vocabulary + forbidden terms |
| 03 | 03-golden-example.docx | A filled, fictional capture (Northwind Trading Co.) |
| 04 | 04-quality.md | Two-gate QC — Gate 1 (mechanical, engine/qc.py) + Gate 2 (judgment checklist) |
| 05 | 05-output-skill.md | The production skill — mine → fill template → flag → gate |
| 06 | 06-facilitation-methodology.md | How to run the capture session (KTP Exercises 1–3) |
| — | engine/ | The executable engine: template.json (the structure) · build.py (renderer) · qc.py (the gate) · example-content.json |
| — | _source-*.docx | The original KTP methodology (archived source) |
This kit ships executable tooling. Unlike doc-only kits, the QC gate here is code (engine/qc.py) that the build is gated on — you cannot ship a capture that hasn't passed it.
Relationship to Other Kits
- Derives from the Knowledge Transfer Process (KTP) and pairs with Educate & Delegate™ (the recording is the input).
- Feeds the SOP / deploy cycle (captured judgment → trained procedure) and can feed the Blueprint (the client-facing version of "what's handled").
- Shares the flag-don't-guess + gate-as-code pattern with the AOS cascade's QC direction.
Confirm Understanding Before Executing
Before any capture run, confirm: "Here's the subject and the source I'm working from, and the template I'll fill. Does that match — am I missing a source?" Do not start production until the advisor confirms. A wrong capture that took ten minutes is worse than a thirty-second confirmation.
File Location
advisory-os-vault/content/frameworks/kit-knowledge-transfer/
00-start-here.md (this file)
01-context.md
02-terminology.md
03-golden-example.docx
04-quality.md
05-output-skill.md
06-facilitation-methodology.md
engine/ (template.json · build.py · qc.py · example-content.json)
_source-knowledge-transfer-overview.docx · _source-knowledge-transfer-implementing.docx