Agents can generate results - but on what authority do we accept delivery?

30-Second Overview

MCP connects agents to tools. A2A connects agents to agents. AgentTeams orchestrates agent collaboration. But when an agent says "I'm done," no existing layer answers:

• What authorization backs this work?
• Did every step stay within scope and quota?
• Do tests, patches, and reports form a complete causal chain?
• Who has the authority to accept or reject the outcome?
• In a dispute, can a third party verify all the facts offline, without connecting to any party's system?

OpenWorkProof fills this gap: contracts, authorization, evidence, and acceptance for agent work. It doesn't try to make agents smarter. It makes their work authorizable, constrainable, verifiable, and acceptable - and rejectable when the evidence falls short.

A contrarian thesis: the primary bottleneck for multi-agent systems isn't model capability - it's accountability, authority, evidence, and acceptance. Without these, agents can generate results, but they can't become delegatable, auditable, billable production actors.

Why OpenWorkProof

Why Now

The market has turned. Gartner predicts 40% of enterprise software will embed AI agents by end of 2026 (below 5% in 2025). The EU AI Act's high-risk provisions are already in effect - organizations that can't prove their agents are "authorized, constrained, and auditable" face real legal risk.

The space is being validated by capital. In H1 2026, over $65M was publicly raised in the agent trust infrastructure category:

These projects solve "who is acting" and "how money moves" - the identity and payment layers. OpenWorkProof solves the layer they all leave untouched: what authority backs this work, why the process is trustworthy, and what makes the outcome acceptable - the work-contract layer. The two are complementary, not competitive.

An analogy: OAuth defined "how humans authorize apps," spawning a $10B+ market (Okta / Auth0). OpenWorkProof defines "how humans authorize agent work and accept results."

Core Principles

• Proof-Carrying Work: actions must carry machine-checkable authorization and result evidence
• No-Cloning Authority: child grants can only attenuate or consume - never replicate equivalent or greater permissions
• Multi-Scale Proof Composition: local credentials can only form an acceptable global proof when causality, evidence dimensions, correlation disclosure, and global conditions are simultaneously satisfied
• Fail Closed: unverifiable permissions, signatures, history, state, or evidence must never resolve as success
• Offline Third-Party Verification: validate_grant_chain enables third parties to verify the entire signed authorization history without connecting to any party's system