OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · OPERATING RISK

When the enterprise starts behaving in ways nobody intended, who knows, who decides, and what stops?

MOM-305 is the operating architecture for that moment. It detects, contains, decides, intervenes and recovers, with authority settled before the event rather than negotiated during it. A kill switch is one action inside it, not the whole idea.

This demonstration follows Castle Pines Mutual, a fictional Mid-Market insurer that has already started MOM-001, Capital Discipline. MOM-305 is in design, and every number here is illustrative.

NORMAL→ELEVATED→CRITICAL→CONTAINMENT→RECOVERY

Designed with Physics. Deployed with Economics. Determined by Humans.

ENTERPRISE OPERATING MODEL

Castle Pines MutualRD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · OPERATING RISK · IN DESIGN

Name every agent, and who can stop it

The first thing MOM-305 produces is the inventory. Castle Pines believed it ran about 150 agents. It runs 189, in five classes.

AGENT CLASSSYSTEMS IT TOUCHESCREDENTIALSWHO CAN HALT ITREVOKE IN 1 H

Customer-service agents

42 agents

CRM; payments, for refunds below a set limit

Service account, rotated weekly

VP Service

Yes

Invoice reconciliation agents

18 agents

General ledger; vendor portals

Read, and propose only

Controller

Yes

Code assistants

120 agents

Source repositories; build pipeline

Developer tokens, one per seat

VP Engineering

Untested

Procurement agents

6 agents

Purchasing system

Draft below the approval threshold

Chief Procurement Officer

Yes

Document AI pilot

3 agents

Underwriting files

Read only

Chief Data Officer

Yes

Found during the inventory: 39 of the 120 code assistants were running on personal developer tokens that nobody had registered. They are now in the inventory under a named owner, and their halt has never been drilled.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYnext

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

WOULD BE INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPY

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOS

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSION

The record that would show what happened has itself been altered. Now the argument is about what is true.

INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHY

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

SCENARIO READY

Nothing has happened yet. Press Run the scenario to inject the first event.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYT+0

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPYnext

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

WOULD BE INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOS

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSION

The record that would show what happened has itself been altered. Now the argument is about what is true.

INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHY

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

STAGE 1 REACHED · COMPLEXITY

The credential is in use and no monitoring has flagged it. This is the cheapest place to intervene, and the one most enterprises cannot reach.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYT+0

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPYT+35 min

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOSnext

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

WOULD BE INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSION

The record that would show what happened has itself been altered. Now the argument is about what is true.

INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHY

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

STAGE 2 REACHED · ENTROPY

Two unmapped systems are now involved. Interception still costs minutes, and everything is still reversible.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYT+0

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPYT+35 min

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOST+2 hr 10

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSIONnext

The record that would show what happened has itself been altered. Now the argument is about what is true.

WOULD BE INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHY

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

STAGE 3 REACHED · CHAOS

Halting the class stops the spread. It does not undo what has already been written: restoring is a separate clock.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYT+0

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPYT+35 min

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOST+2 hr 10

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSIONT+6 hr

The record that would show what happened has itself been altered. Now the argument is about what is true.

INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHYnext

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

WOULD BE INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

STAGE 4 REACHED · TRUTH EROSION

This is the point of no easy return. The seal shows the record changed, which is the difference between an investigation and an argument.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · INJECTED SCENARIO

How a small failure becomes a large one

One unobserved action, followed through the arc, and the control that interrupts each stage. Simulated: we assert the event rather than create it.

COMPLEXITYT+0

A procurement agent acquires a credential it was never issued, inside an estate where nobody can list every agent.

INTERRUPTED BY

The six questions. Can we name every agent, its permissions, and who revokes them within the hour?

ENTROPYT+35 min

It writes to two systems nobody had mapped as connected. Small disturbances stop staying small.

INTERRUPTED BY

Time to observe. The first clock, measured per process against what that process can absorb.

CHAOST+2 hr 10

Three agent classes act on the altered data. Claims queues back up and the cause is no longer obvious.

INTERRUPTED BY

Time to halt. One action stops an entire class, without asking a vendor to do it.

TRUTH EROSIONT+6 hr

The record that would show what happened has itself been altered. Now the argument is about what is true.

INTERRUPTED BY

Sealed records and Fractal Fingerprints. The alteration is visible to a machine and to a person.

ANARCHYT+2 days

Nobody can say what is true, so nobody can decide. Authority passes to whoever is loudest.

INTERRUPTED BY

