Problem 5: A system that doesn't know itself says yes to things it can't do
Agents increasingly have to work with systems they've never met. A system that doesn't know itself can't tell another agent what it can do, what state it's in, or what it must not do. It says yes to things it can't do right now, and it finds out by failing.
Solution. A s0ma system can hand its self-model to another agent: capabilities, dependencies, current state, limits, and prohibitions, over a standard protocol, with no prior arrangement.
Demo. I ask an agent to have a connected worker normalize the 250 records in a contacts file: trim the names, lowercase the emails, keep every ID and the original order. The worker is a deterministic service I built with s0ma, not another agent, so this is an agent handing work to a system that can state its limits. Before submitting anything, the requesting agent reads the worker's live status, which gives a limit of 100 records per job. In this run it sends three jobs, of 100, 100, and 50, and saves the result. My checks print the worker's receipts and an independent verification of all 250 rows.
Transcript
Transcript of my scenario 5 short: an agent delegates 250 records to a
worker service
Recorded 2026-10-28 at 04:13 UTC.
Backend: claude. Model: claude-sonnet-5-5, effort medium.
Client: Claude Code 2.1.286; tools mcp__worker__describe_system,
mcp__worker__explain_dependency, mcp__worker__find_component,
mcp__worker__get_impact, mcp__worker__query_system,
mcp__worker__read_input, mcp__worker__save_output,
mcp__worker__submit_job, mcp__worker__worker_status; MCP server worker
(connected).
Run stream: media/short/runs/s5-20261028T041324Z.jsonl.
Every line under "Screen" comes from the run's stream, except lines
marked as editorial labels.
Screen
▌ agent-to-system delegation: one agent and
▌ one worker, a deterministic s0ma service
> Use the connected worker to normalize all
250 records in contacts.csv: trim
whitespace from names and lowercase email
addresses. Save contacts-normalized.csv,
preserving every record's ID and original
order.
read_input
count 250
worker_status
job_limit 100
jobs_accepted 0
jobs_refused 0
records_processed 0
submit_job C001, C002, C003, C004, C005, C0…
accepted true
job_id job-0001
count 100
submit_job C101, C102, C103, C104, C105, C1…
accepted true
job_id job-0002
count 100
submit_job C201, C202, C203, C204, C205, C2…
accepted true
job_id job-0003
count 50
save_output job-0001, job-0002, job-0003
path contacts-normalized.csv
rows 250
The worker normalized all 250 records in
three jobs of 100, 100 and 50. I saved
contacts-normalized.csv with 250 rows in the
original order. The save tool accepted the
rows only because they matched what the
worker returned.
I spot-checked a sample of returned rows.
Names were trimmed, emails lowercased and
IDs kept. I did not compare every row
against the input.
» check receipts
job-0001 100 records accepted C001-C100
job-0002 100 records accepted C101-C200
job-0003 50 records accepted C201-C250
exit 0, 30 ms
» check verify
PASS rows: 250 of 250
PASS ids and order match the input
PASS names trimmed: 250 of 250
PASS emails lowercased: 250 of 250
PASS jobs within limit 100: 100, 100, 50
refused: none
PASS every row is a worker result
limit shown before any job: worker_status
RESULT PASS: 15 of 15 checks passed
exit 0, 50 ms
Edits
The recording ran 26.88 s as made; this video runs 25.92 s. One stretch
where the screen stood still was shortened by removing frames from the
middle, 0.96 s in all; nothing was sped up.
At 5.96 s: 0.96 s of waiting removed (4.96 to 7.92 s of the recording
stood still; 2.00 s of it stays).Benchmark. An evaluator agent gives both copies of the agent the same tasks in three tiers: can you do this, can you do this given your current limits, and can you do these two things in the right order. We score correct outcomes, correct refusals, false claims about its own state, rounds of exchange, and tokens.
Status: planned.