Born as a brand phrase
It starts as positioning language in client work: a learning platform that "transforms expertise into living knowledge." A tagline, not yet a system. Where knowledge comes alive.
a living document · it updates as the idea earns receipts
Living knowledge
This is a thread I'm currently pulling, and the narrative adapts as it moves. Companies run on documents that claim to describe the present; this page is about the system that keeps them honest, and it practices what it describes: dated, confidence-marked, and still changing.
status in live test
confidence medium
last updated jun 11 2026
next review when the test reports
the idea, briefly
The problem isn't that companies don't document. They document constantly. The problem is that documents are snapshots, and companies are moving pictures. Every day a document sits still, the gap between what's written and what's true gets wider, and people keep deciding against the written version.
Living knowledge is the system that keeps a company's knowledge moving at the speed of the company: living documents kept separate from the daily flood of inputs, a router instead of a warehouse, decisions that keep their criteria, and a system that proposes while people decide.
And underneath it, the frame that keeps sharpening: hierarchies don't just slow context down, they gate it. The substrate a company actually runs on is the combination of everyone's texture graphs, permissioned together, set against where the company and each person are trying to go. Work is navigating that shared terrain. The system's job is making the navigation honest: showing where paths converge, where they diverge, and the difference between losing alignment and losing confidence.
the record · watch the idea grow
jan 2025
apr 2025
The conversation where it became architecture
A working session about company knowledge turns the phrase into a blueprint: evergreen living documents versus temporal inputs, and a system that notices what the org is asking.
"I would love to, as a manager, say: some people from your team are asking this similar question. I've made these suggestions to the curriculum. Do you approve?"
2025
The 2x2
One drawing keeps coming back: personal context and goals against company context and goals. Nearly every misalignment lives in the gap between the quadrants. Routing context across that gap becomes the point of the whole system.
early 2026
The idea turns inward
The same architecture, applied to one person instead of a company, becomes this site. Maintained by the system it describes. Texture is the protocol; living knowledge is the infrastructure.
jun 2026
The permissioning problem
A sharper frame arrives mid-conversation: hierarchies don't just slow context down, they gate it. A conversation on the growth side could be directly helped by one happening on the product team, and both sit in isolated echo chambers. What knowledge organizations may actually need is to look more like decentralized networks running on a shared layer of understanding underneath. People make partial decisions because their picture of the context or the goals has gaps. Orientation matters; shared understanding matters more.
jun 2026
The overlay
Mid-audit, the 2x2 gives up its full meaning, fourteen months after the first drawing. The context halves are texture graphs: a person's on one side, and on the other the company's permissioned combination of everyone's graphs plus its decisions. The goals halves are where each party is trying to go. Employment, seen this way, is two parties navigating shared terrain toward converging goals, and the moment the paths genuinely diverge, the arrangement stops making sense. The infrastructure ambition follows: overlaid texture graphs, co-thinking across boundaries, membranes sharing the shape of thinking without exposing the private record.
now
The live test
The company-scale version is running inside a working growth org: living documents, decision logs, an approval gate. This entry updates when the receipts land. That's the format keeping itself honest.
current state · what I believe as of today
Stale documents are a decision-quality problem, not a documentation problem.high · jun 2026
The value is the router, not the warehouse: relevance beats storage and beats execution.high · jun 2026
Decisions should keep their criteria, date, and confidence, at company scale.medium · in test
The system proposes, humans decide: the approval gate is what makes adoption survivable.medium · in test
Goal divergence and confidence collapse are different endings, and they need different responses.medium · jun 2026
Co-thinking across texture graphs, with progressive disclosure doing the boundary work, is where this is headed.early · jun 2026
open questions · what the test must answer
- Does a working team actually consult the living documents at the moment of decision, or only in onboarding?
- What does the approval gate cost in speed, and who pays it?
- Where does the router get its sense of relevance wrong, and how is that corrected?
- Who holds the permissioning authority in a shared brain, and what does that power do to the network it serves?
maintained by the system it describes this document will change · that's the point
maintained by the system it describes email · victoria, bc