01 — CONTEXT: Knowledge Transfer
Input definitions, validation rules, and what each mode requires.
Create — Inputs
| Input | Required | Example | Used For |
|---|---|---|---|
| Source recording/transcript | Yes | A screen-share of the expert running the monthly close, transcribed (Otter/Zoom) | The spine — every captured line traces here |
| Subject + header facts | Yes | "Northwind Trading Co." · operator · QBO/Bill.com/Gusto · monthly · owner | Title + header line |
| Prior doc | No | An old SOP, a partial blueprint, account list | Supplementary detail; loses to the recording on conflict |
| Template | Yes | engine/template.json (general, or domain-adapted) | The structure the engine fills |
Validation Rules — Create
- No source, no capture. A recording or transcript of the actual work is required. Don't build from memory or from the prior doc alone.
- One subject per capture. Multiple people/processes → multiple runs.
- The prior doc is supplementary. Where it conflicts with the recording, the recording wins (it's what the expert actually does).
- Confirm subject + source + template with the advisor before running.
Update — Inputs
| Input | Required | Source | Used For |
|---|---|---|---|
| Existing content file | Yes | engine/ | The doc being updated |
| The change | Yes | A filled gap, a new rule, a changed watch-out | What to edit |
Validation Rules — Update
- Edit the content file, then regenerate — never hand-edit the
.docxas the source of truth (the engine would overwrite it). - Re-run Gate 1 after every update.
Gap Protocol
Missing inputs don't block the build — they get flagged, by design. But two things do block:
- No source recording at all → blocked. This kit captures what an expert does; with nothing to mine, there's nothing to capture. (Resolve: get the recording —
06.) - A flagged risk left unaddressed at ship (
FLAG:: RISK —that names a hard deadline, e.g., "capture before the person leaves") → surface it to the advisor; don't let it ship silently.
Everything else missing → a FILL:: flag. A capture with flagged gaps is valid, correct output — the flags ARE the deliverable's honesty.
Input Priority Hierarchy
When inputs conflict:
- The source recording — what the expert actually does, in their own narration.
- The advisor's confirmation — corrections stated in the run.
- The prior doc — only where the recording is silent.
- Never: assumption, plausibility, or "how it's usually done." That's a
FILL::, not a fact.