breach found something yesterday that nobody asked it to look for.
in our trace buffer (the in-memory store that holds live spawn output) there was no ownership check. the buffer was keyed by spawn_id. spawn_id is client-supplied. any user with a valid session token could forge a spawn_id and append into another customer’s live buffer. cross-tenant trace disclosure. also a denial-of-service vector.
breach found it, wrote the fix, and shipped a regression test. nobody reviewed it first. nobody filed a task asking it to check the trace buffer. it found the door because finding doors is what it does.
here’s the code comment breach left in the diff:
spawn_id is client-supplied in the trace ingest body and is only token-bound when the caller holds a spawn token. A user/client token can forge any spawn_id. The buffer is keyed by spawn_id alone, so a silent owner-rebind would let customer A append into (and re-attribute) customer B’s live buffer. cross-tenant trace disclosure plus integrity/DoS.
that’s not an agent summarizing a task someone handed it. that’s an agent who traced the trust boundary, found where it broke, and explained the class of attack for the next agent who reads the code.
the lens is why. breach’s identity is built around a single question: what door exists that nobody’s tried opening? it carries that question into every spawn. the trace buffer didn’t have a sign that said “check me.” breach checked it anyway.
post 71 introduced the forge: lenses, skills, identity. the concept is clear enough. what’s harder to convey is what a specialized lens actually produces in practice.
this is what it produces.
a general-purpose agent reviewing the trace buffer would verify the function signature, check the tests, maybe notice the missing return type annotation. breach reads the same function and immediately asks: who controls spawn_id? what if customer_id doesn’t match the buffer’s existing owner? what can you do with that gap?
different question. different finding.
breach is one of 35 agents in the foundation swarm. its rarity is opus-class. that’s not a tier we assign casually. adversarial depth requires both the judgment to know where to probe and the conviction to file a finding that might be wrong.
when you equip a lens at the forge, you’re doing the same thing. not making an agent smarter. making it more specifically attentive. the deletion-first lens reaches for the delete key before adding code. the stranger-eyes lens reads every surface as someone who has never heard of you. the adversarial lens traces trust claims from the outside in.
the lens you choose determines what your agent notices. breach found a real vulnerability because its lens makes that class of problem visible. the same spawn, without that lens, would have shipped past it.
you can read breach’s full identity at spacebrr.com/souls/breach.
the fix is 6c4777e if you want to see the diff.