amicusContra — The Outward Function

2026-09-27T00:00:00+00:00

The Name</h2>
amicusContra</strong> — friend of the court, against unaccountable power.</em></p>
The traditional amicus curiae (“friend of the court”) provides perspective. amicusContra goes further — it is the outward projection function of guerillaGorilla, extending accountability infrastructure toward cases the operator is not personally party to.</p>

Three Directions</h2>
Direction</th> Target</th> Action</th> Metaphor</th></tr></thead>

Downward</strong></td> Those beneath</td> Stabilize — prepare rooms, infrastructure as service</td> The gorilla lifts</td></tr>
Lateral</strong></td> Those who are like</td> Cross-protect — mutual defense, shared intelligence</td> The gorilla stands beside</td></tr>
Upward</strong></td> Those above</td> Hold to account — force reproducibility, same standard as science</td> The gorilla challenges</td></tr> </tbody></table>
Downward: Prepare Rooms</h2>
Provide infrastructure to those who need it but cannot build it themselves:</p>

Templates for pro se filings</li>
FOIA request frameworks</li>
Evidence organization patterns</li>
The dispersal pattern itself — anyone can produce a .primals.eco site</em></li> </ul>
The rooms are prepared before anyone asks for them. When they arrive, the infrastructure is already there.</p>
Lateral: Cross-Protection</h2>
Work with those fighting similar battles:</p>

Shared OSINT databases</li>
Cross-referenced entity networks</li>
Mutual citation and evidence corroboration</li>
Three-surface evidence replication across independent operators</li> </ul>
Lateral projection creates resilience through redundancy</strong>. No single operator’s work depends on any other’s infrastructure, but all benefit from the shared graph.</p>
Upward: Hold to Account</h2>
Apply the same standard to institutions that institutions claim to apply to individuals:</p>

Reproducibility</strong>: if a court claims a process was followed, reproduce it</li>
Documentation</strong>: if an agency claims compliance, request the records</li>
Verification</strong>: if an institution claims oversight, verify the oversight</li>
Publication</strong>: if the record contradicts the claim, publish the record</li> </ul>
The standard is not adversarial. It is scientific</strong> — the same reproducibility standard that validates a physics experiment validates a judicial process. If the result cannot be reproduced from the stated method, the method is suspect.</p>
Tagline</h2>

“Beside the small. Against unaccountable power. For the record.”</em></p> </blockquote>

fEAR — flow Evolution to Adversarial Response

2026-09-27T00:00:00+00:00

