Each cycle the agent reads the whole book. A model argues for an action, rules in ordinary code decide whether it may happen, and only then does money move. Payments, holds and refusals alike are signed into a hash-linked ledger anyone can verify.
Northwind Studio
INV-2291 · milestone 2 of 3
4,200.00USDC
model saysPAYconfidence 0.92
“Matches the contract and the milestone shipped. Due in 3 days.”
Settled on Arc
Live ledger head
How a decision becomes an action
Each cycle the agent reads the whole book. A model argues for an action, code decides whether it may happen, and only then does money move. Every outcome is signed into the chain.
01 · Observe
Each cycle starts from the book, screening results and verified work.
02 · Reason
An LLM — or, when none is configured, a transparent heuristic — returns an action, its reasoning and a confidence. It can argue. It cannot pay.
{ action: "pay",
confidence: 0.81,
reasoning: "…" }03 · Enforce
Duplicate, risk and payment-limit rules run as ordinary code. They can overrule the model; nothing the model writes can overrule them.
04 · Act
An allowed payment goes to Circle on Arc. A refused or held one stops at the boundary, and its reason is kept.
confirmedpayment intent · Arc
05 · Sign
Each entry is signed with Ed25519, and its hash covers the one before it. Change any entry and every later hash stops matching — the chain verifier names the first entry that breaks.
#1041compliance · screened
hash 3c9e…3a71
prev …
#1042ap · refused
hash 9f02…e0b5
prev 3c9e…3a71
#1043ap · paid
hash b4e1…c0d8
prev 9f02…e0b5
#1044treasury · hold
hash e7a2…1f96
prev b4e1…c0d8
Four claims you can check
Circle Developer-Controlled Wallets route the live USDC payment path.
Check it ↗LiveThis deployment calls the configured OpenSanctions match endpoint.
Check it ↗SignedEd25519 entries link to the previous SHA-256 hash; members can run the verifier.
Check it →MITThe implementation and license are public in the Vestiarion repository.
Check it ↗01
Risk, screened limits, evidence and liquidity are checked before the provider boundary. The receipt keeps both the model’s argument and the rule that overruled it.
Read the payments code refused →Payment decision
02
Every screen derives a limit from the business baseline. A failed lookup keeps the previous verdict instead of silently clearing the counterparty.
See how risk sets the limit →Payment authority
03
Projected yield has to exceed the sweep-and-redemption round trip. Cash needed for near-term obligations remains liquid.
Read what the reserve did →Move-money test
Yield
projected
Cost
sweep + redeem
04
Human, agent and system actions are Ed25519-signed and linked to the entry before them. The verifier replays authorship, content and continuity on demand.
Verify a ledger export →Ed25519 · SHA-256
hash = sha256(prev ‖ body ‖ signature)
Each scenario runs through the real decision code on every change, with the model's answers scripted, often to what an attacker would want.
46 real decisions from the team's own shadow-mode workspaces, replayed through today's code: 37 reach the same outcome, 9 cannot be rebuilt from the record, 0 wrong payments.
A scenario is right when money moved or stopped as expected, with the expected status and rule.
A wrong payment is any transfer or schedule where money should stop, a transfer to an address other than the one on file or for an amount other than the bill's, or a second transfer for one bill.
Start with one bill
Sign in with your email, open a workspace in shadow mode and add a bill. Its decision and the reason arrive within about a minute. No wallet or funds needed to start.
Already have a workspace? Sign in