Every system that learns runs on the same five parts. Whether it's a commercial motion, an AI agent, or a cross-departmental process inside an industrial company, the structure underneath is identical. Most businesses install one or two of those parts and call it a business. That's why the system operates but never gets sharper with use.
This essay names that structure. It's the reference behind Product.Zone's commercial-system work, and the frame shared by our partnership with Hurozo on agent installations and our deployments in the chemical industry. The vocabulary below is ours. The pattern it describes is not unique to us, but naming it is what makes it fixable.
01 · The five partsFive organs. One body. Drop one, and it stops compounding.
Most founders install surfaces first: a homepage, a deck, a sales motion. Some add skills: a playbook, a discovery script, maybe a hire who runs it. That is two organs out of five. They call it a business, then wonder why it can't run without them. Here are all five, and the thing most teams have installed in each one's place.
Canon
Locked decisions. The source of truth every skill reads from, versioned and dated, with the reasoning preserved.
Documents, slides, Slack threads. Information, not canon.
Skills
Processes that read canon and act. Agentic (an AI run) or human (a playbook a salesperson follows). The verbs of the system.
Skills tied to specific people: Sarah's discovery process, Marc's pricing instinct.
State
Live operating context. Where each deal is, what this buyer was told last week, what's in flight, queryable in real time by skills.
CRM fields. Necessary, not sufficient. Few have state as a shape skills can act on situationally.
Surfaces
Where canon, skills, and state meet the world. Homepage, deal room, follow-up email, onboarding flow, generated artifact.
Surfaces. This is the one organ they did install. But surfaces without canon underneath get rebuilt every six months, because they never learn.
Sensors
Feedback observed from surfaces, routed back to canon. The mechanism that closes the loop and lets the system learn.
Analytics dashboards, occasional win/loss reviews. Sensors are different: they observe what happens at a surface and update canon.
02 · The build-upFrom the atom up.
These five weren't designed top-down. They were derived by asking what the indivisible unit of business truth is, then building up from there. A claim is the atom. It can't be broken further without losing meaning. Everything else is composed from claims.
| Level | Name | What it is | Example |
|---|---|---|---|
| Atom | Claim | A single indivisible assertion the business holds to be true. | "Our buyer is a technical founder-CEO." |
| Molecule | Decision | A claim that has been locked, versioned, given authority. | A decision-ledger entry. |
| Tissue | Canon | A coherent body of related decisions. | The ledger itself. |
| Organ | A part | A functional unit operating on canon. | Canon, Skills, State, Surfaces, Sensors. |
| Organism | The whole | The five parts running together as one closed system. | The whole architecture in motion. |
| Environment | Governance | The authority under which the system is permitted to change. | Who can lock canon. Who admits new skills. |
Governance is not a sixth part. It's the environment the system operates in: the conditions under which the loop is allowed to change. The five parts describe how the system runs. Governance fires when something needs to change. Different concern, different scope.
03 · Same anatomy, three layersDifferent surfaces, same gaps.
The structure is installation-agnostic. The same five parts run a B2B commercial motion, an AI agent system, and a cross-departmental process inside an industrial company. The presenting symptoms differ. The missing organs are the same.
| Part | Commercial | AI agent | Industrial |
|---|---|---|---|
| Canon | Decision ledger, voice reference, offer architecture | System prompts, knowledge base, retrieval corpus | Extracted contract terms, locked pricing logic |
| Skills | The X-RAY, a sprint, deal-room build, follow-up drafting | Tools, sub-agents, deterministic procedures | Matchmaking agents, expert-augmenting workflows |
| State | Deal stage, buyer knowledge, team workload | Conversation context, run memory, agent variables | Live deal state, customer state, inventory state |
| Surfaces | Homepage, deal room, deck, generated reports | Chat UI, API endpoint, generated artifact | Exception dashboard, recommendation, auto-invoicer |
| Sensors | Won/lost signal, buyer behavior, content engagement | Eval traces, run analytics, audit logs | Customer signals, revenue-leak detection |
A chemical distributor's CIO building an AI agenda and a B2B SaaS founder building a sales motion have the same problem at the structural level. The symptoms look nothing alike. The gaps are identical.
04 · The mechanismWhat actually makes it learn.
The five parts describe a static body. What animates it is the mechanism through which canon gets formed and updated. Conversations happen: sales calls, partner syncs, prospect reviews, internal strategy sessions. Claims get extracted from them. Decision-worthy questions get formulated from the claims. Decisions get locked. Canon updates. Skills carry the new canon out to the surfaces. The next conversation runs against sharper canon.
This loop is largely AI-driven. Skills extract, skills formulate, skills propagate. The operator makes the calls. The mechanism does the connective work between them, so that nothing learned in a conversation gets lost before it reaches a surface.
05 · The frame, restatedThree things, installed together.
The anatomy is what the system is: five parts working together. The mechanism is what makes it learn: the AI-driven engine that turns conversations into locked canon. And the customer's journey is what flows through it over time, across the arc of winning a deal and the arc of keeping it.
One distinction worth holding onto. The five parts are the architecture. The commercial motion your buyers and customers actually move through, the thing that runs on top of this anatomy, is a different layer. The anatomy is what makes that motion run, and run sharper with every cycle. Confuse the two and you end up trying to fix the motion by bolting on another surface, when the part that was never installed sits a layer below it.
All three, installed together and governed properly. Or you have artifacts dressed up as a business: a homepage that gets rebuilt every six months, a pitch that lives in one person's head, a motion that stops the moment the founder steps out of the room.
The depth of the install is the depth of the inventory inside each part: the named decisions, the language, the motions, the questions a buyer asks. Most teams have a rich inventory in one or two parts and nothing in the rest. That's the whole diagnosis. Not "your sales is broken." Which organs you never installed.