Ruflo swarms: a receipt check that fails loudly

[daice77]

Hi rUv,

In Ruflo a swarm agrees on an answer, and a recent thread in your discussions was about catching false consensus in swarm outputs. The version of that problem I keep hitting with my own agents is smaller and older: an agent reports done, the swarm moves on, and nobody can later say which check ran.

I built a small, vendor-neutral kit for that: ownership claims that are rejected when two agents' paths overlap, and verification receipts that are rejected when a check failed or the worktree was never verified. Here is the interactive handoff demo, a real run of the verifier.

It is plain Git hooks, JSON schemas and one Python verifier, so it sits under any orchestrator. The Agent Handoff & Verification Kit is $29, and I offer a one-repository implementation pilot at $500, scope agreed first. I would like to know whether a hard receipt check belongs inside a swarm or outside it, in your view.

Olaf Kupschina
daice.net