Amendment 006 — The Cochran Block, LLC
Description: Amendment No. 006 to the Operating Agreement of The Cochran Block, LLC. The Pointer Discipline Amendment — Protocol P34. We aren't savages, we have pointers.

Amendment 006 · Filed 2026-04-16
Amendment No. 006 to the Operating Agreement of The Cochran Block, LLC
The Pointer Discipline Amendment
Protocol P34 · "We aren't savages. We have pointers."
Effective Date: April 16, 2026 · Original Agreement Effective: April 14, 2026

## Section I · Recitals

WHEREAS the Operating Agreement of The Cochran Block, LLC was duly executed by the Member on April 14, 2026 (the "Original Agreement");

WHEREAS the Company now maintains a multi-document governance stack — the Original Agreement, Amendments 001 through 005, the Manifesto, the operational doctrine at `/no-quarter`, the operator handbook at `/onboarding`, and the constitutional index at `/constitution`;

WHEREAS the Member has observed that Company surfaces summarizing other Company surfaces drift out of sync over time, producing Company-authored Ironies actionable under Protocol P33 (Amendment 005) and degrading the reliability of the public governance record;

WHEREAS the Member holds that a link is a sovereign reference to a canonical source, whereas a duplicated summary is a snapshot that will decay, and that the correct architecture for a multi-document corpus is one canonical source per fact with every other reference resolved by pointer;

WHEREAS the Member has articulated the governing principle in six words:

"We aren't savages. We have pointers."

WHEREAS this principle is already embedded in the Company's software practice — the Rust binary deduplicates configuration, constants, and routing logic; the crate graph forbids circular dependencies (Protocol P15); and compressed identifiers (Protocol P13) exist precisely so that one name points to one referent — and the Member desires to extend the same discipline from code to governance text;

WHEREAS the Member further wishes to add a new Protocol P34 (Pointer Discipline) to Article XVIII of the Original Agreement, to codify the principle as a Company-binding commitment rather than an aesthetic preference; and

WHEREAS this Amendment is executed pursuant to the authority granted in Article XV of the Original Agreement.

NOW THEREFORE, the Original Agreement is hereby amended as follows:

## Section II · Amendment to Article XVIII — Addition of Protocol P34

Article XVIII of the Original Agreement is amended to include the following new Protocol, inserted after Protocol P33:

### P34 — Pointer Discipline ("The No-Savages Protocol")

### (a) Definition

"Pointer Discipline" means the practice of referencing canonical sources via hyperlinks, file paths, git hashes, route paths, crate-qualified symbol names, or other durable pointer identifiers — rather than duplicating the content of those sources into secondary documents, pages, comments, or messages.

### (b) Core Principle

We aren't savages. We have pointers.

A duplicated summary is a snapshot that decays. A pointer is a sovereign reference to a live canonical source. The Company prefers the pointer in all contexts where a pointer is operationally sufficient.

### (c) Application Across Company Surfaces

(i)Governance Documents. Governance pages that reference peer governance pages shall link rather than summarize. The `/constitution` page shall index the stack; it shall not duplicate the content of any indexed document.
(ii)Amendments. When an amendment modifies, supersedes, or operates alongside a prior amendment, it shall reference that prior amendment by number, section, and URL, and shall not reproduce the prior amendment's operative text except where legally necessary (see Section II(d) exceptions below).
(iii)Operational Surfaces. Pages such as `/no-quarter`, `/onboarding`, `/sovereignty`, `/manifesto`, and `/pulse` shall cross-reference each other by link. When fact X is canonical to page Y, other pages shall point to Y rather than restate X.
(iv)Source Code. Code comments referring to Company architectural decisions, governance rules, or protocol text shall link to the canonical source (a file path, a commit hash, a Company URL, or a crate-qualified symbol) rather than paraphrase the decision. Comments that paraphrase canonical governance shall be refactored to pointers upon identification.
(v)Commit Messages. Commit messages referencing prior work shall link to the prior commit by hash rather than re-describe the prior work.
(vi)Public Communications. Tweets, posts, replies, and external emails referencing Company positions shall link to the canonical Company URL rather than transcribe the position.
(vii)Constitution Hub. The `/constitution` page is designated the exemplar of this Protocol. It shall list every governance document as a pointer with title and dateline only, with no content duplication. Any reader seeking substance shall click through. The constitution is an index, not a digest.

### (d) Exceptions

Pointer Discipline yields to self-containment in the following circumstances:

