Context Design Co
ASSET STATE Class · intangible software Licence · MIT, day one Hosting · yours Cost · fixed-fee invoice Provenance · hash-chained
§ Operational IP — the asset thesis

Own what you paid for.

Consulting ends in a goodbye and a slide deck. A Substrate engagement ends in a transferable software asset — codified operating knowledge, MIT-licensed, on your infrastructure, in a form your auditor and a buyer's diligence team can actually receive.

Deliverable: the Handover Manifest · nine artefacts · live, versioned, queryable after close

Every other AI engagement you'll be offered is an expense. This one ends on the balance sheet.

That claim has to survive two professional skeptics: your auditor and a buyer's due-diligence team. This page is written for them — the deliverables register, the four questions an auditor asks, a tamper-evident build log you can try to break, and the valuation math, conservatively framed.

§ 01 — The deliverable

The Handover Manifest — nine artefacts, on the register.

The literal deliverables list at Substrate Handover. Not documents in a folder — live artefacts, maintained, versioned and queryable after close.

MF·01repo

The repo

The substrate codebase — MIT-licensed, hosted in your GitHub from minute one.

MF·02ontology

The ontology

The entity-and-edge schema that mirrors how your business actually works.

MF·03runbooks

Runbooks

Operational procedures — written down, executable, owned.

MF·04decisions

Decision history

The why behind every architectural and operational call, captured.

MF·05integrations

Integration map

Every connector, data path and downstream dependency, documented.

MF·06audit log

The audit log

Every command, action and change — timestamped, append-only, hash-chained.

MF·07retrieval

Retrieval graph

The queryable knowledge layer your AI plugs into, via MCP.

MF·08recovery

DR procedure

Disaster recovery runbook — written, then tested.

MF·09training

Training docs

Onboarding for the next engineer who ever touches the substrate.

For the first time, your CEO and CFO can see the operating business as a queryable system — every connector, every workflow, every decision on record, in plain English, on your own infrastructure.

§ 02 — The auditor's test

The four questions your auditor will ask. The evidence you'll hold.

Recognising software as an intangible asset runs through a known set of questions — the recognition tests auditors apply under IAS 38. The decision is your auditor's, not ours. Our job is that you arrive with the file. Here is the file.

01identifiable

"Can you point at the thing?"

An asset must be separable — something you can name, list and hand over. Not "AI transformation"; nine artefacts on a register, in your repository.

Evidence in hand
Handover Manifest MF·01–09Repo in your GitHubIntegration map
02controlled

"Do you control it?"

Control means the benefits flow to you and you can restrict others' access. MIT licence from day one, self-hosted on your infrastructure, model-agnostic by design — no vendor can switch it off.

Evidence in hand
MIT licence, day oneSelf-hostedMCP — bring any model
03future benefit

"Will it keep earning or saving?"

Probable future economic benefit — demonstrated, not promised: the substrate pattern operating two production businesses, the capacity math you can run on your own numbers, and the three valuation mechanisms below.

Evidence in hand
Two production showcasesRun your own math →/pricingMechanisms § 04
04measurable cost

"Can you evidence what it cost?"

Reliable measurement is the easiest gate of all: each rung is a fixed-fee invoice, and the build itself carries a hash-chained log — provenance you can verify, and your auditor can sample.

Evidence in hand
Fixed-fee invoice per rungHash-chained build log ↓Independent audit § 06

This is information about a recognition process, not accounting advice — your auditor applies the tests to your facts. We make the file easy to open.

§ 03 — Provenance, demonstrated

The audit log artefact — live. Try to break it.

MF·06 isn't a promise of good behaviour; it's cryptography. Below is the same mechanism your substrate's build log uses, running in your browser right now: every entry is sealed with SHA-256 against everything before it. Append your own entry. Then tamper with history and watch the seals break.

build log · append-only · sha-256 chainedcomputed in your browser

    This page never sends your entries anywhere — the chain is computed locally, like the real one on your hardware.

    § 04 — The mechanisms

    Three ways the asset moves valuation.

    Standard diligence adjustments PE and M&A practitioners already apply. Each independently recognised; together they compound.

    Mechanism 1

    Key-person discount, reduced

    SME valuations carry a haircut when operating knowledge lives in the founder's head. The substrate externalises it — code, runbooks, retrieval graph, decision history — and a buyer's adviser observes the externalisation directly.

    Mechanism 2

    Operability premium, documented

    Buyers pay higher multiples for businesses they can step into. The Manifest is the strongest available evidence of operability — not a promise the business runs without you; the record of it.

    Mechanism 3

    Capitalisable software asset

    Owned software with documentation, self-hosted. A buyer's auditor can recognise it as an intangible asset under capitalised software development — delivered in a form their framework can receive.

    § 05 — The math, conservatively framed

    One worked example. Your advisers run the rest.

    We name the lever. Your auditor and your prospective buyer quantify. For the full math, the Federation case and the trend line, read the essay → — or run your own numbers on the calculator →

    § 06 — Independent verification

    Audits of scaffolding are theatre. Ours is in production.

    During Stewardship, an independent technical due-diligence firm audits the substrate in production — the third-party verification a buyer's auditor requires. Included by default in every Practice and Federation engagement.

    § 07 — Common questions

    Asked by every careful buyer.

    What is Operational IP?

    Operational IP is the codified knowledge of an operating business — its ontology, runbooks, decision history, integration map, audit log, retrieval graph, DR procedure, and training documentation — delivered as a transferable software asset at the close of a Substrate engagement. MIT-licensed and owned by the client on day one.

    What is in the Handover Manifest?

    The Handover Manifest is the literal nine-item deliverables list at Substrate Handover: repo, ontology, runbooks, decision history, integration map, audit log, retrieval graph, DR procedure, and training docs. Each artefact is delivered under MIT licence, hosted in the client's GitHub from minute one.

    How does a Substrate affect business valuation?

    Three mechanisms recognised in M&A diligence. First, removing the key-person risk discount that SME valuations carry when operations depend on undocumented founder or staff knowledge. Second, the documented operational IP premium buyers pay for businesses they can step into without the seller. Third, the capitalisable software asset that the buyer's auditor can recognise as an intangible asset on the balance sheet.

    How is the Substrate capitalised on the balance sheet?

    The Substrate is owned software with documentation, self-hosted on the client's infrastructure. The client's auditor can assess it for recognition as an intangible asset under capitalised software development — the decision is the auditor's. An independent technical due-diligence audit during Stewardship provides supporting third-party verification.

    § 08 — Productized substrate

    BlitzBox: when the substrate ships as a SKU.

    Atteste and Practacular are bespoke substrates we built for specific operating models. BlitzBox is the third instance — the same thesis, productized: a single-tenant, local-first AI substrate on a custom-finished Mac Mini, running at your premises. Same operational-IP pattern; different commercial shape.

    Sold directly — no bespoke discovery engagement, no per-customer sprint. The thesis says the substrate is the asset; BlitzBox is that asset, productized.

    See BlitzBox Look inside the box →
    § 09 — Your register, started

    What would your balance sheet gain?

    The diagnostic maps the substrate to your business — and the quote it produces is the first document in your asset's cost evidence. Plain questions, fixed price, twenty minutes.

    20 minutes · plain questions · ends in a fixed quote