Platform · Automate/ORC
Many agents, one ledger, one order of events.
When several agents work the same records, something decides who goes first, what locks, and who wins.
Deterministic ordering·Record-level locking·Conflict resolution
Invoice Held
ap-clerk
SAMPLE · ONE WRITER AT A TIME
One run/01
What happens when a document arrives.
01
Claim
One agent holds it
02
Plan
Checked against limits
03
Commit
All or nothing
04
Release
Lock lifts, trail written
Held until release
Nothing writes until the whole plan has been checked.
Six mechanisms/02
What keeps a dozen agents from fighting.
1
2
3
Ordering
By rule, not by race
Lease running
Locking
Visible holds, lease expiry
AB
Conflict
Precedence or a person
Deferred, with a reason
Backpressure
Work waits, visibly
Rolled back
Atomic commit
No half-posted state
Replay and handover
Any run, or take it over
Conflict/03
Two agents disagree. Then what?
ap-clerk
Release the payment
close-agent
Hold for the period close
Higher precedence applies
Never decided by timing.
Both positions kept Repeats raise a rules problem
ILLUSTRATIVE AGENTS · SAMPLE DECISION
At a glance/04
Stated, not implied.
Ordering
Declared precedence
Isolation
Record claim, lease expiry
Atomicity
Commit as one unit
Retry
Idempotent, safe to re-run
Conflict
Rule or person, never timing
Queues
Bounded, fair, rate-limited
Observability
Full replay
Interruption
Break lock, hand over
What it does not solve/05
Safe and legible. Not automatically wise.
Not worth it for most work
One agent is usually enough.
Not an accuracy fix
Order does not make an agent right.
Limits do not add up
Three small ceilings stay small.
Not a message bus
Moving data is integration.
Next step