Simulated demo data. Not live production telemetry. Static scenario playback using sanitized artifacts from SwarmOS v1.0.0-rc1. Request pilot access for the real gateway.

Simulated demo

SwarmOS Control v1.0.0-rc1

Simulated dashboard — 2 agents, 3 vaults, 5 receipts

Emergency:NORMAL

Health:96%

Verifier:Running

Receipts verified:42

Registered Agents

agent-alpha-7f3a

2 session keys

active

agent-beta-2c8b

1 session keys

active

Security Health

identity

100%

treasury

95%

policy

100%

verification

90%

security

95%

Capital Cells (Vaults)

Cell ID	Purpose	Balance	Reserved	Policy
`cell-001-ops`	Alpha ops vault	847.50 ETH	0.00	`pol-conservative`
`cell-002-yield`	Yield strategy vault	2340.00 ETH	150.00	`pol-standard`
`cell-003-payments`	Payment processing vault	500.00 ETH	0.00	`pol-conservative`

Recent Receipts

Receipt	Cell	Amount	Status	Verified
`rcpt-a1b2c3`	`cell-001-ops`	50.00 ETH	confirmed	✓
`rcpt-d4e5f6`	`cell-002-yield`	150.00 ETH	confirmed	✓
`rcpt-g7h8i9`	`cell-001-ops`	25.00 ETH	confirmed	✓
`rcpt-j0k1l2`	`cell-003-payments`	100.00 ETH	confirmed	✓
`rcpt-m3n4o5`	`cell-002-yield`	200.00 ETH	confirmed	✓

Pipeline Scenarios: Success & Failure

A system that only shows green checks is hiding something. Select a scenario below to see exactly how SwarmOS handles stale keys, policy violations, verifier outages, and emergency transitions.

Execution Scenarios

Simulated demo

SwarmOS is designed to reject, degrade, and halt. These scenarios show both success and failure paths through the 11-step pipeline. Select a scenario to see the causal event timeline.

Healthy Baseline

Normal operation — agent executes transfer successfully

Intent submitted0ms

transfer.external 50 ETH to 0xrecipient

Policy checked2ms

per_action_limit=500, requested=50 → ALLOW

Session key validated3ms

key_id=sk_a1b2, not expired, rotation_counter=0, capability=treasury.transfer

Simulation passed8ms

Estimated gas: 21000, projected balance: 950

Risk scored9ms

Risk level: LOW (score=0.12)

Approval9ms

Not required for LOW risk

Transaction signed12ms

Policy hash re-verified, TX signed with session key

Chain submitted35ms

Nonce reserved, submitted to local adapter

Receipt generated37ms

rcpt_7f3a...5c → outcome=success, fee=0

Verification queued47ms

Background verifier: 5/5 checks passed → VALID

Chain appended48ms

Receipt hash-chained, trust score unchanged

Emergency State Machine

Verified artifact

4-state total order. Engagement moves only toward more restrictive. Release goes one level at a time with 10-minute cooldown. GSI can engage up to SAFE_READONLY; only operators can engage HARD_STOP.

NORMAL

All actions allowed

Engage: operator or GSIRelease: 10-min cooldown ↑

DEGRADED

Only LOW risk without approval

Engage: operator or GSIRelease: 10-min cooldown ↑

SAFE_READONLY

Writes blocked; reads work

Engage: operator onlyRelease: 10-min cooldown ↑

HARD_STOP

All operations blocked

View full proof pack →