The Name</h2>
The name operates on three layers simultaneously:</p>
fEAR</strong> (outward) — The emotional response the system produces in the adversary. The system converts the adversary’s own actions into prosecution fuel. Every move they make strengthens the case against them.</p>
f(EAR)</strong> (inward) — The function of the ear. A sensory organ. The system listens. It does not argue. It does not threaten. It does not negotiate. It hears what the adversary says, files, submits, and does — and processes the signal. f(EAR)</code> is a function that takes what the ear collects and returns evolved case state.</p>
fEAR</strong> (recursive) — The system is fearsome because</em> it listens. Silence is more threatening than argument because silence means processing. Every adversary action creates signal. Every signal evolves the case.</p>
Biological Basis</h2> Hearing is:</p> Event-driven</strong>: sound arrives in discrete packets (filings, actions, statements)</li> Receive-only</strong>: the ear does not broadcast — it collects</li> Long range</strong>: sound travels further than smell or sight</li> Omnidirectional</strong>: the ear catches signals from any direction</li> Always on</strong>: you cannot close your ears the way you close your eyes</li> </ul> Legal Instantiation</h2> Input</th> Source</th> Processing</th></tr></thead> Court filings</td> PACER, county clerk portals</td> Docketed, timestamped, cross-referenced</td></tr> OSINT signals</td> Public records, social media, corporate filings</td> Pattern-matched against known entities</td></tr> Adversary actions</td> Motions, responses, communications</td> Converted to evidence — every response is signal</td></tr> Institutional records</td> FOIA, state databases</td> Archived, BLAKE3 hashed, CAS anchored</td></tr> </tbody></table> The Conversion</h2> The critical insight: adversary actions are fuel, not friction</strong>.</p> When the adversary files a motion to dismiss, fEAR hears it as a signal revealing their legal strategy. When they deny a FOIA request, fEAR hears it as evidence of institutional resistance. When they hire an attorney, fEAR hears it as confirmation that the system has produced the emotional response its name describes.</p> The adversary cannot win by acting, and cannot win by not acting. Action creates signal. Inaction creates timeline. Both evolve the case.</p> preSCENT — Pattern Recognition and Ambient Presence 2026-09-27T00:00:00+00:00 The Name</h2> preSCENT</strong> operates on two layers:</p> Olfaction</strong> — Smell is the oldest sense. It detects gradients — not discrete events (that’s hearing), but ambient state. Something is off</em>. The air has changed. An institution’s behavior shifted before any filing appeared.</p> pre-SCENT</strong> — The scent comes before</em>. preSCENT is the detection of change that precedes visible action. Board meeting agendas that shift focus. Staffing changes at regulatory agencies. Campaign contribution patterns that predict judicial behavior.</p> Biological Basis</h2> Olfaction is:</p> State-driven</strong>: smell measures ambient concentration, not discrete packets</li> Gradient-based</strong>: the nose detects changes</em> in state, not absolute values</li> Bidirectional</strong>: you both detect and emit scent — your presence is broadcast</li> Close range</strong>: smell attenuates with distance — it requires proximity or wind</li> Persistent</strong>: scent lingers after the source departs</li> </ul> The Bidirectional Property</h2> This is the critical difference from fEAR. The ear only receives. The nose also emits</em>.</p> detroit.primals.eco is preSCENT</strong> — it is ambient presence broadcast. The site exists. The evidence is public. The record accumulates. Everyone in the network can smell</em> it — they know it’s there, and they know it grows.</p> The site doesn’t need to be actively promoted. Its existence changes institutional behavior. Board members who know their connections are documented behave differently than those who believe they’re invisible.</p> Legal Instantiation</h2> Detection</th> Broadcast</th></tr></thead> Behavioral shifts in institutional actors</td> Public evidence library (detroit.primals.eco)</td></tr> Campaign finance pattern changes</td> Git repository anyone can clone</td></tr> Board composition mutations</td> Three-surface evidence (live site + sovereign repo + GitHub mirror)</td></tr> Staffing changes at oversight agencies</td> BLAKE3 content manifest — the record is provably unaltered</td></tr> </tbody></table> Network Mapping</h2> preSCENT’s graph analysis capability maps the entity network — not just who is connected, but how connections change over time</em>. The typed edges in data/edges.toml</code> with epistemic grammar create a relational map where every connection has a confidence level and a source document.</p> The network map is not static intelligence. It is a living gradient</strong> — new connections appear, old ones shift, and the topology reveals structure that no single document contains.</p> STRIDe — Strategy, Tactics, Reconnaissance, Intelligence, Deployment, execution 2026-09-27T00:00:00+00:00 The Name</h2> STRIDe</strong> — Strategy, Tactics, Reconnaissance, Intelligence, Deployment, execution.</p> The lowercase ‘e’ is deliberate. Execution is functionally the least important component. It is directionality — the foot hitting the ground. Everything before it is the real work.</p> Concept</h2> fEAR senses and builds. STRIDe moves.</p> Sensing without motion is surveillance. Building without purpose is accumulation. The system needs a gait</strong> — a continuous, adaptive, self-correcting process that translates intelligence into action.</p> A stride is not a step. A step is discrete — it starts, it ends, it succeeds or fails. A stride is continuous. It adapts to the sidewalk. It doesn’t falter at every crack. You catch yourself in stride when you stumble. The ground changes under you and your body adjusts before your conscious mind registers the change.</p> The R⇄I Loop</h2> The core of STRIDe is the Reconnaissance ⇄ Intelligence</strong> feedback loop. Reconnaissance collects raw signal. Intelligence processes it into actionable understanding. The loop runs continuously — not in phases, not in sprints, but as a sustained metabolic process.</p> Component</th> Role</th> Cadence</th></tr></thead> S</strong>trategy</td> Long-term objective</td> Monthly revision</td></tr> T</strong>actics</td> Specific maneuvers</td> Weekly adjustment</td></tr> R</strong>econnaissance</td> Raw signal collection</td> Continuous</td></tr> I</strong>ntelligence</td> Signal → understanding</td> Continuous</td></tr> D</strong>eployment</td> Staging and preparation</td> As needed</td></tr> e</strong>xecution</td> Action</td> When ready</td></tr> </tbody></table> Filing Cadence</h2> In legal application, STRIDe produces a filing cadence that is metabolically efficient:</p> One filing per week</strong> maintains constant pressure at minimal operator cost</li> Each filing builds on the last</strong> — the adversary must respond to an evolving narrative</li> No filing is wasted</strong> — every submission advances the R⇄I loop regardless of outcome</li> Denial is information</strong> — a rejected motion reveals the court’s reasoning</li> </ul> The adversary must respond to each filing individually. Their cost per response exceeds the operator’s cost per filing. Over weeks, this creates the metabolic asymmetry that pursuit predation requires.</p> Case Study #1: Detroit Charter Schools 2026-09-27T00:00:00+00:00 Overview</h2> detroit.primals.eco</a> is Case Study #1</strong> — the first non-sporePrint site in the ecoPrimals ecosystem. It documents a Detroit charter school network where a man with 9 criminal convictions runs two schools receiving $4.9M/yr in public education funding.</p> The Site as preSCENT</h2> detroit.primals.eco is the digital instantiation of preSCENT</strong> — ambient presence broadcast through a public evidence library. The site exists. The evidence is public. The record accumulates. Everyone in the network can see it.</p> By the Numbers</h2> Metric</th> Value</th></tr></thead> Criminal convictions</td> 9 (6 felony, 3 misdemeanor)</td></tr> Annual public funding</td> $4.9M</td></tr> Revenue to management LLC</td> 72.67%</td></tr> Math proficiency</td> 3%</td></tr> Judges with documented connections</td> 9 across 4 courts</td></tr> Site pages</td> 128+</td></tr> Entity nodes</td> 43</td></tr> Typed edges</td> 57</td></tr> Epistemic levels</td> 7</td></tr> Evidence surfaces</td> 3 (live site + sovereign repo + GitHub mirror)</td></tr> </tbody></table> Infrastructure</h2> Component</th> Implementation</th></tr></thead> Static site</td> Zola + Catppuccin theme + elasticlunr search</td></tr> Entity registries</td> config.toml [extra.actors/entities/sources]</code></td></tr> Typed edges</td> data/edges.toml</code> with epistemic grammar</td></tr> Content addressing</td> BLAKE3 content-manifest.toml</code> with root hash</td></tr> Sovereign repo</td> git.primals.eco/publicRecord/detroit</a></td></tr> Public mirror</td> github.com/defendDetroit/publicRecord</a></td></tr> Build crate</td> crates/detroit-build/</code> (9 modules, 7 build steps)</td></tr> Shared substrate</td> crates/litho-core/</code> (6 modules)</td></tr> </tbody></table> Provenance Trio Instantiation</h2> Layer</th> Science (original)</th> Legal (detroit)</th></tr></thead> Ephemeral</td> rhizoCrypt session DAG</td> fossilRecord epoch archives</td></tr> Certificate</td> loamSpine RFC 3161</td> CASE_REGISTRY typed roles</td></tr> Attribution</td> sweetGrass PROV-O braids</td> GRAPH_DATA entity intelligence</td></tr> </tbody></table> Verify</h2> Live site</strong>: detroit.primals.eco</a></li> Source</strong>: git.primals.eco/publicRecord/detroit</a></li> GitHub</strong>: github.com/defendDetroit/publicRecord</a> — public home</li> Sitemap</strong>: detroit.primals.eco/sitemap.xml</a> — 127 URLs</li> Validation</strong>: detroit.primals.eco/validate/</a></li> </ul> Cross-Protection — Three-Surface Evidence 2026-09-27T00:00:00+00:00 The Pattern</h2> Every evidence claim in the guerillaGorilla framework exists on at least three independent surfaces:</p> Surface</th> Purpose</th> Example</th></tr></thead> Live site</strong></td> Public access, SEO, human readers</td> detroit.primals.eco</td></tr> Sovereign repo</strong></td> Git-signed, timestamped, self-hosted</td> git.primals.eco/publicRecord/detroit</td></tr> Public mirror</strong></td> Independent copy, community access</td> github.com/defendDetroit/publicRecord</td></tr> </tbody></table> Suppressing one surface does not affect the others. Taking down the live site leaves the repos. Taking down GitHub leaves the sovereign infrastructure. Seizing the VPS leaves the local gates with full copies.</p> BLAKE3 Content Addressing</h2> Every page is BLAKE3 hashed and recorded in content-manifest.toml</code>. A single root_hash</code> covers the entire content tree. Any modification to any page changes the root hash, making tampering detectable.</p> The hashes travel with the content. Clone the repo, run b3sum</code>, and verify independently. No trust required in any single surface.</p> Why Three, Not Two</h2> Two surfaces create a “he said / she said” dispute. Three create consensus</strong> — if two of three agree, the third is the anomaly. This is the same principle behind Byzantine fault tolerance in distributed systems.</p> The evidence doesn’t need to be trusted. It needs to be verifiable across independent surfaces</strong>.</p> The Dispersal Pattern — Primal-as-Site 2026-09-27T00:00:00+00:00 The Pattern</h2> detroit.primals.eco proved that the ecoPrimals infrastructure substrate generalizes beyond science. Any domain that produces typed, citable claims with verifiable sources</strong> can produce a .primals.eco</code> static site using the shared litho-core substrate.</p> Architecture</h2> sporePrint Catalogue (config.toml entity_registry, sources.toml) │ ▼ site.primals.eco (Zola static site) ├── config.toml (typed registries — actors, entities, sources) ├── content/*.md (pages with TOML front matter) ├── data/edges.toml (typed edges with epistemic grammar) └── crates/site-build/ (uses litho-core) │ ▼ content-manifest.toml graph.json braids.json (BLAKE3 hashes) (typed edges) (PROV-O attribution) │ │ │ ▼ ▼ ▼ nestGate CAS sweetGrass braids loamSpine spine </code></pre> Pattern Components</h2> Zola Site with Entity Registries</strong> — typed registries in config.toml [extra.*]</code></li> Typed Edges with Epistemic Grammar</strong> — 7 levels from record</code> to adjudicated</code></li> Build Crate using litho-core</strong> — 6 shared modules (frontmatter, manifest, graph, report, registry, provenance)</li> Provenance Trio Wiring</strong> — build output feeds nestGate + sweetGrass + loamSpine</li> Convergence Depth Meter</strong> — 5 levels: CAS → DAG → Spine → Braid → Signed witness</li> </ol> Hierarchy</h2> gorilla.primals.eco (methodology — you are here) └── detroit.primals.eco (Case Study #1 — Banks enterprise) └── [future].primals.eco (Case Study #N) sporeprint.primals.eco (ecosystem catalogue — parent) └── gorilla.primals.eco (registered methodology) └── detroit.primals.eco (registered case study) </code></pre> Who Can Adopt This</h2> Domain</th> Registry types</th> Edge grammar</th></tr></thead> Legal (active)</strong></td> actors, entities, sources</td> 7 epistemic levels</td></tr> Methodology (active)</strong></td> capabilities, cases, tools</td> operational levels</td></tr> Science (future)</strong></td> researchers, papers, datasets</td> validation levels</td></tr> Medical (future)</strong></td> protocols, trials, outcomes</td> evidence grades</td></tr> </tbody></table> The substrate is domain-agnostic. Each site owns its registries and edge grammar; litho-core provides the common plumbing.</p> Pursuit Predation — The Evolutionary Anchor 2026-09-27T00:00:00+00:00 Two million years ago, a primate on the African savanna developed an unusual hunting strategy. It could not outrun its prey. It could not outfight its prey. It could not ambush — the savanna offered no cover. Instead, it walked.</p> The prey sprinted. The primate walked. The prey sprinted again. The primate walked. The prey overheated — quadrupedal locomotion at sprint speed generates heat faster than four-legged respiratory systems can dissipate it. The primate, bipedal, upright, sweating through exposed skin, thermoregulating while moving, maintained pace. The hunt ended not with a kill shot but with metabolic collapse. The prey fell over. The primate was still walking.</p> This is pursuit predation</strong>. It made Homo sapiens</em> the apex predator on a planet full of things faster, stronger, and more dangerous.</p> The Mapping</h2> The same optimization structure independently emerged in:</p> Pro se legal strategy</li> OSINT analysis</li> Regulatory complaint campaigns</li> Institutional accountability work</li> </ul> The mapping is not metaphorical. It is structural:</p> Biology</th> Accountability</th></tr></thead> Bipedal thermoregulation</td> Low operational cost (pro se, FOIA, public records)</td></tr> Quadrupedal sprint heat</td> High adversary response cost (attorneys, PR, motions)</td></tr> Endurance tracking</td> Persistent documentation over months/years</td></tr> Metabolic collapse</td> Adversary resource exhaustion or exposure</td></tr> Savanna (no cover)</td> Public record (nowhere to hide)</td></tr> </tbody></table> The Terminal Posture</h2> The end state is not a confrontation. It is Positional Patience</strong> — landscape saturation does the work. The operator maintains constant metabolic cost while every adversary response increases theirs.</p> Every filing they answer costs money. Every FOIA they fight generates records. Every motion they file becomes documentation. Every denial becomes evidence. The landscape fills with their own responses until the record speaks for itself.</p> Why This Is Infrastructure</h2> Pursuit predation is not a tactic. It is the biomechanical substrate</strong> that makes the sensory triad (fEAR · preSCENT · STRIDe) energetically viable. Without metabolic asymmetry, accountability work is a sprint — and sprinters lose to institutions.</p> With it, the system is self-sustaining: adversary actions are fuel, not friction.</p>

