capability gating · kill switches · audit ledgers · graduated autonomy
Chicago, IL · connorevans29@gmail.com
I built four of these over five months without intending them as a set. They converged on the same architecture anyway, in three different languages, and I only noticed once I put them side by side.
┌──────────────────────────────────────────┐
an agent wants to │ 1 declare it first ....... manifest │
do something │ 2 gate it ................ arbiter │
│ │ 3 bound the spend ........ budget │
└──────────────▶│ 4 stop it mid-flight ..... revoke │
│ 5 write down what happened ledger │
│ 6 earn the next rung ..... trust │
└──────────────────────────────────────────┘
│
┌───────────────┬───────────────┼───────────────┐
▼ ▼ ▼ ▼
LOOM ONEXUS WFR SMADP
Rust · TS Python TypeScript Python · Docker
| LOOM | ONEXUS | WFR | SMADP | |
|---|---|---|---|---|
| declare first | organ manifest | Aegis manifest | tool policy | agent profile |
| gate | sandbox validation | check_capability |
trust gate | tripwire engine |
| revoke live | per-organ | revoke() |
kill switch + halt | stale on drift |
| bound spend | per-organ budget | trust tiers | cost ledger | judge triage |
| record it | git timeline | Chronicle | route ledger | chronicle log |
| earn autonomy | consent cards | suggest → autonomous | trust sentinel | evidence ladder |
Every one is the same bet: an agent should have to say what it needs before it runs, be refused when it asks for more, be stoppable mid-flight, and leave a record you can read afterwards. I find that more interesting than making agents capable, because capability is the part that already works.
|
Scout
|
Hired as an inbound SDR, then selected to lead workflow automation and Clay-based enrichment for the sales organization. That mandate became Scout: prospect discovery, account intelligence and enrichment pipelines in one internal platform, comparable in scope to LinkedIn Sales Navigator. Now used by Flexport sales employees in more than 30 countries; my team has held 100% of quota throughout. The only system here whose adoption was decided by other people. |
|
ONEXUS
|
A local-first agent runtime built on Aegis, a 786-line capability arbiter. An agent declares filesystem reach, outbound domains and tools in a manifest; every call is checked against it, allowed or denied, and appended to a ledger that is never rewritten. A static test AST-parses every kernel module and proves none but Aegis can open a socket. Then I red-teamed it,
found that |
|
LOOM
|
An offline computer that builds itself. Describe a capability in one sentence and a local model plans it, writes the code and its tests, proves it in a sandbox, repairs its own failures over bounded rounds, and commits to a git timeline. It then asks permission before the new organ may run. Powers are declared, budgeted and revocable while running. No cloud, no subscription, no telemetry. |
|
SMADP
|
Safe Multi-Agent Deployment Platform. Nobody has systematically studied what happens when the coding agent, the browser agent and the email agent all share your filesystem and OAuth scopes. SMADP publishes that matrix, with a tripwire engine that halts a run mid-flight when a planted secret leaks or egress steps outside the allowlist. Every verdict carries its evidence rung as a field on the record. Eleven pairs have actually been executed against each other; 2,268 are labeled priors, in the data rather than a footnote. |
|
AUSPEX
|
A living globe of the planet's perils and its breakthroughs, free and login-free. Autonomous pipelines read USGS, GDACS, NASA FIRMS, Launch Library and global RSS, score each event for severity and confidence, and render it honestly: calm where the world is calm, red reserved for genuine danger. The disaster path needs zero API keys, which is what lets it stay free. |
|
HYPERION
|
A browser game about running a private orbital agency over a living Earth, with real orbital mechanics, real world events, and a world that keeps evolving while you are offline. A scheduled server tick advances every away player's world, so you return to a digest of what changed without you. |
|
Flexport SDR Console
|
I wanted to work in freight forwarding, so instead of writing a cover letter I built the tool the job would need: ICP-scored prospects, live AIS vessel positions, live ADS-B aircraft, port-congestion rings, FRED macro data and tariff tables in one console. The working core came together in a 30-hour weekend before my final interviews. I kept building it after, and ran it in production for my own team. |
|
EMBER
|
An offline survival console for the day the network isn't there: a local LLM advisor, 38 field
guides, offline navigation, a solar power budget, and a Forge that rewrites the console's own code
from a plain-language prompt. Genuinely zero external requests; the only thing it ever talks to
is |
the README beside it says how much was verified and how much was inferred.

