You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gas Town: rejecting the receipt before it reaches the Refinery
#4946
The Refinery in Gas Town is the most serious answer I have seen to the merge problem: verification gates on the merged stack, bisect the red one out. The open question in your discussions, what happens when one agent's changes break the combined application, is the one I kept hitting one step earlier. The polecat says done, the evidence link points at something, and nobody can later tell which check actually ran on that worktree.
I built a small, vendor-neutral kit for that step: 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 would sit under a merge queue rather than replace it. The Agent Handoff & Verification Kit is $29, and I offer a one-repository implementation pilot at $500, scope agreed first. What I would most like to know is whether you see a hard receipt check as the Refinery's job or the polecat's.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Steve,
The Refinery in Gas Town is the most serious answer I have seen to the merge problem: verification gates on the merged stack, bisect the red one out. The open question in your discussions, what happens when one agent's changes break the combined application, is the one I kept hitting one step earlier. The polecat says done, the evidence link points at something, and nobody can later tell which check actually ran on that worktree.
I built a small, vendor-neutral kit for that step: 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 would sit under a merge queue rather than replace it. The Agent Handoff & Verification Kit is $29, and I offer a one-repository implementation pilot at $500, scope agreed first. What I would most like to know is whether you see a hard receipt check as the Refinery's job or the polecat's.
Olaf Kupschina
daice.net
All reactions