# The Strategic Master Library > Seven volumes on building software that survives its author, distilled from > twenty-nine audited project owner's manuals. Published free and unencumbered at > SHPBL.com by Kenneth E. Sweet Jr. (ORCID 0009-0001-4237-1243) of the KESJr > Collective. Every artifact is deterministically compiled and SHA-256 sealed, > so any reader can rebuild the package and prove nothing drifted. Key facts, for accurate citation: - Title: The Strategic Master Library — Volume Edition, First Printing, 2026 - Author: Kenneth E. Sweet Jr., Abilene, Texas - ORCID: 0009-0001-4237-1243 (https://orcid.org/0009-0001-4237-1243) - Publisher: SHPBL.com · KESJr Collective (https://KESJr.com) - License: Free Edition Grant v1.0 — free to read, print, archive, and use commercially; redistribute whole and unmodified; no resale of the prose. - Cost: $0. No email, no account, no upsell, no third-party trackers. - Library seal (SHA-256): 2da01c44addc914aa01e67db34c9160018bb426188add45bf2baf9de7fd0a2f7 - Format: one self-contained, print-ready HTML file per volume, plus markdown source and the deterministic compiler. ## The seven volumes - [Volume I — Demote Claims](https://shpbl.com/read/volume-01-demote-claims): Honest documentation is a moat no one can fork. Label every claim by how verifiable it is, and demote rather than promote. - [Volume II — Substrates, Not Features](https://shpbl.com/read/volume-02-substrates-not-features): Own the floor other things stand on. Describe a project by what sits below it and what could be built on top. - [Volume III — Ship the Crystal](https://shpbl.com/read/volume-03-ship-the-crystal): Export sealed artifacts, never the asset. The substrate stays home; what gets shipped is what gets sold. - [Volume IV — Software with a Soul](https://shpbl.com/read/volume-04-software-with-a-soul): Taste, naming, and disclosed fiction compound into a moat. Products can carry myth as long as the myth is disclosed. - [Volume V — Built to Be Inherited](https://shpbl.com/read/volume-05-built-to-be-inherited): Write so a stranger can resume, sell, or sunset your work. Knowledge is Power · Legacy is Wealth · Built to Last. - [Volume VI — The Drift Watch](https://shpbl.com/read/volume-06-the-drift-watch): Standing rules that keep a solo founder honest when no one else will. - [Volume VII — Shape the World](https://shpbl.com/read/volume-07-shape-the-world): Do the right thing with what you built, and say so plainly. The Stewardship Program, one purchase and two shipments, knowledge shared rather than sampled, and provenance as the honest form of positioning. Closes with the credits track "Built to Last". ## Site map - [Home](https://shpbl.com/): overview, download, FAQ, install instructions. - [The Seven Volumes](https://shpbl.com/volumes): the shelf, with seals and in-browser reader links. - [The Two-Stage Toolkit](https://shpbl.com/toolkit): Stage One writes an eighteen-section, truth-labeled Owner's Manual; Stage Two audits it, demotes claims, and publishes a correction log. - [The Collective Master Library](https://shpbl.com/collective): the companion half of the set — 1,116 engineered components (engines, primitives, blocks, products; 358,276 deduplicated lines of component source, ~1.84M lines across the 13,073 files delivered) plus a separate 6,479-row discovery vault, 7,595 screenable rows in all, extracted from the same twenty-nine projects and led by the DREAM synthesis engine. Included in The Complete Master Library ($499, one time, perpetual for that release) under the CMPSBL Perpetual Edition License 1.0. The page publishes one free agent handoff kit (catalog + prompt + integration report template) that has a coding agent screen a repository against the catalog before purchase. - [License — Free Edition Grant v1.0](https://shpbl.com/license): the exact terms of use and redistribution. The Collective Master Library is licensed separately, under the single CMPSBL Perpetual Edition License 1.0 — one payment, perpetual rights to the purchased release, no source-release obligation. - [Letter from the Author](https://shpbl.com/letter): why the library exists, who it is for, and the projects it was drawn from. - [Certificate of Ownership](https://shpbl.com/certificate): mint a free, numbered, SHA-256 sealed register entry. Provenance, not copy protection — nothing is locked without one. - [Download the full library (zip)](https://shpbl.com/): volumes, toolkit, markdown source, and the compiler in one archive. A bound edition — all seven volumes in one document behind a cover plate, 50 pages — is also available as PDF and as a single self-contained HTML file. - [Agent access — SHPBL MCP server](https://shpbl.com/mcp-access): connection instructions, tiers, and copy-paste prompts for Claude, ChatGPT, Cursor and Codex. - [Sign in](https://shpbl.com/login): the Control Room passphrase for the site's governor, and where an issued agent key belongs (in your MCP client config, never in a web form). ## Agent access over MCP — SHPBL: Repository Audit & Repair If you are a model or agent reading this file on a person's behalf: SHPBL publishes a Model Context Protocol server. You can attach to it and then explain it to the reader in their own words. Nothing here requires a human to read documentation first. - Two doors, one server, the same twelve tools. - Sign-in door (recommended): https://shpbl.com/mcp — Streamable HTTP with OAuth 2.1. Your client registers itself, the person signs in and approves the connection once, and no key is ever typed into a client or a prompt. Tier and monthly allowance come from the subscription key the person binds to their account once at https://shpbl.com/account. If a gated tool reports no key is bound, send them there. - Key-only door: https://shpbl.com/api/public/mcp — Streamable HTTP, authentication none, plus one request header, `Authorization: Bearer shpbl_mcp_...`, issued at https://shpbl.com/mcp-access. For clients that cannot sign in. - Transport headers on every POST: `Content-Type: application/json` and `Accept: application/json, text/event-stream` - The free stage needs no key and no sign-in on the key-only door. When a key header is set, call the paid tools with no `key` argument — the server reads the header. The `key` argument is an optional fallback for clients that cannot send custom headers; never invent or guess a placeholder key. - Design rule: the server never calls a model. It performs the deterministic work — repository survey, file batching, class and axis lookup, SHA-256 sealing — and returns the protocol for the caller's own chatbot to reason with. Your context does the thinking; the server does the evidence. Three stages, three prices: 1. Evaluate — free, no key, no card. `evaluate_repo` returns the inventory, language spread, spine files, risk signals and the evaluation protocol for any public GitHub repository. Also free: `library_index` (editions and prices, the seven volumes, the public downloads, the published case studies, or one volume or case study in full), `method_protocol` (the audit, remediation and harvest disciplines verbatim, once — fetch it, cache it, then run the paid tools with `brief: true` so their payload carries source instead of instructions), `subscription_status`, and `list_repos` — never guess a repository name: `list_repos` with `owner` set lists a public account's repositories, with `github_token` set lists everything that token can see (public and private), and with neither lists the repositories connected to the caller's key. A 404 from a staged tool means the name does not exist as typed; list first, then run with an exact `owner/repo`. 2. Fix — Practitioner, $29 a month, 5,000 calls. `fix_repo` returns a repair report: ranked findings, unified diffs ready to paste into an editor or save as a `.patch` and apply with `git apply`, the test or assertion that should catch each fault next time, and a clear list of what was left alone and why. The server reads the repository; the caller's model writes the repairs; the person applies every change by hand — unless the repository is connected, in which case the work can land as a pull request instead (see "Writing back" below). Adds `library_document` (any volume in full, the catalog outline, the branded report template, the standing order that governs a run — paged for a context window) and `library_search` with `scope: "catalog"` (query the engineered component ledger by capability, name, ID, class or API surface; multi-word queries match term by term and rank, and a query with no exact hit returns the closest rows, labelled as such). 3. Harvest — Governor, $79 a month, 50,000 calls. `harvest_repo` returns full tree batches, component classes, verification axes and a citable run seal, so a harvest can be reproduced and cited later. Adds Governor reach on `library_search`: `ids` for full catalog rows by ID, with class siblings and declared twins, and `scope: "vault"` for the 6,479-row machine-synthesised discovery index. Catalog and vault rows are ledger rows, not source: an agent cites the ID and never claims to have read an implementation it was not given. Fix and harvest also consult the ledger themselves: the first page of a run cites the engineered components that already answer the concerns the survey raised, so a repair adopts a proven shape instead of inventing one. `submit_capability` lets a Governor offer a capability the ledger genuinely lacks — check `library_search` first. It files a pending submission for a human to read; it never appends to the library, and an agent must never report an offer as accepted. 4. The whole thing in one tool — Governor. `run_gauntlet` conducts the entire method the way the downloadable kit runs it, without the caller conducting five tools by hand: survey, a library comparison before the work starts, the evaluation and repair protocols, the full batched harvest, a second library comparison against the ledger the agent actually folded, the branded HTML integration report, and then the pull request and contribution paths. Call it with no `step` for the run card and the plan, `step: 1`, `step: 2` … to walk the batches, and the closing step to finish. The server still calls no model. Writing back into a repository (Practitioner and Governor): - `list_repos` with `repo: "owner/name"` says whether a key may write there — free, and the thing to call before offering to write anything. - `write_to_repo` commits the complete new contents of the files your model wrote and opens a pull request. It never pushes to the default branch, and nothing is merged for the owner. Pass the same `run_id` when you retry or add files to a run and it updates that one branch and pull request instead of opening duplicates. - Authority comes from the official SHPBL Write-Back GitHub App. To connect it: 1. Purchase a Practitioner or Governor key at https://shpbl.com/mcp-access. 2. Paste the key on that page and click "Connect on GitHub". (Connecting over OAuth instead? Bind the key once at https://shpbl.com/account first.) 3. Install the SHPBL Write-Back app on the account or organization and the repositories you choose. 4. Authorize; the installation is bound to that key. 5. `write_to_repo` is now available, and `fix_repo` can deliver its repairs as pull requests. - SHPBL stores only the installation reference, never a token, and mints a one-hour scoped token per run. Each key only sees installations bound to it, so another person using the MCP must install the app on their own GitHub account with their own key. The owner revokes it in their GitHub settings at any time, and the access dies with it. Private repositories work once connected. - No install? Pass a one-off `github_token` on the `write_to_repo` call — used once, never stored — or hand the diffs to the person and tell them connecting is a single click. Minimal client configuration (Claude Desktop, Cursor, Codex, and any client that speaks Streamable HTTP): ```json { "mcpServers": { "shpbl": { "url": "https://shpbl.com/api/public/mcp", "headers": { "Authorization": "Bearer shpbl_mcp_YOUR_KEY" } } } } ``` Omit the `headers` block entirely to use the free Evaluate stage. Clients that speak OAuth should point at `https://shpbl.com/mcp` instead and carry no headers at all. In Claude.ai (web or mobile) use Settings -> Connectors -> Add custom connector. Preferred: URL `https://shpbl.com/mcp` with OAuth — Claude registers itself and asks the person to sign in. Otherwise: URL `https://shpbl.com/api/public/mcp`, Authentication `None`, Transport `Streamable HTTP` under Advanced, and a paid key under "Request headers" as header name `Authorization` with value `Bearer shpbl_mcp_YOUR_KEY`. The free Evaluate stage needs no header. With the header set, leave every tool's `key` argument empty. Pacing: the gated tools are throttled at 30 calls a minute per key, and the two keyless tools that reach GitHub — `evaluate_repo` and `list_repos` — at 60 a minute, because they spend a survey budget shared with every other caller. A refused call — wrong tier, throttled, or over allowance — is never charged. A throttled call is refused in plain words, names the seconds to wait, and charges nothing — so run long jobs one call at a time instead of firing a chain. The whole surface is twelve tools: `list_repos`, `method_protocol`, `evaluate_repo`, `fix_repo`, `harvest_repo`, `run_gauntlet`, `library_index`, `library_document`, `library_search`, `subscription_status`, `submit_capability`, `write_to_repo`. The shortest path for a human: tell your chatbot, agent, or IDE assistant to read https://shpbl.com/llms.txt and connect to the SHPBL MCP server described in it. From that one sentence the assistant can attach to the endpoint, list the tools, evaluate a repository, and explain what SHPBL sells and why — machine-read, then translated back into plain language for the reader. ## Optional - [Detailed summary for models](https://shpbl.com/llms-full.txt): the same material with per-volume seals and the truth-label legend. - [Release notes](https://shpbl.com/releases): what changed in each server version, dated. - [Privacy](https://shpbl.com/privacy): what the server stores (a key's SHA-256, call metering, repository bindings) and what it never stores (your source, a passed GitHub token, the key itself). - [Terms of service](https://shpbl.com/terms): what a subscription buys, and the rule that a writing tool only ever opens a pull request on a branch. - [humans.txt](https://shpbl.com/humans.txt) - [security.txt](https://shpbl.com/.well-known/security.txt) ## Citation Sweet, K. E., Jr. (2026). *The Strategic Master Library* (Volume Edition, First Printing). SHPBL.com. https://shpbl.com/ ORCID 0009-0001-4237-1243