Knowledge Threads

The tetrahedral model works in small groups — dance floors, villages, teams. James C. Scott identifies how scaling always introduces legibility: the center simplifies the periphery to read it, and simplification destroys local knowledge. How does recognition infrastructure scale without reproducing this?

• Legibility is geometric, not moral. A center coordinating many nodes needs compression. Compression discards local detail. Local detail is where the pattern operates.
• The tetrahedron offers a different geometry. Distributed load across four vertices and six edges — no single center. Structurally different from hub-and-spoke.
• Ostrom's polycentric governance: Nested overlapping jurisdictions. Governance at the scale of knowledge.
• Succession implies staging. Scale should follow succession, not precede it.

Three scaling media analyzed as test cases: Website (practitioners, somatic activation), Repository (knowledge developers, developmental history), Skill (system designers, executable operations). Each is a complete tetrahedral system at its own scale, connected at specific edges. The principle: scale through differentiated media, not uniform replication. This is Ostrom’s polycentric governance in practice — federation through differentiated instances, no center. Local knowledge stays local; it doesn’t need compression to travel.

1. Federation vs. replication: answered. Federation through different media. Each medium is a complete tetrahedron connected at edges.
2. Inter-group edges: answered. The six edges describe inter-group dynamics at different grain. Same vocabulary, scale-appropriate application.
3. Information flow at scale: answered. Through trace, not compression. Each medium is a trace deposit at a different scale.
4. Open Village as test case: partially addressed. Three-economy model maps to three media (gift/exchange/commons).
5. Digital infrastructure: answered. Digital replication preserves structural pattern while compressing context. Resolution: maintain all three media, each at appropriate scale.

Graduated trust means you don't start with full access — you demonstrate coherent action in shared stakes over time. But every entry barrier can become exclusion. How does graduated trust entry avoid becoming the thing it was built to replace?

• Gatekeeping filters people; graduated trust filters behavior. Static screening vs. developmental calibration.
• Boundaries are information, not rejection. Entry barriers should communicate what's needed, not perform exclusion.
• Consent is ongoing negotiation between system needs and person's capacity — not pass/fail.
• Entry should match succession stage. Pioneer entry is simple; climax entry is complex.

The built entry sequence (Session 3) and the OSG V2 holding-the-commons page provide evidence. Key reframing: entry through commons, not through service. When the framework is offered (not administered), entry is self-directed (not evaluated). The four diagnostic questions are both the entry mechanism AND the ongoing practice — no separate gate. The “face cards” in the practice deck solve urgent entry: your search for the capacity IS your entry. Exit language is identified as a genuine gap.

1. Who designs entry? Power is made legible (questions visible, routing transparent) but not eliminated. Succession model suggests entry design becomes challengeable as system matures.
2. Observable by whom? Reframed: self-observation, not surveillance. Diagnostic questions are first-person. But community-level entry still involves observation by others.
3. Speed problem: resolved for individual entry. Four questions are immediate, no prerequisites. Graduated trust applies at deeper levels through engagement, not assessment.
4. Exit: genuine gap identified. The framework needs explicit exit language. If all four questions are easy, you don’t need the framework.
5. Ceremonial Gift: confirmed. The OSG V2 website IS the ceremonial gift at digital scale. The practice deck’s breath gate is the threshold ritual.

The framework's foundation is somatic — nervous systems reading each other, bodies calibrating in real time. Porges and Menakem aren't supplementary; they're foundational. How does a digital knowledge system hold somatic knowing without reducing it to description?

• The gap is structural, not cosmetic. The dance floor works because nervous systems negotiate below language. Digital systems operate above language.
• Description is not transmission. Reading about co-regulation does not produce co-regulation.
• The repository has somatic markers, not somatic content. Drift detection, failure mode signatures, and succession correlates are pointers for people who already have somatic capacity.
• Menakem's insight: Bodies carry structural knowledge the cognitive mind can't articulate. Some patterns cannot be written down.

1. Is "pointing at" sufficient, or does the codex require body-based practice alongside?
2. Could video/audio transmit more of the embodied pattern than text alone?
3. Can ceremonial protocols create somatic conditions for reading the content?
4. The AI paradox: if somatic knowing is foundational but AI has no body, what does generative AI-human exchange say about the somatic requirement?
5. Could an embodied practice catalog connect codex concepts to specific physical activities?

The Architecture test: "what works without you?" But this entire body of work is deeply marked by one person's lived experience. The framework's power comes from its particularity — it wasn't theorized from distance. How does deeply particular knowledge become transferable without becoming generic?

• Generic frameworks fail. They travel well but land poorly. This model's strength is specific convergence, not abstraction.
• Differentiation addresses this directly. Transfer means the receiver integrates through their own experience, not wholesale adoption.
• Lineage tracking preserves particularity by naming the specific source. Concepts carry their history.
• The codex compresses, not translates. Compression preserves (you can decompress); translation replaces.

1. Does the framework need practitioner guides for different contexts (education, healthcare, tech)?
2. The teaching problem: the framework transfers without the maker, but does the practice require a living teacher?
3. Successive particularization: does the repository become richer (more particular) as more people engage, rather than more generic?
4. The gift economy answer: you don't make it transferable — the receiver does the work of making it theirs.
5. This repository as test case: will future sessions compound knowledge from experience they didn't have?