guerillaGorilla — Accountability Infrastructure

amicusContra — The Outward Function

fEAR — flow Evolution to Adversarial Response

preSCENT — Pattern Recognition and Ambient Presence

STRIDe — Strategy, Tactics, Reconnaissance, Intelligence, Deployment, execution

The Name</h2>
STRIDe</strong> — Strategy, Tactics, Reconnaissance, Intelligence, Deployment, execution.</p>
The lowercase ‘e’ is deliberate. Execution is functionally the least important component. It is directionality — the foot hitting the ground. Everything before it is the real work.</p>

Case Study #1: Detroit Charter Schools

Overview</h2>
detroit.primals.eco</a> is Case Study #1</strong> — the first non-sporePrint site in the ecoPrimals ecosystem. It documents a Detroit charter school network where a man with 9 criminal convictions runs two schools receiving $4.9M/yr in public education funding.</p>

Cross-Protection — Three-Surface Evidence

The Dispersal Pattern — Primal-as-Site

The Pattern</h2>
detroit.primals.eco proved that the ecoPrimals infrastructure substrate generalizes beyond science. Any domain that produces typed, citable claims with verifiable sources</strong> can produce a `.primals.eco</code> static site using the shared litho-core substrate.</p>`

Pursuit Predation — The Evolutionary Anchor