Volume Edition · Public

# THE STRATEGIC MASTER LIBRARY

Seven volumes. One discipline.

I DEMOTE CLAIMS II SUBSTRATES, NOT FEATURES III SHIP THE CRYSTAL, KEEP THE SUBSTRATE IV SOFTWARE WITH A SOUL V BUILT TO BE INHERITED VI THE DRIFT WATCH VII SHAPE THE WORLD

Seven volumes · one discipline · pull any spine

- I DEMOTE CLAIMS — Honest documentation is a moat no one can fork.
- II SUBSTRATES, NOT FEATURES — Own the floor other things stand on.
- III SHIP THE CRYSTAL, KEEP THE SUBSTRATE — Export sealed artifacts. Never export the asset.
- IV SOFTWARE WITH A SOUL — Taste, naming, and disclosed fiction compound into a moat.
- V BUILT TO BE INHERITED — Write so a stranger can resume, sell, or sunset your work.
- VI THE DRIFT WATCH — Standing rules keep a solo founder honest when no one else will.
- VII SHAPE THE WORLD — Build the floor so you can afford to give something away — then give it away.

## WHAT THIS IS

The source of this library is a private compendium: twenty-nine full owner's manuals for twenty-nine shipped and shipping projects, written in one voice by one founder, each manual audited against the live code it describes. That compendium is organized by project, because its job is retrieval — look up any capability, decision, or asset in one place.

This edition is organized by message, because its job is transfer. The same corpus, cut along a different axis: not "here is everything about project X," but "here is one thing this whole body of work proves, with the receipts."

Each volume makes a single argument. The projects appear inside the volumes as exhibits — evidence, not chapters. A project may appear in three volumes and be seen three different ways, which is the point: a portfolio is not a list of things, it is a set of lessons that happen to have running code attached.

## WHO IT IS FOR

Solo builders, small teams, and anyone documenting a body of work they intend to outlive. Nothing in these volumes requires access to the source projects. Every practice section is written to be applied to your work, not to admire someone else's.

## THE TRUTH LEGEND

Claims carried over from the source manuals keep their original truth tags. They mean the same thing everywhere they appear:

- CONFIRMED — Directly verifiable in the codebase, database, or shipped product.
- OBSERVED — Present in committed docs, migrations, or memory files; load-bearing intent.
- INFERRED — Synthesized from multiple sources; reasonable but not directly stated.
- PLANNED — Explicit roadmap item, not yet shipped.
- SPECULATIVE — Strategic projection or vision. Not a promise.
- NEEDS CONFIRMATION — A gap; verify before quoting externally.

The rule that governs them all: demote claims, do not promote them. When in doubt, a claim moves down the ladder, never up.

## THE TOOLKIT

The volumes describe the method. The toolkit ships it — the same two-stage instrument that produced all twenty-nine source manuals, generalized for your projects:

- Stage One — the Owner's Manual Patch generates the eighteen-section manual: truth labels inline, phased from source intake to a print-ready render.
- Stage Two — the Truth Audit Patch is the forensic pass: demote claims, publish the diff, score the result.

Run One, then Two, against your own project in your own AI session. Fill in your identity block — the manuals you produce are yours; the method carries its credit line. This is Volume I and Volume V in executable form.

## WHAT WAS LEFT OUT

This is a public edition distilled from a confidential source. Broker relationships, named contacts, valuation figures, patent application numbers, inheritance mechanics, security-testing targets, and internal infrastructure details were deliberately excluded. The full dossiers remain the founder's private canon. What ships here is the method — which is the part that transfers.