Menu

1 / 8

Merged Isn't Delivered: Building CommitmentProof, a Two-Agent Switch Workflow

DEV Community: github·Aadi Harale·9 days ago
#oLhhtPZL
#devtogithub#technology#devto#dev#commitment
Reading 0:00
15s threshold

A pull request is merged. 27 of 27 checks are green. Support is ready to tell the customer "it's fixed." Can they?

The short version

CommitmentProof checks the proof behind a software promise before anyone tells a customer it is kept.

Two separate Codex agents work in one Switch-connected Discord room with a human. The Evidence Agent collects source-linked GitHub proof. The Coordinator Agent applies a deterministic completion policy and drafts the next step.

On a real merged PR, microsoft/vscode #331010 , the policy returned NEEDS_EVIDENCE . The PR was merged and 27 of 27 checks passed, but nothing proved deployment or QA.

Instead of closing the promise, the Coordinator proposed an exact GitHub issue. A human replied approve , created issue #2 by hand, and the Coordinator verified it through GitHub's read-only API.

The workflow concluded with a human-approved GitHub follow-up, independently verified by the Coordinator Agent.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.