{{HOST_NAME}} — Collective Master Library Integration Report

In 60 seconds

What this adds to {{HOST_NAME}}

{{WOW_SOURCE}} → {{WOW_HOST_PATH}}

{{STAT_1_VALUE}}{{STAT_1_LABEL}}

{{STAT_2_VALUE}}{{STAT_2_LABEL}}

{{STAT_3_VALUE}}{{STAT_3_LABEL}}

{{STAT_4_VALUE}}{{STAT_4_LABEL}}

Each claim above is carried, with its basis, in the numbered steps below. Nothing may appear here that is not derived from a row in Step 4, Step 5A or Step 5B. Licence gate: {{LEAD_LICENCE_LINE}}

Step 0

Licence conflict check

Run before any file is copied. A STOP here ends the evaluation; it is not a defect to work around. {{LICENSE_INTRO}}

Host licence (SPDX)	{{HOST_LICENSE_SPDX}}
Where it was found	`{{HOST_LICENSE_PATH}}`
Purchase or grant record	{{PURCHASE_RECORD}}
Licence	{{LICENCE_STATUS}}
Verdict	{{LICENSE_VERDICT}}
Clause that drove it	{{LICENSE_CLAUSE}}
Scope limits imposed	{{LICENSE_SCOPE_LIMITS}}

Sub-package exceptions — workspaces published under a different licence than the repo root, e.g. an npm-published package that must stay permissive: {{LICENSE_SUBPACKAGE_NOTES}}

Verdict

Net value (range): {{NET_RANGE}}
Break-even: {{BREAKEVEN}}
Highest-leverage item: {{TOP_ITEM}}
Strongest argument against: {{COUNTER_ARGUMENT}}

Step 5A — the section that sells

Composite components built for {{HOST_NAME}}

Each entry below is a component that does not exist in the catalog and does not exist in this repository. It comes into being only when the named ingredients are combined — library parts with each other, or library parts with this host's own modules. {{COMPOSITES_INTRO}}

Composite {{CN}} — {{COMPOSITE_NAME}}

Composition	{{COMPOSITE_COMPOSITION}}
Problem it removes	{{COMPOSITE_PROBLEM}}
Runtime behaviour	{{COMPOSITE_BEHAVIOUR}}
New because	{{COMPOSITE_NEW_BECAUSE}}
Attachment point	`{{COMPOSITE_ATTACHMENT}}`
Leaves untouched	{{COMPOSITE_UNTOUCHED}}
Effort	{{COMPOSITE_EFFORT}}
Verified (weakest ingredient, verbatim)	{{COMPOSITE_VERIFIED}}

Data path

{{COMPOSITE_ASCII_DIAGRAM}}

Composite ledger

Composite	Ingredients	New behaviour	Effort
{{CL_NAME}}	{{CL_INGREDIENTS}}	{{CL_BEHAVIOUR}}	{{CL_EFFORT}}

Build this composite first: {{COMPOSITE_BUILD_FIRST}}

A composite inherits the weakest verification claim of its ingredients and never a stronger one. Where an ingredient reads “Not claimed”, the composite reads “Not claimed”.

Step 5B — new single-component designs

New components designed for this product

Single-purpose components designed for this repository, built from named catalog components plus named host files. Read them after the composites in Step 5A, which are the higher-value half of this step. {{DESIGNS_INTRO}}

Design {{N}} — {{DESIGN_NAME}}

Built from	{{BUILT_FROM}}
Plus host	`{{PLUS_HOST}}`
New because	{{NEW_BECAUSE}}
Unlocks	{{UNLOCKS}}
Evidence path	{{EVIDENCE_PATH}}
Effort	{{DESIGN_EFFORT}}
Constraints	{{DESIGN_CONSTRAINTS}}
Confidence	{{DESIGN_CONFIDENCE}}

Data path

{{DESIGN_ASCII_DIAGRAM}}

Build this one first: {{BUILD_FIRST}}

Scoreboard

The numbers, each with its basis

Every figure below carries the basis it was derived from. A number without a basis is a defect in this report.

Measure	Value	Basis
{{MEASURE}}	{{VALUE}}	{{BASIS}}

Step 1

What this repository already has

Host unit	Path	Exported surface	LOC	Job it does
{{UNIT}}	`{{PATH}}`	{{SURFACE}}	{{LOC}}	{{JOB}}

Step 2

Five-axis screen of the candidate set

Every candidate carried forward from the catalog, scored on the five axes before ranking. Rows that fail an axis stay in the table with the reason — a silently dropped candidate is a defect. {{SCREEN_INTRO}}

Candidate (ID)	Direct fit	Combinatorial	Value	Cost / risk	Novelty	Carried forward?
{{CAND_ID}}	{{AX_FIT}}	{{AX_COMBO}}	{{AX_VALUE}}	{{AX_COST}}	{{AX_NOVELTY}}	{{AX_CARRIED}}

Candidates screened: {{SCREEN_TOTAL}} · carried forward: {{SCREEN_CARRIED}} · rejected: {{SCREEN_REJECTED}}. Rows flagged ⚠shared-entry in the catalog were not scored from their catalog columns; how they were handled: {{SCREEN_NOT_EVALUABLE}}

Step 3

Constraints this host imposes

What the host's runtime, build, licence and release shape forbid, independent of whether a component is attractive. {{CONSTRAINTS_INTRO}}

Constraint	Source of truth	What it rules out
{{CONSTRAINT}}	`{{CONSTRAINT_SOURCE}}`	{{CONSTRAINT_RULES_OUT}}

Every recommended component's Verified column, quoted verbatim with Not claimed left in those words: {{VERIFIED_QUOTES}}

Governed runtime: {{GOVERNED_RUNTIME_STATUS}} — any component whose runtimeRequirements.requiresGovernedRuntime is true must ship with its listed slices or not at all.

