Human context
Memory, private notes, conversations, judgment, and authority.
THE CONCEPT BEHIND THE NAME
A shared reference that survives the handoff.
In the locating-plate joint shown here, a dowel passes through aligned bores in two parallel mating parts, normal to their shared plane. A knowledge dowel applies that shared-axis idea to the record behind physical work.
The planes remain parallel. Their bores register to one axis. The dowel travels normal to both—not sideways between two edges.
PHYSICAL JOB / LOWER PLANE
EVIDENCE FIELD / UPPER PLANE
PLANE NORMAL / DOWEL AXIS
RESOLVED GLYPH
A knowledge dowel is an independently persisted, provenance-bearing reference artifact that keeps authorized people and computational systems registered to the same physical Job across changes in person, session, model, tool, and time—without transferring authority between them.
Candidate architectural pattern · not a claim that a public interoperability standard exists today
WHY A THIRD PIECE MATTERS
The record belongs to the Job, not to a passing context.
People leave. Sessions close. Context windows disappear. Tools change. The durable record remains available to the people and systems authorized to continue the work.
JOBINDEPENDENTLY PERSISTED
Computational context
Models, sessions, tools, summaries, proposals, and inferences.
THE CAUSAL LADDER
From continuity problem to possible primitive.
The deeper metaphor is useful only when each idea is tied to a product relationship and an honest maturity level.
01CURRENT + COMMITMENT
Third-piece independence
The record persists outside any one person’s memory, session, model, or tool. Independent does not mean ownerless: custody, authorization, and accountability remain explicit.
02PRODUCT COMMITMENT
Fit and tolerance
People and systems connect through stable identity, typed records, source provenance, units, time, and honest uncertainty—not a pile of context forced into a prompt.
03CURRENT + EXTENSION
Visible drift
The physical situation keeps changing. Time anchors, corrections, measurements, and follow-up help expose where its computational representation has moved out of registration.
04CURRENT + COMMITMENT
Re-registration
When a person, session, or model changes, the next authorized participant can return to the same scoped evidence and authority boundaries without starting again.
05CONCEPTUAL EXTENSION
Interchangeable access
A stable, versioned record envelope could make tools and models more substitutable around the Job. That requires contracts, authorization, conformance tests, and migration policy that do not yet exist publicly.
06STRATEGIC POSSIBILITY
Category primitive
Knowledge dowel may become a portable term for the pattern, with Dowelify as an early implementation. It becomes a category only through a stable definition, independent usefulness, and external adoption.
CANDIDATE INVARIANTS
A pattern should eventually be testable.
These are design targets for a formal knowledge-dowel pattern. They are not a declaration that every surface already satisfies a public specification.
- 01
Stable identity and explicit physical-Job scope
- 02
Durable persistence outside participant memory or model context
- 03
Source-level provenance
- 04
Typed roles for observations, claims, proposals, decisions, actions, and outcomes
- 05
Time, validity, units, and uncertainty where applicable
- 06
Explicit authority and authorization boundaries
- 07
Visible revision, correction, and supersession
- 08
Machine-readable retrieval through a stable envelope
- 09
Re-registration to the same record version and boundaries
- 10
A stable core that can carry trade-specific payloads without flattening physical work
BOUNDARIES THAT STRENGTHEN THE IDEA
Registration preserves distinctions. It does not erase them.
01Independent does not mean ownerless.
02Fit does not guarantee truth.
03Alignment does not mean consensus.
04The same reference does not require the same conclusion.
05A durable assertion is not automatically a true assertion.
06Sharing an interface does not make people and AI symmetrical in authority.
DOWELIFY BY REACHABILITY LABS
Build from the same reference. Keep the basis visible.
Dowelify is the product. Job remains the ordinary user-facing object. Knowledge dowel names the continuity pattern the system is working to make real.