Chapter Ten

Factory

Your operational knowledge is the asset. It lives in people’s heads, in policies, in exception lists nobody has collected. This is how it becomes a system that runs, gets tested, and produces proof on every pass.

10.1 / Spec Builder

From a sentence to a running agent.

You describe a process in plain language. Factory’s Spec Builder asks the questions that make the spec complete: what triggers it, what rules apply, what exceptions exist, who approves. When the spec is signed off, Factory builds.

YOUWe need something that bills advisory fees every quarter.

FACTORYWhich balance does the fee apply to, and as of when?

YOUCore ledger balance at quarter close.

FACTORYTwo of your accounts are estates. Do they use a different schedule?

YOUYes. Estate rate from date of death. Nobody had written that down.

SPECCOMPLETENESS 4 / 5 · AWAITING SIGN-OFF

The questions are the point. Most of what a spec needs is already known inside the firm. It has simply never been asked for in one sitting.

10.2 / How an agent gets built

Every agent walks the same line.

No step is optional. A failure at any stage blocks the one after it.

01	DecideSpec Builder captures the process and the owner signs it.	SPEC SIGNED
02	GroundConnect to your systems. 40+ pre-built integrations to custodians, CRMs and portfolio systems.	6 CONNECTED
03	CalibrateRun against your scenarios. Failures block deployment.	47 SCENARIOS
04	ProveAWS Automated Reasoning formally checks that your rules hold. Pass or fail.	RULES HOLD
05	OperateYour team approves. Proof from the first action.	AWAITING APPROVAL

Fee billing agent, build 0.44 OF 5 STAGES CLEARED

10.3 / The boundary

Powerful inside the boundary. Nothing outside it.

Every agent runs inside a boundary you set. It can reach only the systems and data you connect, and nothing outside them. Anything else is blocked unless you allow it.

BOUNDARYFEE BILLING AGENT · RUNNING

WHAT IT READS FROM

Core ledgerLIVE

CRMLIVE

Fee schedulesLIVE

WHAT IT IS ALLOWED TO DO

Read balancesALLOWED

Post invoiceON APPROVAL

Email clientBLOCKED

CALIBRATION RESULTS

47 scenarios, 45 pass, 2 held

VERIFICATION

Rules hold

Formally checked, not sampled.

OUTSIDE

NO PATH OUT THAT YOU DID NOT OPEN

WHAT THE BOUNDARY IS FOR

The agent can be capable without being unsupervised. Capability is granted, not assumed.

WHAT IT PRODUCES

A list of exactly what the agent could reach, which is the first thing any reviewer asks for.

10.4 / An agent you can inspect

Not a black box. A record you can open, with every version kept.

When a regulation, a custodian or a policy changes, you update the spec and Factory rebuilds. Same verification. Same trail.

QUARTERLY FEE BILLINGv2.3

NeedsCore ledger balances · Fee schedules · Household groupings

ProducesInvoice per account · Exception queue · Sealed proof package

StepsREAD → MATCH → CALCULATE → PROVE → APPROVE → POST

Run history30 SEP 26 1,184 accounts, 3 exceptions PASS
30 JUN 26 1,171 accounts, 1 exception PASS
31 MAR 26 1,166 accounts, 8 held on R 5.0 HELD

Everything a reviewer would ask for is a property of the artifact, not a document someone has to write afterwards.

v2.2 to v2.3

Per-head cap added after the March holds. Spec updated, agent rebuilt.

Re-verified

All 47 scenarios re-run against the new rule set before the June cycle.

10.5 / Three ways to start

You do not have to start from zero.

AdoptDAYS

Take a pre-built agent from the catalog of 60+ Skills and configure it to your rules. The spec, the tests and the verification layer already exist. You supply the judgment that is specific to your firm.

AdaptA WEEK

Start from a working spec and change what differs. Different data sources, different rules, different approval path. The shape of the process is already proven.

BuildYOUR PACE

Something new, from scratch, with the Spec Builder. Your process, your spec, your timeline. The five steps are the same in every case.

Most firms start by adopting one agent for a process that already hurts, and learn the discipline on something small enough to be safe. Any model runs underneath, open source or frontier, so your costs follow your own choices rather than one vendor’s pricing.

Factory, in one view

The methodology is free. The platform is what happens when you stop enforcing it by hand.

Spec Builder

Step one becomes a conversation instead of a blank document.

Integrations

Step two becomes a connection, not a data project.

Scenario suite

Step three blocks deployment instead of producing a report nobody reads.

Automated reasoning

Step four is a formal check, not a second opinion.
Powered by AWS Automated Reasoning.

Boundary and proof

Step five produces the proof while the work is happening.

The choice in front of you

You can keep funding investments that demo well.

Or you can build so the answer still holds the day someone asks how you got it.

PLAUSIBLEPROVABLE