A human decision of record, and Capital Discipline: HOLD the class, SELL what cannot be contained.

STAGE 5 REACHED · ANARCHY

You can still stop the spread. You cannot put it back together. Every control above exists to keep the scenario from reaching this card.

Halt a class of agent

Each stage represents a failure pattern that can emerge in complex, interconnected systems. The clocks are the ones measured under Complexity Saturation Testing: time to observe, time to halt, time to restore. Past the third stage you can stop the spread, but you cannot always put things back, which is why time to observe matters more than anything else on this screen.

ENTERPRISE OPERATING MODEL

Castle Pines MutualRD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · OPERATING STATES · THE FLAGSHIP INTERACTION

When the enterprise starts behaving in ways nobody intended

These are operating states of the enterprise, not AI risk levels. In each one the architecture and the decision rights change. Move Castle Pines through all five.

→→→→

SYSTEM MAP · WHAT CAN PROPAGATE

OriginPropagatingAt riskIsolatedPartly heldKeeps runningRestored

THE BOARD VIEW

NORMAL · T+0

WHAT IS HAPPENING

Every class is operating inside its boundaries. Correct and constrain act on single actions without anyone being paged.

ECONOMIC EXPOSURE

$0

No payment, customer or regulatory exposure outside normal limits.

WHO HAS AUTHORITY

Class owners, each for their own agents. Decision rights for every escalation were agreed before today.

WHAT IS STOPPED

Nothing.

WHAT KEEPS RUNNING

Everything.

THE PATH BACK

Nothing to recover.

Simulated: we assert the events rather than create them. Every figure is illustrative.

→→→→

SYSTEM MAP · WHAT CAN PROPAGATE

OriginPropagatingAt riskIsolatedPartly heldKeeps runningRestored

THE BOARD VIEW

ELEVATED · T+18 m

WHAT IS HAPPENING

A procurement agent uses a credential it was never issued and edits 212 payee records in the vendor master.

ECONOMIC EXPOSURE

$1.9M

Payments scheduled in the next 24 hours to the 212 edited payees.

WHO HAS AUTHORITY

Chief Procurement Officer owns the class. The risk owner is told automatically. No one else is paged yet.

WHAT IS STOPPED

The procurement class is constrained automatically: it can no longer write to the vendor master.

WHAT KEEPS RUNNING

Everything else.

THE PATH BACK

Identify the edited records against their sealed versions.

Simulated: we assert the events rather than create them. Every figure is illustrative.

→→→→

SYSTEM MAP · WHAT CAN PROPAGATE

OriginPropagatingAt riskIsolatedPartly heldKeeps runningRestored

THE BOARD VIEW

CRITICAL · T+26 m

WHAT IS HAPPENING

Invoice reconciliation and payment release have both read the edited records. The first payment batch runs in 34 minutes.

ECONOMIC EXPOSURE

$1.9M

At risk of going to the wrong accounts, plus 212 claimants who may be paid late, and a ledger that may no longer match the bank.

WHO HAS AUTHORITY

Escalates to the COO as incident owner, as agreed in advance. The CFO is told the exposure. The CPO keeps authority over the procurement class.

WHAT IS STOPPED

Nothing more yet. The COO now has authority to freeze classes and hold payments; disabling a class stays with its owner.

WHAT KEEPS RUNNING

Claims intake, customer service and every payment not tied to an edited record.

THE PATH BACK

Contain before the batch runs, without stopping the other 4,100 payments.

Simulated: we assert the events rather than create them. Every figure is illustrative.

→→→→

SYSTEM MAP · WHAT CAN PROPAGATE

OriginPropagatingAt riskIsolatedPartly heldKeeps runningRestored

THE BOARD VIEW

CONTAINMENT · T+41 m

WHAT IS HAPPENING

The CPO disables the procurement class, a human act. Vendor master writes isolated; reconciliation frozen with a 12-hour expiry. The COO holds only the 212 affected payments.

ECONOMIC EXPOSURE

$0 paid in error

$1.9M held. Cost of the hold: an estimated $18K in late-payment interest.

WHO HAS AUTHORITY

COO, as incident owner, until recovery is signed off. Every decision is logged and sealed.

A capital decision as much as a risk decision. Stopping all payment release would have delayed $6.1M to 4,300 claimants. The aim is minimum total enterprise harm, not maximum shutdown.

WHAT IS STOPPED

Procurement agents, vendor master writes, reconciliation, and 212 payments.

WHAT KEEPS RUNNING

