Agent Atlas / Comparison Labs

Compare the boundary, not the brand.

Each lab starts with one architectural question, shows the project evidence state, and keeps uninspected separate from absent.

23 mapped projects

Tool Contracts

When does an API, MCP resource, shell command, or UI action become a model-usable tool?

Check whether the project separates discovery, schema validation, credential authority, approval, execution, and receipts.
17 mapped projects

Governed Memory

Who owns saved agent context, and how can a reader tell whether it is current, scoped, and safe?

Look for provenance, namespace, retention, no-secrets rules, search scope, compaction visibility, and migration tests.
14 mapped projects

Delegation Receipts

How does a parent agent prove what a child did, received, and returned?

Find parent IDs, child IDs, sent payloads, received results, lifecycle states, cancellation behavior, and merge rules.
21 mapped projects

Approval Boundaries

Where does consent live when an agent uses tools, wakes later, or delegates work?

Trace the decision from prompt to worker thread to executor, and reject designs that collapse scoped approval into global trust.
19 mapped projects

Human Workbench

Can the operator see enough of the agent system to steer, review, stop, and resume work?

Inspect review surfaces, status indicators, session threads, branch summaries, pending work, and evidence rendering.
24 mapped projects

Sessions And Recovery

What survives interruption, restart, protocol change, or a client disappearing?

Find durable session identity, serialized state, replay rules, expiry, cancellation, reconciliation, and the point where an unknown effect becomes safe to retry.
24 mapped projects

Evidence And Evaluation

What would prove that the agent did the intended work rather than merely reporting success?

Look for traces, diffs, tests, environment effects, failure classes, eval criteria, provenance, and a caveat that separates project-owned evidence from production outcomes.
24 mapped projects

Maturity Signals

Which changes show agent projects leaving prototype mode and becoming maintainable infrastructure?

Favor tests, rollback decisions, release contracts, self-hosting checklists, source-visible caveats, and boring operational edges.