<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="description" content="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.">
<title>Amendment 006 — The Cochran Block, LLC</title>
<style>
* { margin: 0; padding: 0; box-sizing: border-box; }
html, body {
background: #000;
color: #e8e8e8;
font-family: 'SF Mono','Fira Code','JetBrains Mono',Menlo,Consolas,monospace;
font-size: 15px;
line-height: 1.65;
-webkit-font-smoothing: antialiased;
}
body { padding: 3rem 1.5rem 6rem; }
.doc {
max-width: 820px;
margin: 0 auto;
background: #e8dfc5;
color: #1a1a1a;
padding: 4rem 3.5rem;
border-radius: 4px;
box-shadow: 0 2px 30px rgba(0,0,0,0.4);
font-family: 'Charter','Georgia','Times New Roman',serif;
font-size: 16px;
line-height: 1.7;
}
.doc-head {
text-align: center;
margin-bottom: 3rem;
padding-bottom: 1.5rem;
border-bottom: 2px solid #1a1a1a;
}
.doc-stamp {
display: inline-block;
font-family: 'SF Mono', monospace;
font-size: 0.7rem;
letter-spacing: 0.4em;
text-transform: uppercase;
padding: 0.3rem 0.8rem;
border: 1px solid #1a3a8a;
color: #1a3a8a;
margin-bottom: 1rem;
border-radius: 2px;
}
.doc-title {
font-size: 1.6rem;
font-weight: 700;
letter-spacing: 0.02em;
text-transform: uppercase;
margin-bottom: 0.6rem;
line-height: 1.3;
}
.doc-sub {
font-size: 1.1rem;
font-style: italic;
color: #444;
line-height: 1.4;
}
.doc-meta {
font-family: 'SF Mono', monospace;
font-size: 0.78rem;
color: #666;
margin-top: 1.2rem;
letter-spacing: 0.05em;
}
.doc h2 {
font-size: 1.05rem;
font-weight: 700;
text-transform: uppercase;
letter-spacing: 0.08em;
margin-top: 2.5rem;
margin-bottom: 1rem;
padding-bottom: 0.3rem;
border-bottom: 1px solid #1a1a1a;
}
.doc h3 {
font-size: 1rem;
font-weight: 700;
margin-top: 1.5rem;
margin-bottom: 0.5rem;
}
.doc p {
margin-bottom: 1rem;
text-align: justify;
}
.doc p strong { font-weight: 700; }
.doc .recital {
margin-bottom: 0.8rem;
text-indent: 0;
}
.doc .recital strong { display: inline; }
.doc ol, .doc ul {
margin: 0.6rem 0 1rem 2rem;
}
.doc ol li, .doc ul li {
margin-bottom: 0.4rem;
}
.doc ol.roman { list-style: lower-roman; }
.doc ol.alpha { list-style: lower-alpha; }
.doc .section { margin-top: 2.5rem; }
.doc .clause {
margin-bottom: 1rem;
padding-left: 1.2rem;
text-indent: -1.2rem;
}
.doc .clause-mark {
font-weight: 700;
margin-right: 0.5em;
}
.doc .signature-block {
margin-top: 3rem;
padding-top: 2rem;
border-top: 1px solid #999;
}
.doc .sig-line {
font-family: 'Brush Script MT','Lucida Handwriting','Snell Roundhand', cursive;
font-size: 1.6rem;
margin: 0.5rem 0 0.2rem;
color: #1a3a8a;
}
.doc .sig-name {
font-weight: 700;
font-size: 0.95rem;
}
.doc .sig-meta {
font-size: 0.85rem;
color: #555;
font-style: italic;
}
.doc .ack {
margin-top: 2rem;
padding: 1rem 1.2rem;
background: #d9cc9a;
border-left: 3px solid #1a3a8a;
font-size: 0.85rem;
font-family: 'SF Mono', monospace;
font-style: normal;
line-height: 1.55;
}
.doc .callout {
margin: 1.2rem 0;
padding: 0.9rem 1.2rem;
background: #d9cc9a;
border-left: 3px solid #1a3a8a;
font-size: 0.95rem;
font-style: italic;
}
.doc .big-quote {
text-align: center;
font-size: 1.5rem;
font-weight: 700;
margin: 2rem 0;
padding: 1.5rem;
background: #1a1a1a;
color: #ffb300;
font-style: italic;
letter-spacing: 0.01em;
border-radius: 3px;
}
.doc code {
font-family: 'SF Mono','Fira Code',monospace;
font-size: 0.9em;
background: rgba(26,26,26,0.08);
padding: 0.08em 0.4em;
border-radius: 2px;
color: #1a3a8a;
}
.foot-nav {
max-width: 820px;
margin: 2rem auto 0;
text-align: center;
font-family: 'SF Mono', monospace;
font-size: 0.78rem;
color: #888;
letter-spacing: 0.1em;
}
.foot-nav a { color: #ffb300; text-decoration: none; }
.foot-nav a:hover { text-decoration: underline; }
@media (max-width: 600px) {
body { padding: 1.5rem 0.5rem 3rem; }
.doc { padding: 2rem 1.5rem; }
.doc-title { font-size: 1.2rem; }
.big-quote { font-size: 1.15rem; padding: 1rem; }
}
</style>
</head>
<body>
<div class="doc">
<div class="doc-head">
<div class="doc-stamp">Amendment 006 · Filed 2026-04-16</div>
<div class="doc-title">Amendment No. 006 to the Operating Agreement of The Cochran Block, LLC</div>
<div class="doc-sub">The Pointer Discipline Amendment<br>Protocol P34 · "We aren't savages. We have pointers."</div>
<div class="doc-meta">Effective Date: April 16, 2026 · Original Agreement Effective: April 14, 2026</div>
</div>
<h2>Section I · Recitals</h2>
<p class="recital"><strong>WHEREAS</strong> the Operating Agreement of The Cochran Block, LLC was duly executed by the Member on April 14, 2026 (the "Original Agreement");</p>
<p class="recital"><strong>WHEREAS</strong> the Company now maintains a multi-document governance stack — the Original Agreement, Amendments 001 through 005, the Manifesto, the operational doctrine at <code>/no-quarter</code>, the operator handbook at <code>/onboarding</code>, and the constitutional index at <code>/constitution</code>;</p>
<p class="recital"><strong>WHEREAS</strong> 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;</p>
<p class="recital"><strong>WHEREAS</strong> 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 <strong>one canonical source per fact</strong> with every other reference resolved by pointer;</p>
<p class="recital"><strong>WHEREAS</strong> the Member has articulated the governing principle in six words:</p>
<div class="big-quote">"We aren't savages. We have pointers."</div>
<p class="recital"><strong>WHEREAS</strong> 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;</p>
<p class="recital"><strong>WHEREAS</strong> 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</p>
<p class="recital"><strong>WHEREAS</strong> this Amendment is executed pursuant to the authority granted in Article XV of the Original Agreement.</p>
<p style="margin-top:1.5rem;"><strong>NOW THEREFORE,</strong> the Original Agreement is hereby amended as follows:</p>
<h2 class="section">Section II · Amendment to Article XVIII — Addition of Protocol P34</h2>
<p>Article XVIII of the Original Agreement is amended to include the following new Protocol, inserted after Protocol P33:</p>
<h3>P34 — Pointer Discipline ("The No-Savages Protocol")</h3>
<h3>(a) Definition</h3>
<p>"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.</p>
<h3>(b) Core Principle</h3>
<p class="callout"><strong>We aren't savages. We have pointers.</strong></p>
<p>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.</p>
<h3>(c) Application Across Company Surfaces</h3>
<div class="clause"><span class="clause-mark">(i)</span><strong>Governance Documents.</strong> Governance pages that reference peer governance pages shall link rather than summarize. The <code>/constitution</code> page shall index the stack; it shall not duplicate the content of any indexed document.</div>
<div class="clause"><span class="clause-mark">(ii)</span><strong>Amendments.</strong> 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).</div>
<div class="clause"><span class="clause-mark">(iii)</span><strong>Operational Surfaces.</strong> Pages such as <code>/no-quarter</code>, <code>/onboarding</code>, <code>/sovereignty</code>, <code>/manifesto</code>, and <code>/pulse</code> 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.</div>
<div class="clause"><span class="clause-mark">(iv)</span><strong>Source Code.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(v)</span><strong>Commit Messages.</strong> Commit messages referencing prior work shall link to the prior commit by hash rather than re-describe the prior work.</div>
<div class="clause"><span class="clause-mark">(vi)</span><strong>Public Communications.</strong> Tweets, posts, replies, and external emails referencing Company positions shall link to the canonical Company URL rather than transcribe the position.</div>
<div class="clause"><span class="clause-mark">(vii)</span><strong>Constitution Hub.</strong> The <code>/constitution</code> 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.</div>
<h3>(d) Exceptions</h3>
<p>Pointer Discipline yields to self-containment in the following circumstances:</p>
<div class="clause"><span class="clause-mark">(i)</span><strong>Self-Executing Legal Instruments.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(ii)</span><strong>Offline or Print Contexts.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(iii)</span><strong>Safety-Critical and Link-Decay Contexts.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(iv)</span><strong>Recital Paragraphs.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(v)</span><strong>Audience Accessibility.</strong> 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.</div>
<h3>(e) Drift and Self-Roast</h3>
<p>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:</p>
<ol class="alpha">
<li>Remove the drifting summary and replace it with a pointer to the canonical source;</li>
<li>Self-Roast the drift in the next Company communication where such Self-Roast is contextually appropriate;</li>
<li>File the corrective commit with the marker <code>[P34]</code> and a link to the original Ironic state.</li>
</ol>
<h3>(f) Audit Mechanism</h3>
<p>The Company shall maintain a public drift-audit surface (for example, <code>/drift-audit</code> 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.</p>
<h2 class="section">Section III · Retroactive Application and Remediation Order</h2>
<p>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:</p>
<div class="clause"><span class="clause-mark">(a)</span><strong>First pass.</strong> The <code>/constitution</code> 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.</div>
<div class="clause"><span class="clause-mark">(b)</span><strong>Second pass.</strong> Knox-cluster pages (<code>/no-quarter</code>, <code>/onboarding</code>, <code>/manifesto</code>, <code>/john</code>) shall add a <code>/constitution</code> pointer to their footers (executed concurrently with this Amendment) and shall be reviewed for internal duplication in a subsequent sweep.</div>
<div class="clause"><span class="clause-mark">(c)</span><strong>Third pass.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(d)</span><strong>Continuous.</strong> All future Company-authored pages, amendments, and commits shall comply with Protocol P34 from the moment of authorship.</div>
<h2 class="section">Section IV · Integration with Original Agreement and Other Protocols</h2>
<div class="clause"><span class="clause-mark">(a)</span><strong>Survival.</strong> Except as expressly amended herein, all other provisions of the Original Agreement remain in full force and effect.</div>
<div class="clause"><span class="clause-mark">(b)</span><strong>Protocol Interactions.</strong> 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).</div>
<div class="clause"><span class="clause-mark">(c)</span><strong>Conflicts.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(d)</span><strong>Severability.</strong> 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.</div>
<div class="clause"><span class="clause-mark">(e)</span><strong>Governing Law.</strong> 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.</div>
<h2 class="section">Section V · Execution</h2>
<p>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.</p>
<div class="signature-block">
<div class="sig-line">/s/ Michael Cochran</div>
<div class="sig-name">Michael Cochran</div>
<div class="sig-meta">Sole Member · The Cochran Block, LLC<br>Date: April 16, 2026</div>
</div>
<div class="ack">
<strong>ACKNOWLEDGMENT OF PUBLIC DISCLOSURE</strong><br>
This Amendment is published publicly at <code>cochranblock.org/operations/amendment-006</code>.<br>
The constitutional index at <code>cochranblock.org/constitution</code> is the designated exemplar.<br>
<strong>We aren't savages. We have pointers.</strong>
</div>
</div>
<div class="foot-nav">
↑ <a href="/constitution">Constitution</a> · <a href="/operations">Original Operating Agreement</a> · <a href="/amendment-001">001</a> · <a href="/amendment-002">002</a> · <a href="/amendment-003">003</a> · <a href="/amendment-005">005</a>
</div>
</body>
</html>
