Skip to main content

Posts

Showing posts from January, 2026

How to Make Citizens Safer and Reduce Drug-War Harm Without Changing Any Laws

Trust infrastructure as public safety infrastructure Debates about drug policy usually focus on laws. Change the statutes. Elect different officials. Argue that criminalization causes harm. Sometimes this works. Often it doesn’t. Because many of the harms associated with the “war on drugs” are not primarily legal. They are structural. They arise from a simpler condition: Illegal markets lack trust infrastructure. And when trust is missing, violence substitutes. If people cannot rely on contracts, courts, or reputation, they rely on intimidation and retaliation. That substitution is mechanical, not cultural. Any market behaves this way under those constraints. If the goal is safer neighborhoods, the first problem to solve is not legislation. It is trust. Why illegal markets are disproportionately violent Legal markets use: contracts arbitration licensing credit history reputation systems Disputes get resolved economically: someone loses access, not bl...

Field Manual: Minimal Federated Trust-Bound Social Infrastructure

Minimal Federated Trust-Bound Social Infrastructure (Ur-Protocol) Complete Specification and Field Manual v0.5 Part I: Specification 0. Scope Ur-Protocol defines a portable identity + small-group coordination substrate. It is not: a platform a company service a monolithic app a global social graph It is: a protocol that allows many independent servers and many independent clients to coordinate small human groups safely and cheaply The protocol guarantees: identity continuity social proof admission/recovery group ordering/consistency server replaceability client replaceability Everything else (UX, features, aesthetics) is out of scope. 0.1 Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 0.5 Fo...

Field Manual: Epistemic Self-Defense with Large Language Models

Field Manual: Epistemic Self-Defense with Large Language Models Doctrine, Procedures, Constraints 0. Purpose This document defines the primary strategic use of locally operated large language models. Not content generation. Not companionship. Not automation of thought. Primary function: reduce the cost of verifying claims. Outcome: epistemic self-defense. 1. Core Premise Large language models are clerical cognition engines. They compress text, extract structure, reorganize information, and compare documents. They do not originate truth, exercise judgment, or determine correctness. They reduce labor. They do not replace thinking. 2. Historical Constraint Before cheap computation, reading large volumes was expensive, cross-checking sources was slow, and synthesis required staff. Institutions therefore held advantages: think tanks, policy offices, PR operations, lobbying groups, major media. Their edge was processing scale. They could read everything. Individuals could not. Trust in autho...