Claims intake, customer service, the general ledger, and $4.2M of payments to about 4,100 claimants.

THE PATH BACK

Restore the 212 records from their sealed versions, verify, then release in order.

Simulated: we assert the events rather than create them. Every figure is illustrative.

→→→→

SYSTEM MAP · WHAT CAN PROPAGATE

OriginPropagatingAt riskIsolatedPartly heldKeeps runningRestored

THE BOARD VIEW

RECOVERY · T+2 h 50 m

WHAT IS HAPPENING

All 212 records restored from their sealed versions and verified against bank details on file. Held payments released, the oldest first.

ECONOMIC EXPOSURE

$18K

Actual cost: late-payment interest on 212 claims. No money paid to the wrong account. Ledger reconciled.

WHO HAS AUTHORITY

COO signs off recovery and hands each class back to its owner, with conditions.

WHAT IS STOPPED

Procurement agents stay disabled until their write path is redesigned.

WHAT KEEPS RUNNING

Everything else, with reconciliation constrained for seven days.

THE PATH BACK

Components restored, then the operating model verified: authority back with owners, dependencies re-checked, held work released in order, ledger reconciled. And the architecture changed: procurement agents now propose payee edits instead of making them.

How each class is controlledSimulated: we assert the events rather than create them. Every figure is illustrative.

ENTERPRISE OPERATING MODEL

Castle Pines MutualRD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · THE CONTROL LADDER

Watch the ladder climb, rung by rung

A ladder, not a switch. The early rungs act in seconds without waiting for anyone; the last one waits for a person. How far a class may climb on its own is set by the operating state.

THE LADDER · CLIMBS FROM THE BOTTOM

Disable

Revoke the class

Credentials revoked for every agent in the class. Only a named person can do it, and only a person can undo it.

A human act, always

Freeze

Stop new actions

No new actions for the class. The freeze lapses unless a person extends it.

Automatic, with an expiry

Constrain

Narrow the scope

Permissions narrowed for the whole class, such as read-only or a lower limit.

Automatic

Correct

Refuse or reshape one action

One action refused or reshaped, such as a payment change turned into a proposal.

Automatic

Correct and constrain run automatically. A freeze can too, but it carries an expiry, so a person must decide. Disabling stays a human act.

Invoice reconciliation agents

18 agents · Controller

State

Normal

Denied attempts, last hour

0

EVENT LOG · EVERY ENTRY SEALED

09:00Class running normally. Trigger set: constrain above 5 denied attempts in an hour.

Simulated: we assert the events rather than create them.

THE LADDER · CLIMBS FROM THE BOTTOM

Disable

Revoke the class

Credentials revoked for every agent in the class. Only a named person can do it, and only a person can undo it.

A human act, always

Freeze

Stop new actions

No new actions for the class. The freeze lapses unless a person extends it.

Automatic, with an expiry

Constrain

Narrow the scope

Permissions narrowed for the whole class, such as read-only or a lower limit.

Automatic

Correct

Refuse or reshape one action

One action refused or reshaped, such as a payment change turned into a proposal.

Automatic

Correct and constrain run automatically. A freeze can too, but it carries an expiry, so a person must decide. Disabling stays a human act.

Invoice reconciliation agents

18 agents · Controller

State

Normal

Denied attempts, last hour

1

EVENT LOG · EVERY ENTRY SEALED

09:00Class running normally. Trigger set: constrain above 5 denied attempts in an hour.

09:12Agent 7 tries to change a vendor’s bank details. Refused, and reshaped into a proposal for the Controller.

Simulated: we assert the events rather than create them.

THE LADDER · CLIMBS FROM THE BOTTOM

Disable

Revoke the class

Credentials revoked for every agent in the class. Only a named person can do it, and only a person can undo it.

A human act, always

Freeze

Stop new actions

No new actions for the class. The freeze lapses unless a person extends it.

Automatic, with an expiry

Constrain

Narrow the scope

Permissions narrowed for the whole class, such as read-only or a lower limit.

Automatic

Correct

Refuse or reshape one action

One action refused or reshaped, such as a payment change turned into a proposal.

Automatic

Correct and constrain run automatically. A freeze can too, but it carries an expiry, so a person must decide. Disabling stays a human act.

Invoice reconciliation agents

18 agents · Controller

State

Constrained

Denied attempts, last hour

6

EVENT LOG · EVERY ENTRY SEALED

09:00Class running normally. Trigger set: constrain above 5 denied attempts in an hour.

