Wisdom Transfer Standard
When has written knowledge become reusable wisdom?
Wisdom Transfer is complete when an unfamiliar recipient can decode the artifact, see its system, find its authority, meet its quality bar, apply it in context, and return learning that improves the next baseline.
Five Gates
Every significant Playbook artifact must pass all five gates:
- Language — canonical meaning, domain qualification, and uncertainty are decodable.
- System — boundary, relationships, inputs, outputs, consequences, and feedback are visible.
- Wiki — owner, route, page job, lifecycle, and typed contextual links are unambiguous.
- Standard — reader setpoint, evidence state, checks, failure modes, and falsifier are declared.
- Transfer — an unfamiliar recipient can understand, apply, adapt, prove, and return learning.
Failure of one required gate means transfer is incomplete. Do not average the gates.
Commissioning
- L0 — absent: no artifact exists.
- L1 — drafted: the five gates are addressed in intent.
- L2 — built: the artifact passes structural and generated checks.
- L3 — used: a real case produces feedback and a dated receipt.
- L4 — transferred: all gates pass and an independent person in the served role validates transfer.
Structural checks can prove L2. Authors cannot self-declare L4.
Apply by Page Job
Do not impose five ritual headings. Apply the gates through the page's job:
| Page job | Transfer proof |
|---|---|
| Hub | A reader finds and chooses the rightful route. |
| Concept | A reader explains the model and transfers it to another context. |
| Playbook | A reader repeats the action and produces the declared output. |
| Evidence | A reader traces provenance, confidence, limits, and review state. |
| Glossary | Different readers decode and use the same meaning. |
| Decision record | A later reader reconstructs the reasoning and review conditions. |
| Domain map | A reader sees the boundary and uses the choice logic. |
Failure Modes
- Decoded but ownerless — the meaning is clear but no route or lifecycle authority exists.
- Routed but unproved — the page is findable but hides evidence state or failure conditions.
- Executable but unsafe — the method omits authority, consequence, or refusal boundaries.
- Readable but inert — the recipient can repeat the words but cannot apply or adapt them.
- One-way learning — use produces feedback that never updates the source or next question.
Changes my mind: independent use shows that one gate is redundant, or a missing interface predicts transfer failure better than the five-gate contract.
Context
- depends-on DDL Nomenclature — supplies canonical meaning.
- depends-on Systems — makes relationships and feedback visible.
- depends-on Wiki Schema — assigns route, job, lifecycle, and authority.
- pairs-with Documentation Writing Standard — implements transfer for pages.
- instance-of Compounding Standards — commissions one cross-interface standard.
Questions
Next question: which gate would an unfamiliar recipient fail first?