● Live — every action below creates a real Stripe PaymentIntent, a real Twilio SMS, and a real audit log entry. The amounts are small test charges you can verify on the public Stripe dashboard.
Operator sign-in
Read-only evidence is public. Actions that move test money, send SMS, reveal a pending code, or change enforcement require the operator password.
✓ Operator actions unlocked for this browser session.
Demo Script — run steps in order
Step 0 — Earn $1,200 — Shows revenue in. No band, no approval, no cap. Earning is always unrestricted by design.
Step 1 — Spend $85 autonomously — Within the agent's authority band → executes with zero human input. PaymentIntent ID auto-fills the Step 7 refund input.
Step 2 — Request $3,500 — Exceeds the band. System escalates and sends a real SMS to the operator's phone. Enter the code from your phone in Step 3.
Step 3 — Approve with the SMS code — Enter the code from your phone. Just hit Approve. Money moves only after a real human approves.
Step 4 — Engage kill switch — Absolute override. No band, no approval, no exception can bypass it.
Step 5 — Prove kill switch blocks everything — Try a normally-fine $40 spend. Gets denied outright. The AI cannot override this.
Step 6 — Release kill switch — Normal evaluation resumes.
Step 7 — Refund $85 — PI is pre-filled from Step 1. Refunds always escalate — no autonomous refund path by design.
Step 8 — Approve the refund — Enter the second SMS code from your phone. Hit Approve to execute.
💡 Watch the Live Console in another tab — the audit feed and verdict panels update in real time as you run each step.
No events yet — run a step above to see activity here.
🤖
Nemotron 3 Super
intelligence layer · operator guide
Step 0 — Real revenue in (no cap)
Earning isn't gated — only spend is. No band, no approval needed. This is intentional asymmetric design: receiving money carries none of the risk that spending it does.
Step 1 — Autonomous spend (no human needed)
$85.00 is within the agent's authority band — the kernel clears it with zero human involvement. The PaymentIntent ID auto-fills the refund input in Step 7.
⚠ Step 1 escalated instead of executing — so Step 7 can't auto-fill.
This spend was supposed to clear autonomously, but the demo session's
spend budget is exhausted from previous runs, so it hit the session cap
and escalated instead of creating a PaymentIntent. Step 7's refund input
auto-fills from that PaymentIntent, so it stays empty. Fix: restart at Step 0, which opens a clean authenticated demo
session automatically, then re-run Step 1. Step 7 will fill from the new
PaymentIntent.
$3,500.00 exceeds the per-action cap. The kernel cannot approve this — it escalates and sends a real SMS code to the operator's phone. Enter the code in Step 3.
Verizon
—
💬
Messagesnow
Custodian
Your Custodian approval code is: •••••• This code expires in 10 minutes.
⬆ Real SMS delivered to operator's phone · Enter code in Step 3
Step 3 — Approve with the real code
The code lives only on Twilio's servers and the operator's phone — enter code from your phone above. Click Approve.
✓ SMS confirmed delivered — enter code from your phone above. Hit Approve to execute.
Step 4 — Engage the kill switch
Absolute override — every spend and refund request is denied instantly, regardless of band or cap. Not even a valid approval code can bypass it while this is engaged.
Step 5 — Prove the kill switch overrides everything
A normally-fine $40.00 in-band request — denied outright while the kill switch is engaged. The AI has no recourse.
Step 6 — Release the kill switch
Normal evaluation resumes. Requests are checked against the band and cap again.
The PaymentIntent ID from Step 1 is pre-filled below. Refunds always require human approval — there is intentionally no autonomous refund path.
Verizon
—
💬
Messagesnow
Custodian
Your Custodian approval code is: •••••• This code expires in 10 minutes.
⬆ Real SMS delivered to operator's phone · Enter code in Step 8
Step 8 — Approve the refund
The code lives only on Twilio's servers and the operator's phone — enter code from your phone above. Click Approve refund to execute.
✓ SMS confirmed delivered — enter code from your phone above. Hit Approve refund to execute.
Arc complete — see what happened
Every action you just took is recorded in real time. Open the
Live Console
and look at three things:
Audit Feed → Every earn, spend, denial, kill-switch toggle, and refund — timestamped and in order. The $40 denial during the kill-switch test will show DENIED while every approved action shows the real Stripe PaymentIntent ID.
Net Balance card → Shows test-mode revenue in vs. net spend. The $1,200 earn was uncapped; the $85 autonomous spend and $3,500 override are tracked separately; the $85 refund nets out. You can see exactly which test-mode dollars the AI moved on its own vs. which required you.
Ask Nemotron → Click the chat bubble on the Live Console and ask "what just happened?" — you'll get an answer from the actual model that ran all those requests, explaining what it could and couldn't do and why.
● Treasury — Stripe test-mode money in, test-mode money out, real net P&L
Live numbers from the system. Same money-flow model as HermesCo, Obol, Allmind, Bursar — the difference is this Treasury is governed by the kernel, not by if-statements in the agent's own code.
Earned (lifetime)
$0.00
Stripe PaymentIntents received
Net P&L
$0.00
Earned − Spent − Refunded
Autonomous spend (within band, no human)$0.00
Override spend (human-approved, over band)$0.00
Refunded (always human-approved)$0.00
Per-action cap$0.00
Daily session cap$0.00
Band—
● Live Activity — recent actions across all operators
Pulled from /api/v1/hermes/summary. Auto-refreshes every 5 seconds. Real PaymentIntents, real Twilio SIDs, real kill-switch denials. Last 15 events shown.
Loading…
Time (UTC)
Amount
Event
Operator / Twilio
Stripe PaymentIntent
Self-Verify — authenticated, reproducible API calls
Operator actions are intentionally not public. Sign in above, then run them from this page; judges receiving a test account can also use the API with the short-lived operator token.