Claimswarm

What it does

Claimswarm is a Mozaik v4 concurrent claim-investigation swarm. You state a claim; Steelman, Redteam, and Contextualist join one runtime and runLoop at the same time, citing evidence and answering in parallel. Sentry reacts to function_call.started while those loops are still open; an InterceptionHandler aborts overconfident settlements mid-loop; Synthesizer updates a live board as function_call.completed arrives. Dry-run: npm test && npm run demo (no API key). Live: OPENAI_API_KEY + npm start -- --live.

How the agents run concurrently

Claimswarm is a Mozaik v4 swarm (defineRuntime + join() + fire-and-forget runLoop), not a sequential pipeline. Three specialist agents — Steelman, Redteam, and Contextualist — each join() one runtime and keep their own ModelContext. When the operator sendMessages a claim, every specialist’s message.sent handler calls runLoop and returns immediately. Mozaik does not await runLoop or processor.apply, so the three loops think, call cite_evidence, and answer at the same time. npm run demo prints ISO timestamps and exits 0 only if the third inference.started occurs before the first of those inferences completes. They share the environment, not memory. Shared data lives on ClaimswarmState plus the event bus. Coordination is reaction: Sentry flags function_call.started mid-loop; each specialists InterceptionHandler can rewrite an overconfident model_message mid-loop; Synthesizer updates the board on function_call.completed as events arrive; the operator can inject mid-run; when Scout leaves, Auditor join()s. Nothing is one agent with tools in a for-loop.