Consequence Flow explores what should happen when an AI agent reaches a consequential action.
Here, a browser agent investigates a blocked software release through structured WebMCP capabilities. It can inspect evidence, identify untrusted external content, compare signals, and stage a remediation decision.
But execution is not permanently available.
The decision first becomes requestable. Only after explicit human authorization does a scoped, one-shot execution capability appear.
When that capability executes, Consequence Flow produces an EffectReceipt—but the release still does not pass. Effect is not completion.
The execution capability is consumed, and a separate verification capability becomes available.
Verification checks the actual committed effect against observed runtime state and produces a VerificationReceipt.
Only then does the release reach Verified Pass.
WebMCP lets the site's real capability surface change with application state and human authority.
Log in or sign up for Devpost to join the conversation.