KD-039 · Workflow
Experience Compiler Lifecycle
Show how operating experience becomes a reviewable authority asset without broadening its claim boundary.
- Evidence level
- Verified
- Executive audience
- Founder, editor, TIF operator
- Publication status
- Published after human review
Inspect the operating model
Rendering diagram…
Text alternative and Mermaid source
Experience Compiler Lifecycle. Show how operating experience becomes a reviewable authority asset without broadening its claim boundary. Business problem: Real work is often trapped in notes, discussions, and delivery artifacts rather than converted into reusable, evidence-bound intellectual property. Claim boundary: Internal TIF operating model. It describes the implemented review and traceability design, not autonomous publication, a knowledge graph, or a claim about external outcomes.
flowchart LR
X[Operating experience] --> C[Capture]
C --> E[Evidence]
E --> P[Problem and pattern]
P --> F[Framework and diagram]
F --> A[Authority package]
A --> R[Human review]
R --> U[Publication and learning]Why this matters
Real work is often trapped in notes, discussions, and delivery artifacts rather than converted into reusable, evidence-bound intellectual property.
Executive decision
- Capture source context, admit evidence, identify the operating problem and pattern, assemble a framework and diagram, then submit an asset for human review.
Claim boundary
Internal TIF operating model. It describes the implemented review and traceability design, not autonomous publication, a knowledge graph, or a claim about external outcomes.
Evidence summary
tko:ev-operational-intelligence-vs-reporting
Across healthcare, RachelOS, and CRE engagements, dashboards and reports describe what happened, but the decision about what to do next still depends on a person — reporting is not the same capability as operational intelligence.
Boundary: Generalized finding from cited code- and pattern-backed records. No metric.