← Vault Index
Source: frameworks/kit-knowledge-transfer/02-terminology.md

02 — TERMINOLOGY: Knowledge Transfer

Locks the vocabulary used across this kit and in the capture document.


Terms Used in This Kit

TermMeaningNOT This
Tacit knowledgeThe judgment, watch-outs, and standing calls in one person's head — the part that isn't written downThe steps (those are usually already documented)
Capture documentThe kit's output — a structured, gap-flagged record of one person's/process's knowledgeAn SOP (steps), or a client-facing dashboard (Blueprint)
SubjectThe person or process whose knowledge is being capturedThe advisor; the successor
Operator / successorThe person who inherits the work and runs from the captureThe expert who's leaving
SourceThe narrated recording/transcript the capture is mined fromMemory, the prior doc alone
MineExtract content from the source into the template, line by line, tracedSummarize, paraphrase loosely, infer
Gap flag (FILL::)A marker for anything missing/unconfirmed — renders as highlighted "Fill this out — …"A guess; a blank
Risk flag (FLAG::)A marker for a single point of failure / undocumented method to capture — renders highlightedA normal watch-out
The gateengine/qc.py — the mechanical pass the build is gated onA checklist someone can skip
Educate & DelegateRecord the task as it naturally happens — the input-capture methodA separate, staged training exercise
KTPThe Knowledge Transfer Process — the source methodology this kit executes AI-nativelyThis kit's name in client-facing settings

Visual / Format States (in the capture .docx)

StateTreatmentMeans
Plain textBlack, AptosCaptured, sourced
Yellow highlight, "Fill this out — …"Bold, highlightedA gap the operator must complete
Yellow highlight, "RISK — …"Bold, highlightedA live risk to act on

Forbidden Terms (never in the capture document)

TermWhy
Internal AI-team names (Arden, Reid, Kit, …)To the reader it's the advisor's work — never name the back-of-house
Builder/dev jargon (deploy, wrapper, container, push, spin up)The operator is a non-technical practitioner; use the plain word
Vault-internal jargon ("kit," "golden example," "the engine")Inside-baseball; the operator sees a working document, not the machinery
A real client/person/account in a vault-visible captureAnonymization boundary — fictional names only
Coach-y filler ("lean in," "sit with," "show up")Vault voice is direct and specific