Protocols/Projects
27 Apr 2026 - 27 Apr 2026
- @@html: <style> .tbl-wrap { padding: 1rem 0; font-size: 13px; font-family: Optima; margin: 20pt; } .tbl-wrap table { width: 100%; border-collapse: collapse; table-layout: fixed; } .tbl-wrap th { font-weight: 600; font-size: 14px; text-align: left; padding: 6px 10px; border-bottom: 0.5px solid var(--color-border-tertiary); } .tbl-wrap td { vertical-align: top; padding: 8px 10px; border-bottom: 0.5px solid var(--color-border-tertiary); color: var(--color-text-primary); line-height: 1.4; } .tbl-wrap tr:last-child td { border-bottom: none; } .badge { display: inline-block; font-size: 13px; padding: 2px 7px; border-radius: 4px; font-weight: 500; white-space: nowrap; } .b-done { background: EAF3DE; color: 3B6D11; } .b-ready { background: E6F1FB; color: 185FA5; } .b-gap { background: F1EFE8; color: 5F5E5A; } .b-theory { background: EEEDFE; color: 3C3489; } .b-case { background: E1F5EE; color: 0F6E56; } .b-creative { background: FAEEDA; color: 854F0B; } .b-method { background: FCEBEB; color: A32D2D; } .effort-low { color: 3B6D11; font-weight: 500; } .effort-med { color: 854F0B; font-weight: 500; } .effort-hi { color: A32D2D; font-weight: 500; } col.c1 { width: 22%; } col.c2 { width: 32%; } col.c3 { width: 12%; } col.c4 { width: 13%; } col.c5 { width: 21%; } .tbl-wrap tr:hover td { background: var(--color-background-secondary); } .key { display: flex; flex-wrap: wrap; gap: 8px; margin-bottom: 12px; font-size: 11px; } .key-group { display: flex; gap: 6px; align-items: center; } .key-label { color: var(--color-text-secondary); } </style> <div class="tbl-wrap"> <h2 style="sr-only">Protocol community contribution map</h2> <div class="key"> <span class="key-label">Type:</span> <span class="badge b-theory">theoretical</span> <span class="badge b-case">case study</span> <span class="badge b-creative">creative</span> <span class="badge b-method">methodological</span> <span class="key-label">Status:</span> <span class="badge b-done">done</span> <span class="badge b-ready">framework ready</span> <span class="badge b-gap">gap identified</span> </div> <table> <colgroup><col class="c1"><col class="c2"><col class="c3"><col class="c4"><col class="c5"></colgroup> <thead> <tr> <th>contribution</th> <th>core argument / angle</th> <th>type</th> <th>effort</th> <th>status</th> </tr> </thead> <tbody> <tr> <td>Cancer as protocol disease</td> <td>Aktipis framework: cancer = systematic violation of 5 cellular cooperation protocols; biology as billion-year testbed for protocol design</td> <td><span class="badge b-creative">creative</span></td> <td class="effort-low">low</td> <td><span class="badge b-done">done</span> — <a href="https://substack.com/@mtraven23/p-188992206">HTML essays created</a></td> </tr> <tr> <td>Protocol epoch taxonomy</td> <td>"-zoic" naming system: Somatozoic → Graphozoic → Mechanozoic → Cyberozoic → Autonomozoic; geological parallel with scholarly gravitas</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-low">low</td> <td><span class="badge b-done">done</span> — taxonomy developed</td> </tr> <tr> <td>Protocol maintenance / stewardship theory</td> <td>Reader cites "muddling through" as phrase but not Lindblom's full argument; no theory of steward succession, political economy of stewardship labor, or failure modes beyond ossification. Weber routinization + Ostrom commons + Maintainers (Russell & Vinsel) synthesis</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-hi">high</td> <td><span class="badge b-ready">framework ready</span> — <a href="https://docs.google.com/document/d/1qbFiIZMD_AauNREJm2fPxEwRumE5IYhlj3EewbYUJs4/edit?tab=t.0">Brand book review in prep</a>, gaps mapped</td> </tr> <tr> <td>Protocol enforcement theory</td> <td>Reader lacks unified framework covering cost structures, ecology of cheating strategies, co-evolutionary dynamics, and trust-minimization vs. trust-building tradeoffs</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-med">medium</td> <td><span class="badge b-ready">framework ready</span> — gaps analyzed in depth</td> </tr> <tr> <td>Protocol invisibility as political achievement</td> <td>Critique of Whitehead "advance" framing: invisibility is not neutral — it obscures power relations, asymmetric knowledge, and whose labor sustains coordination infrastructure</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-med">medium</td> <td><span class="badge b-ready">framework ready</span> – Ideas incorporated into Brand book review</td> </tr> <tr> <td>Sit-in as adversarial protocol design</td> <td>Decision-tree dominance, strategic internalization as distinct enforcement mechanism, behavioral-propositional duality — protocol as argument that speech cannot make. Reader undertheorizes adversarial protocol design</td> <td><span class="badge b-case">case study</span></td> <td class="effort-low">low</td> <td><span class="badge b-ready">framework ready</span> — I'm not sure wtf claude is talking about, but see <a href="https://hyperphor.com/ammdi/Protocols%E2%88%95of-Protest">Protocols of Protest</a></td> </tr> <tr> <td>Common law / civil law as protocol epistemology</td> <td>Common law = emergent-protocol epistemology; civil law = designed-protocol epistemology. Codification often damages what it formalizes (Agile → Scrum, IETF RFCs). Reader has the examples but not the frame</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-med">medium</td> <td><span class="badge b-ready">framework ready</span></td> </tr> <tr> <td>Demandance → protocol design</td> <td>Shrager's "demandance" (stimulus-pull) maps onto protocol design: good protocols create behavioral affordances that align psychological pulls with desired coordination outcomes</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-low">low</td> <td><span class="badge b-ready">framework ready</span> — connection noted, not written</td> </tr> <tr> <td>Liquid democracy as governance protocol case study</td> <td>Delegation chain dynamics, super-delegate concentration, revocability as protocol properties. Reader covers DAO governance extensively but misses this mechanism entirely</td> <td><span class="badge b-case">case study</span></td> <td class="effort-med">medium</td> <td><span class="badge b-gap">gap identified</span></td> </tr> <tr> <td>Secret / underground protocols</td> <td>Hobo codes, spy tradecraft, resistance comms, criminal signaling — how secrecy constraints shape protocol design; evolution under surveillance pressure. Complete gap in Reader</td> <td><span class="badge b-case">case study</span></td> <td class="effort-med">medium</td> <td><span class="badge b-gap">gap identified</span></td> </tr> <tr> <td>Negarestani / Land as missing theoretical voices</td> <td>Negarestani's normative recursion (rational agency as protocol-all-the-way-down); Land's capitalist automatism as critique of human-centered coordination. Community skews hopeful-pragmatic and ignores accelerationist challenge</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-hi">high</td> <td><span class="badge b-gap">gap identified</span></td> </tr> <tr> <td>Agent-based modeling as methodological bridge</td> <td>NetLogo / SugarScape to bridge formal protocol theory (pi-calculus, automata) with intuitive simulation; could make theoretical claims testable and communicable</td> <td><span class="badge b-method">methodological</span></td> <td class="effort-hi">high</td> <td><span class="badge b-gap">gap identified</span></td> </tr> <tr> <td>Plural currency non-fungibility</td> <td>How to structurally prevent plural currencies from collapsing into fungibility through exchange/conversion — spheres of exchange framing, sacred/profane distinction as mechanism not just norm</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-med">medium</td> <td><span class="badge b-gap">gap identified</span></td> </tr> <tr> <td>Chorematics / spatial protocol primitives</td> <td>Laban's movement notation as spatial protocol grammar; what counts as a "primitive" in embodied/spatial coordination protocols</td> <td><span class="badge b-theory">theoretical</span></td> <td class="effort-hi">high</td> <td><span class="badge b-gap">gap identified</span></td> </tr> </tbody> </table> </div> @@