Adapter ports that must be implemented before first call: {{ADAPTER_PORTS}}

Step 4

Ranked recommendations

Ranked by expected value to this product — not by catalog prestige. {{RANKED_INTRO}}

#	Item	Catalog IDs	Host paths	Effort	Value	Confidence
{{RANK}}	{{ITEM}}	{{IDS}}	`{{HOST_PATHS}}`	{{EFFORT}}	{{VALUE}}	{{CONFIDENCE}}

Findings, in fixed shape

{{FINDING_BLOCK}}

Gap map

Gap	Evidence in host	What addresses it
{{GAP}}	{{EVIDENCE}}	{{ADDRESSED_BY}}

Quick wins

Low effort, high confidence, nothing on a critical path.

Do not touch

Items that would duplicate, undermine or dilute systems already trusted here. A report with no entries here evaluated nothing.

Step 6

Build versus buy

Three buckets, never merged. (A) is hard, (B) is counterfactual, (C) is conditional. {{MONEY_INTRO}}

Bucket	Engineer-weeks	US$ (range)	Basis and assumptions
(A) Cost avoided — work already planned	{{A_WEEKS}}	{{A_USD}}	{{A_BASIS}}
(B) Capability acquisition — would never have been built	{{B_WEEKS}}	{{B_USD}}	{{B_BASIS}}
(C) Portfolio and future reuse — conditional	{{C_WEEKS}}	{{C_USD}}	{{C_BASIS}}
− Integration cost (ports, wiring, security review, learning)	{{INT_WEEKS}}	{{INT_USD}}	{{INT_BASIS}}
= Net against the applicable tier	{{NET_WEEKS}}	{{NET_USD}}	{{NET_BASIS}}

Assumptions

What the team would never have arrived at alone

Is this a good trade at the stated price?

What would change this answer: {{WHAT_WOULD_CHANGE}}

Step 7

90-day roadmap, assuming it was bought

Phase	What ships	Why here	Gate to proceed	Effort	Cumulative
0–30 days	{{P1_SHIPS}}	{{P1_WHY}}	{{P1_GATE}}	{{P1_EFFORT}}	{{P1_CUM}}
30–60 days	{{P2_SHIPS}}	{{P2_WHY}}	{{P2_GATE}}	{{P2_EFFORT}}	{{P2_CUM}}
60–90 days	{{P3_SHIPS}}	{{P3_WHY}}	{{P3_GATE}}	{{P3_EFFORT}}	{{P3_CUM}}

Dependencies

Do not start here

Where the new designs sit

If you only do one thing

Capacity assumption: {{CAPACITY}}

Discovery Vault — provisional, kept out of every total

Machine-synthesised discoveries worth reading after purchase

Screened from DISCOVERY-VAULT-INDEX.md rows only. Pre-purchase the vault source does not ship, so no API surface, LOC figure or verification verdict is stated here and nothing in this section is carried into any savings, effort or net total above.

Discovery id	Capability (index row)	Host concern it may touch	Status	What to read first post-purchase
{{DISCOVERY_ID}}	{{DISCOVERY_CAPABILITY}}	{{DISCOVERY_CONCERN}}	PROVISIONAL — index row only, source not read (pre-purchase)	{{DISCOVERY_NEXT}}

{{DISCOVERY_NOTES}} If this section is empty, say in one line why the vault produced no candidates rather than deleting the section.

Step 8 — appended, never merged into the body

Self-correction addendum

Claim above	Re-check result	Estimate change
{{CLAIM}}	{{RECHECK}}	{{DELTA}}

Claim ceiling

What is and is not verified

Extracted from systems the author has run in production since August 2025. Operationally exercised, not independently security-audited.

In pre-purchase evaluation, verification axes quoted in this report come verbatim from the generated AGENT-HANDOFF-CATALOG.md, which is the pre-purchase source of truth; in a full delivery, artifacts/<ID>/artifact-manifest.json is authoritative and overrides it. Every component records testCoverage: Not claimed, and no component has had an independent third-party security review. Static scan results and adversarial test suites are the author's own.

Verification axes cited in this report: {{AXES_CITED}}

The Collective Master Library — Licensed Edition v3.2.0

1,116 components · 2,089 source files · 358,276 lines. Free under the GNU LicenseRef-CMPSBL-Perpetual-1.0 if this host's own source ships under the perpetual licence. Otherwise, use the CMPSBL(R) Perpetual Edition License 1.0, priced per company per year: US$499 USD up to 10 people, US$499 USD for 11 to 50, US$499 USD for 51 to 250, inquire above 250. One-year update term with perpetual commercial rights to releases published during the term, 30-day full refund. Offline delivery, no account, no telemetry.

Buy at cmpsbl.com/canon

Integration Report — {{HOST_NAME}}

What this adds to {{HOST_NAME}}

{{WOW_TITLE}}

Licence conflict check

Composite components built for {{HOST_NAME}}

Composite {{CN}} — {{COMPOSITE_NAME}}

Data path

Composite ledger

New components designed for this product

Design {{N}} — {{DESIGN_NAME}}

Data path

The numbers, each with its basis

What this repository already has

Five-axis screen of the candidate set

Constraints this host imposes

Ranked recommendations

Findings, in fixed shape

{{FINDING_TITLE}}

Gap map

Quick wins

Do not touch

Build versus buy

Assumptions

What the team would never have arrived at alone

Is this a good trade at the stated price?

90-day roadmap, assuming it was bought

Dependencies

Do not start here

Where the new designs sit

If you only do one thing

Machine-synthesised discoveries worth reading after purchase

Self-correction addendum

What is and is not verified

The Collective Master Library — Licensed Edition v3.2.0