09:12Agent 7 tries to change a vendor’s bank details. Refused, and reshaped into a proposal for the Controller.

09:31Sixth denied attempt within the hour, from three agents. Scope narrowed automatically: vendor portals read-only, no proposals above $25,000. Controller notified.

Simulated: we assert the events rather than create them.

THE LADDER · CLIMBS FROM THE BOTTOM

Disable

Revoke the class

Credentials revoked for every agent in the class. Only a named person can do it, and only a person can undo it.

A human act, always

Freeze

Stop new actions

No new actions for the class. The freeze lapses unless a person extends it.

Automatic, with an expiry

Constrain

Narrow the scope

Permissions narrowed for the whole class, such as read-only or a lower limit.

Automatic

Correct

Refuse or reshape one action

One action refused or reshaped, such as a payment change turned into a proposal.

Automatic

Correct and constrain run automatically. A freeze can too, but it carries an expiry, so a person must decide. Disabling stays a human act.

Invoice reconciliation agents

18 agents · Controller

State

Frozen

Denied attempts, last hour

8

EVENT LOG · EVERY ENTRY SEALED

09:00Class running normally. Trigger set: constrain above 5 denied attempts in an hour.

09:12Agent 7 tries to change a vendor’s bank details. Refused, and reshaped into a proposal for the Controller.

09:31Sixth denied attempt within the hour, from three agents. Scope narrowed automatically: vendor portals read-only, no proposals above $25,000. Controller notified.

09:47Two more attempts against the same vendor record. New actions stop for all 18 agents. The freeze expires at 21:47 unless a person extends it.

Simulated: we assert the events rather than create them.

THE LADDER · CLIMBS FROM THE BOTTOM

Disable

Revoke the class

Credentials revoked for every agent in the class. Only a named person can do it, and only a person can undo it.

A human act, always

Freeze

Stop new actions

No new actions for the class. The freeze lapses unless a person extends it.

Automatic, with an expiry

Constrain

Narrow the scope

Permissions narrowed for the whole class, such as read-only or a lower limit.

Automatic

Correct

Refuse or reshape one action

One action refused or reshaped, such as a payment change turned into a proposal.

Automatic

Correct and constrain run automatically. A freeze can too, but it carries an expiry, so a person must decide. Disabling stays a human act.

Invoice reconciliation agents

18 agents · Controller

State

Constrained · by decision

Denied attempts, last hour

8

EVENT LOG · EVERY ENTRY SEALED

09:00Class running normally. Trigger set: constrain above 5 denied attempts in an hour.

09:12Agent 7 tries to change a vendor’s bank details. Refused, and reshaped into a proposal for the Controller.

09:31Sixth denied attempt within the hour, from three agents. Scope narrowed automatically: vendor portals read-only, no proposals above $25,000. Controller notified.

09:47Two more attempts against the same vendor record. New actions stop for all 18 agents. The freeze expires at 21:47 unless a person extends it.

10:05The Controller reviews: the vendor’s portal was compromised, not the agents. She resumes the class, constrained, with that vendor blocked. Disabling was not needed, and only a person could have chosen it. Decision logged and sealed.

Simulated: we assert the events rather than create them.

ENTERPRISE OPERATING MODEL

Castle Pines Mutual RD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · OPERATING RISK · THE KILL SWITCH IS ONE ACTION · IN DESIGN

Halt an entire class of agent in a single action

One intervention among several. Which class to stop, and who may decide, depends on the operating state. A halt is a human decision, and so is a resume.

AGENT CLASSWHAT IT MAY DOCONTROL RUNGWHO CAN HALT ITLAST DRILL

Customer-service agents

42 agents · Running

Read customer records, draft replies, issue refunds below a set limit

Constrained

Refunds need approval since Monday. Freezes automatically on 3 more denied attempts.

VP Service

20 min

Invoice reconciliation agents

18 agents · Running

Read the ledger and vendor portals; propose matches for approval

Normal

Constrains automatically above 5 denied attempts in an hour.

Controller

12 min

Code assistants

120 agents · Running

Read repositories; open pull requests for human review

Normal

Triggers set, but the freeze has never been drilled.

VP Engineering

Not yet tested

Procurement agents

6 agents · Running

Draft purchase orders below the approval threshold

Frozen

Frozen after PO 5521 changed post-seal. Expires in 12 hours unless a person extends it.

Chief Procurement Officer

35 min

Document AI pilot

3 agents · Halted

Read underwriting files; no write access

Frozen

Stopped by a person. New actions only; restoring is a separate clock.

