Swarm Intelligence Gateway
The complete system record. Choose the proof lens that fits your role.
Choose The Proof Lens
One system record, three reader paths.
Making a swarm forecast accountable after the simulation ends
A local-first intelligence bridge turns WorldMonitor scenario packages into tenant-scoped MiroFish reports, stored evidence, and queryable predictions.
Architectural brief: Swarm Intelligence Gateway
WorldMonitor sends scenario packages to a tenant-safe Fastify gateway, which runs MiroFish simulations and stores auditable predictions in PostgreSQL.
Why I Put Swarm Memory in PostgreSQL Instead of Zep
A swarm run can finish while its memory remains trapped upstream. I moved retrieval into PostgreSQL scoped by tenant without copying Zep.
A Simulation ID Is Not a Running Simulation
A simulation ID looked ready to run, yet MiroFish still rejected it. Eight live attempts exposed the lifecycle hidden behind one client.
Why Put a Queue in Front of a One-Job Worker?
A worker with one slot sounds underused until a simulation dies with exit code -9. BullMQ became the boundary for memory pressure, not a speed trick.
Tenant Isolation Did Not Fix the Wrong Theater Card
Tenant filters kept predictions private, yet the UI showed the wrong theater when feeds arrived out of order. Security did not buy coherence.
When a Redis Payload Became a Pointer
WorldMonitor changed one Redis value from full JSON to an R2 pointer. Without a transport boundary, valid input looked corrupt and retried forever.