The companion half of the set
The Collective
Master Library
The seven volumes on this site are the argument. This is the parts bin the argument was made with — 1,000+ engineered components and a separate set of 3,000+ runnable capability units — drawn from the same twenty-nine projects the volumes cite as exhibits, sealed, catalogued, and licensed so they can sit inside your software instead of only being described in a book.
Included inside The Complete Master Library — $499, one time, perpetual for that release. The evaluation download on this page is free, and answers the only honest question: would any of it actually help your codebase?
The library at a glance
1,000+
Engineered components
Admitted catalogue components, counted apart from capability units
3,000+
Capability units
Runnable capability units your agent composes from
25
Composites, counted apart
Invented mid-run across 6 published evaluations — designs with a report, not shipped rows. Grown only by our own governed runs; whatever your runs compose stays in your repository
1,068
Plain imports
`direct` mode — no runtime, no init step
ALL
Install & type-check
Every engineered component records `I:ok` in a bare host project
Durable floors shown throughout SHPBL: 1,000+ engineered components and 3,000+ runnable capability units. They are different evidence classes and are never summed.
Lead exhibit · PRIM-ENG-01
DREAM
It has been in this Canon since November 2025, sealed and dated — which matters only because the industry arrived at the same idea later and independently. That is not a claim of influence. It is a claim of timestamp, and the seal chain is what makes it checkable rather than a story. Volume I would demote it otherwise.
748 entry LOC · self-contained · one adapter port (PORT-PERSISTENCE) you implement · verified C:proj(12) I:ok B:exec, with test coverage and security review Not claimed.
CANDIDATE GATES CATALOGUE
───────── ───── ─────────
capability unit ──▶ [1] parse + conformance ──▶ rejected ✕
│ passes
▼
[2] licence + origin ──▶ rejected ✕
│ clean
▼
[3] human decision ──▶ deferred ⟳
│ accepted
▼
engineered component ──▶ counted, cited, shipped ✔
counted separately, never summed: capability units ≠ components- ✕Refused at a gate. Most rows end here, and that is the point.
- ⟳Held for a later run rather than waved through.
- ✔In the catalogue: named, versioned, licensed, reusable.
What else is in there
DREAM
Rule-based, no-model synthesis engine that runs on idle cycles, mines signals below the confidence floor everyone else discards, and clusters them into novel patterns.
PRIM-ENG-01 · The crown jewel. In this Canon since November 2025. Self-contained — one adapter port (PORT-PERSISTENCE) you implement.
748 entry LOC
Creative Forge
Full creative stack — imagination, innovation and dream engines fused for generative synthesis, pattern evolution, and nocturnal optimization.
MENGINE-CREATIVE-FORGE · Meta-engine. Plain import; shared entry with its class; one persistence port you implement.
727 entry LOC
World-First Cognitive
BRAIN attention and memory, DECODE intent understanding, and DREAM creative evolution unified into one cognitive layer.
MENGINE-WORLD-FIRST-COGNITIVE · Meta-engine. Plain import.
727 entry LOC
Creative Evolution Engine
Genetic-algorithm knowledge mutation, insight crystallization into permanent memory, emergent pattern evolution, and dream-state analysis.
SENGINE-CREATIVE-EVOLUTION-ENGINE · Substrate engine. Shared runtime closure across the class.
1,890 entry LOC
Temporal Engine
Temporal causal chains, chronological event synthesis, time-aware pattern detection, lifecycle state prediction, and temporal memory indexing.
SENGINE-TEMPORAL-ENGINE · Substrate engine. Shared runtime closure across the class.
1,890 entry LOC
Dream Synthesizer
Offline memory consolidation — decay, prune, strengthen, merge. Turns raw experience traces into compacted long-term memory.
BLD-ENG-260 · The DREAM idea at its smallest, extractable on its own with no dependencies.
106 entry LOC
On the shelf, not in a chat log
A library you can point at, six months later.
Each kept capability lands on a shelf with a name, a citation and a licence, readable by the next agent that opens the repository. Chat logs are not a library.
Before you spend anything
Hand it to your agent
One download: thirteen agent-workflow files plus four reference documents. PROMPT.md is the standing order — attach the kit, say “follow the kit”, and the agent runs the whole assignment unasked. AGENT-HANDOFF-CATALOG.md carries the instructions, the licence rules, the method, the full component catalogue and the prompt — PART 3 is PART 1 verbatim, so the attachment and the pasted prompt can never disagree. If your agent's context window cannot hold the merged catalog, the same content ships split into three phase files, each row extracted by the build rather than retyped, so the two cannot drift. Your agent fills in the bundled template and leaves a branded, self-contained HTML report — plus a Markdown twin for code review — at your repo root.
If the report comes back "not much here," you have saved your money. That is the intended outcome for plenty of codebases, and the template is written so an agent is free to say it.
The single download · kit r3.4.0
947 KB · ZIP↓
The agent handoff kit
PROMPT.md→ your coding agent
The standing order: the exact instruction the agent executes with no human prompting. Attach it and say nothing more than “follow the kit”.
AGENT-HANDOFF-CATALOG.md→ your coding agent
The merged catalog: instructions, licence rules, terms, method, the complete component catalogue, the discovery-library index, and the copy-paste prompt in PART 3.
CATALOG-PHASES.md→ your coding agent
Router for the three-phase read path — which phase file to read when, for agents that cannot hold the merged catalog.
CATALOG-PHASE-1-DIRECTIVES.md→ your coding agent
Phase 1 — standing order, assignment, price, licence rules, Step 0. No components.
CATALOG-PHASE-2-SHORTLIST.md→ your coding agent
Phase 2 — class and capability indexes plus one compact row per component: id, name, mode, LOC, verification, constraints.
CATALOG-PHASE-3-COMPONENTS.md→ your coding agent
Phase 3 — the full component rows verbatim, including what each does and its API surface.
DISCOVERY-VAULT-INDEX.md→ nobody — retained for continuity
Legacy index, kept in the tree for continuity only. The pool it describes is retired: nothing on the server reads it, its total is never quoted as library size, and an agent should not screen from it. Screen the component catalogue instead.
INTEGRATION-REPORT-TEMPLATE.html→ your coding agent
The report skeleton the agent must fill in — every {{TOKEN}} replaced, no external assets, opens from file://.
AGENTS.md→ your coding agent
Standing operating rules: rule 0 (the standing order), ground rules, licence pointer, the Step 0 licence-conflict check with its host-licence verdict table, integration procedure.
ROOT-OF-TRUST.md→ you and your reviewer
What the checksums prove and what they cannot: the root hash, why the seal is checksums only with no signature claimed, and how to anchor the tree out of band.
SECURITY-SCAN.md→ you and your reviewer
The 31-rule repeatable sweep across both collections — 0 high, 19 medium delivery-wide — and exactly what that does and does not mean.
LICENSE→ you and your legal reviewer
The CMPSBL® Perpetual Edition License 1.0, verbatim — the single licence covering every delivered file.
EXAMPLE-INTEGRATION-REPORT.html→ you
A filled-in report, so you can see what a finished evaluation looks like before your agent writes one.
LICENSING.md→ you
The licence in one page: what it permits, and what needs written permission.
docs/LICENSE-COMPATIBILITY.md→ you and your legal reviewer
The host-licence verdict detail behind Step 0 — MIT, BSD, Apache-2.0, MPL, GPL and proprietary hosts, each with an answer.
docs/TAXONOMY.md→ your coding agent
The canonical primitive taxonomy: the 40 primitives every capability unit is classified against.
README.md→ you
Three steps, and how to check the delivered report.
The HTML catalog is typeset, searchable and prints to PDF — for you, not your agent. It is deliberately kept out of the kit so an agent never reads the catalog twice. Your agent gets the same document as plain Markdown (3.6 MB), inside the kit.
Look inside first
4 parts · 35 sections · 1,068 rows
What is in the catalog
PART 1 — THE ASSIGNMENT
- Pricing and terms
- How to read a catalog row
- If the host repo is not TypeScript
- Verification axes
- How to read the LOC columns
- Costing rules
- + 5 more
PART 2 — THE CATALOG
- Index
- Find by capability
- CrownJewel/S-Tier
- CrownJewel/S-Tier-Unregistered
- Primitive/Organ
- Primitive/Layer
- + 17 more
PART 3 — COPY-PASTE PROMPT
PART 4 — THE DISCOVERY VAULT (retired section)
- Retired pool. Kept only so the shipped document's structure is described in full: nothing on the server reads it, no count includes it, and its former total is never quoted as library size.
Not a TypeScript repo? The delivery ships a polyglot bridge generator — 19 languages plus 7 hardware/HDL targets, no install, no network. TypeScript stays canonical.
1
Attach
Give your coding agent PROMPT.md, AGENT-HANDOFF-CATALOG.md, AGENTS.md and INTEGRATION-REPORT-TEMPLATE.html, in the repository you want evaluated. Tight context window? Attach CATALOG-PHASES.md and the three phase files instead of the merged catalog.
2
Say “follow the kit”
PROMPT.md is the standing order — the agent runs the whole assignment unasked. If your tool needs a prompt separately, paste PROMPT.md or PART 3 of the catalog.
3
Collect
COLLECTIVE-MASTER-LIBRARY-INTEGRATION-REPORT.html lands at your repo root, with a Markdown twin for code review. Self-contained, no network, prints to PDF, reads on a phone.
What the delivered report must contain
- ·No surviving {{TOKEN}} placeholders — a remaining one is a defect.
- ·A Step 0 licence verdict for your repository — integrate, or STOP with the reason named — reached before a single call is wired.
- ·The commit SHA it evaluated, in the masthead — or a plain statement that it could not pin one.
- ·Coverage stated with numbers: rows parsed, rows matched, rows read in full, rows recommended. Sampling admitted rather than implied.
- ·REPLACE / HARDEN / SKIP per candidate, mapped to your own file paths.
- ·A SKIP list. An evaluation with no skips did not evaluate anything.
- ·Net LOC delta, plus each component's verification tokens quoted verbatim — every unproven axis reading “Not claimed” in those two words.
- ·Adapter ports named as work you must schedule — never as included.
- ·Net-new components designed by composing catalog pieces against your codebase.
If your agent returns an enthusiastic list of every component with no constraints, no skips and no ports — re-run it with PART 3 verbatim. It summarized instead of evaluating.
$499, one time · No subscription and no per-seat metering. The Collective Master Library ships inside The Complete Master Library — one payment, perpetual rights to the purchased release. Thirteen @cmpsbl/* packages published to npm under Apache-2.0 before the relicensing stay Apache-2.0 as published there.
What it will not tell you
That is a real claim and a bounded one — Volume I's rule applied to the author's own storefront. Every artifact carries six verification axes, and unproven axes read Not claimed rather than being quietly left blank. If an agent tells you a component is "secure" or "production-proven for your use case," ask it which verification field it based that on.
LICENSE · LicenseRef-CMPSBL-Perpetual-1.0 — One licence covers every delivered file: the CMPSBL® Perpetual Edition License 1.0. Use it internally with no seat limits, modify it and keep your changes private, and embed it in a product you sell, provided that product has substantial independent function. No source-release obligation, ever — the earlier AGPL-or-commercial model is retired. Reselling, mirroring or republishing the Library itself needs written permission. Attribution to Kenneth E. Sweet Jr. stays in your documentation. Standalone resale of a component, or a product whose principal function is a component's function, needs written permission. That is a different license from the Free Edition Grant covering the volumes on this site.
Licensed Edition · One licence, one door · v3.4.0
Own the parts, not just the book
The volumes stay free forever. The components are the half you license — and the whole delivery ships inside The Complete Master Library, purchased once at $499 and licensed perpetually for that release.
- 1,000+Engineered components
Admitted, named software components in the shipped catalogue.
- 3,000+Capability units
Runnable capability units your agent composes from, counted apart from the catalogue.
- 29Originating projects
One continuous software lineage.
- 7Strategic volumes
Free to read. No email required.
The engineered catalogue and the capability units are counted and cited separately. They are never added together to make a bigger number.