(i)Self-Executing Legal Instruments. The Original Agreement itself must be self-contained for execution under Maryland LLC law. An amendment that wishes to modify the Agreement must state its operative changes; it cannot merely link to a GitHub issue describing the intended change. Legal-instrument exceptions are narrow and the Member shall not invoke them to justify general duplication.
(ii)Offline or Print Contexts. Printed slide decks, PDFs intended for offline review, and any document delivered to an audience that cannot follow links at the time of reading may include inline summaries, provided each summary cites the canonical source URL for later verification.
(iii)Safety-Critical and Link-Decay Contexts. Documents whose correctness would be operationally compromised by a broken link (for example, a cert artifact referencing an external hash database) shall include both the link and a hash- or signature-verifiable archival copy of the referenced content, such that an expired link does not destroy the document's integrity.
(iv)Recital Paragraphs. In amendments and other legal instruments, recital paragraphs may contain brief contextual summaries of the state of the world at the time of the instrument. Recitals are interpreted as historical framing, not as canonical statements of ongoing Company position; the canonical statement remains at the linked source.
(v)Audience Accessibility. When a reference would be materially unintelligible without a one-sentence inline gloss (for example, an acronym at first use), a gloss is permitted provided it is explicitly flagged as a reader aid and cites the canonical source. Glosses are not summaries and are not covered by the prohibition.

### (e) Drift and Self-Roast

Drift between a linked canonical source and a summarizing copy on a Company surface is a Company-authored Irony of the Architectural category under Amendment 005 (Protocol P33). Upon identification of such drift, the Member shall:

1. Remove the drifting summary and replace it with a pointer to the canonical source;
2. Self-Roast the drift in the next Company communication where such Self-Roast is contextually appropriate;
3. File the corrective commit with the marker `[P34]` and a link to the original Ironic state.

### (f) Audit Mechanism

The Company shall maintain a public drift-audit surface (for example, `/drift-audit` or an equivalent automated report in the Company binary) that enumerates known instances of content duplication across Company pages. This surface is a Pointer Discipline compliance indicator and is subject to the transparency obligations of Article XXIII of the Original Agreement.

## Section III · Retroactive Application and Remediation Order

Upon execution of this Amendment, the Member shall conduct a Pointer Discipline pass across the existing Company governance stack and remediate observable violations. The remediation order is as follows:

(a)First pass. The `/constitution` page shall be reduced to pointers only. No doc-description text shall remain; each entry shall carry only a title and a link. The Member has executed this pass in conjunction with the execution of this Amendment.
(b)Second pass. Knox-cluster pages (`/no-quarter`, `/onboarding`, `/manifesto`, `/john`) shall add a `/constitution` pointer to their footers (executed concurrently with this Amendment) and shall be reviewed for internal duplication in a subsequent sweep.
(c)Third pass. Company source code shall be audited for paraphrasing comments. Comments that paraphrase canonical governance shall be rewritten as pointers to the canonical URL or file path.
(d)Continuous. All future Company-authored pages, amendments, and commits shall comply with Protocol P34 from the moment of authorship.

## Section IV · Integration with Original Agreement and Other Protocols

(a)Survival. Except as expressly amended herein, all other provisions of the Original Agreement remain in full force and effect.
(b)Protocol Interactions. P34 operates alongside P13 (Compression Mapping — one name, one referent), P15 (Anti-Circular Dependencies — one canonical layer per concern), P26 (Moonshot Frame — reviewer-friendly discipline), P31 (Unbreaking Software — repair over duplication), and P33 (Irony Observation — drift between a pointer and a paraphrase is itself an Irony).
(c)Conflicts. In the event of conflict between this Amendment and any prior Amendment, the prior Amendment controls only to the extent its operative terms are self-executing. Where a prior Amendment's terms depend on a Company practice that P34 reforms, P34 controls going forward and the Member shall update the affected surfaces.
(d)Severability. If any provision of this Amendment is held to be unenforceable or invalid, the remaining provisions shall continue in full force and effect, and the unenforceable provision shall be reformed to the minimum extent necessary to render it enforceable while preserving the original intent of the Member.
(e)Governing Law. This Amendment shall be governed by and construed in accordance with the laws of the State of Maryland, without regard to its conflicts-of-law principles, consistent with Article XVI of the Original Agreement.

## Section V · Execution

The undersigned Member, being the sole Member of The Cochran Block, LLC, acting in such capacity and pursuant to the authority granted in Article XV of the Original Agreement, hereby executes this Amendment as of the Effective Date set forth above.

/s/ Michael Cochran
Michael Cochran
Sole Member · The Cochran Block, LLC
Date: April 16, 2026
ACKNOWLEDGMENT OF PUBLIC DISCLOSURE
This Amendment is published publicly at `cochranblock.org/operations/amendment-006`.
The constitutional index at `cochranblock.org/constitution` is the designated exemplar.
We aren't savages. We have pointers.