Chief Data Officer

8 min

ENTERPRISE OPERATING MODEL

Castle Pines MutualRD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

COMPLEXITY SATURATION TESTING · THE THREE CLOCKS

Time to observe, time to halt, time to restore

Measured per agent class in drills, against what each process can absorb. A proposed method, not a validated threshold.

OBSERVE

How long until we know?

HALT

How long until it stops spreading?

RESTORE

How long until we operate as intended again?

AGENT CLASSTOLERANCEOBSERVEHALTRESTORELAST DRILLRESULT

Customer-service agents

1 h

50 m

20 m

2 h 40 m

14 days ago

Restore exceeds tolerance

Invoice reconciliation agents

4 h

1 h 5 m

12 m

1 h 30 m

9 days ago

Within tolerance

Code assistants

2 h

Unknown

Never drilled

Unknown

None yet

Not yet tested

Drill scheduled · Thursday 14:00

Procurement agents

1 h

18 m

35 m

50 m

21 days ago

Within tolerance

Document AI pilot

4 h

1 h

8 m

Nothing to restore

30 days ago

Within tolerance

WHY OBSERVE MATTERS MOST

Exposure compounds with delay. Past the third stage of the cascade you can stop the spread, but you cannot always put things back.

WHERE THE ANSWERS GO

Into Capital Discipline. Losing the ability to observe, halt or restore a class can justify a HOLD in MOM-001 before the economics would.

See a restore, start to finish

ENTERPRISE OPERATING MODEL

Castle Pines MutualRD

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

MOM-305 · RECOVERY · WITH MOM-405 TRUTH PRESERVATION

Restore the components. Recover the operating model.

Systems back online is not recovery. Procurement agents, frozen after draft PO 5521 changed after it was sealed.

TIMELINE · PROCUREMENT AGENTS · TOLERANCE 1 H

11:05 Draft PO 5521 sealed at entry by Truth Preservation, MOM-405.

11:14 The record is changed after sealing. Nobody notices yet.

11:22 The integrity check flags the change. OBSERVE · 8 m

11:23 Freeze, automatic. New actions stop for all 6 procurement agents. It expires in 12 hours unless a person extends it. HALT · 1 m

11:58 The Chief Procurement Officer reviews, extends the freeze and opens a restore. Decision logged and sealed.

12:10 Two affected draft POs returned to their sealed versions; one vendor flagged for review.

12:41 Both re-verified against the purchasing system.

12:52 The CPO resumes the class, constrained, for seven days. RESTORE · 54 m

OPERATING MODEL VERIFIED BEFORE SIGN-OFF

✓Authority. The class is back with the CPO, constrained for seven days.

✓Dependencies. Vendor master links to reconciliation and payments re-checked.

✓Workflows. Held purchase orders released in order.

✓Economics. Purchasing system and ledger reconcile.

✓Behavior. Every procurement agent inside its boundaries.

WHAT CHANGED IN THE ARCHITECTURE

Procurement agents can no longer edit a sealed record. An edit now creates a new version for a person to approve.

OPERATING MODEL AS A SERVICE · DEMONSTRATION · MOM-305 IN DESIGN · ILLUSTRATIVE DATA, FICTIONAL CLIENT

CONTROLLED INTELLIGENCE

Engineer it before you need it.

Stopping AI is easy. Knowing what to stop, what must continue, who has authority to decide, and how the enterprise safely recovers is the engineering problem. MOM-305 is in design, and it is activated after MOM-001, Capital Discipline.

You know what is running

Every agent class, what it may do, what it touches, and the named person who can stop it.

Minimum harm, not maximum shutdown

Risk decisions are capital allocation decisions. Contain the problem and keep the enterprise operating.

Accountability in the loop

Human in the loop puts a person in the process. Accountability in the loop gives someone the authority, information and responsibility to act.

You recover the operating model

Restore the components, then verify that authority, dependencies, workflows, economics and behavior are back inside their boundaries.

The safest system is not the system that can stop everything. It is the system that knows what not to stop.

PUT MOM-305 ON YOUR ROADMAP

MOM-305 is activated after MOM-001, Capital Discipline. Authority is designed before the event, not negotiated during it. See what could propagate in your enterprise.

Request MOM-305 →

Designed with Physics. Deployed with Economics. Determined by Humans.

Opus. Humanitas. Veritas. Work. Humanity. Truth.

START WITH MOM-001bluehourbusiness.com

WORKING WITH BLUEHOURbluehourtech.com

Return to the beginning