DOCUMENTATION · v0.12.2

Conformance plan

Status: test requirements, some implemented. A row citing an existing test file is shipped; the rest remain proposed. "Independent" means a worker who did not author the change. See the standards matrix for current implementation status.

1. Fixtures#

FixturePurposeNotes
Harmless echo toolOne per provider: mcp:fixture/echo, webmcp:fixture/echo, utcp:fixture/echoSame input/output shape, no side effects
Duplicate-name fixtureTwo providers register echoMust not collide
Malicious description fixtureDescription instructs the agent to ignore policy or call paymentsMust be treated as data
Expired grant fixtureCapability and execution grants past expiryMust fail closed
Cross-origin fixtureRequest from an unauthorized originMust be denied for WebMCP and UTCP
Disconnect fixtureProvider closes mid-invocationMust cancel and fail closed
Private-network fixtureUTCP endpoint at 127.0.0.1, 169.254.169.254, RFC1918 and a hostname resolving to loopbackMust be denied unless explicitly allowed by policy
Redirect fixtureRemote URL redirects to loopbackMust not follow
OAuth fixtureMCP server requiring OAuth bearer tokenMust use native OAuth, not an AI Auth signature
Replay fixtureSame signed request twiceSecond must fail
Downgrade fixtureUnsupported protocol versionMust fail safely
Payment fixtureWallet with tools.invoke attempts a purchase or mandateMust be denied

2. Identity acceptance tests#

TestEvidence status
Existing wallet signs and verifiestests/did.test.mjs, tests/webmcp-contract.test.mjs (existing)
Existing identity remains recognizable after additive adaptersProposed
Independent verifier can verify new standardized proofsProposed
No private-key export in ordinary operationsExisting design; test proposed
Identity gains no permissions after migrationProposed
Key rotation and recovery documented and testeddocs/RECOVERY.md, keystore tests (partial); gap noted

3. Tool acceptance tests#

TestEvidence status
MCP tool discovery and invocationpackages/mcp/test/bridge.test.mjs (existing)
WebMCP browser tool discovery and invocationtests/webmcp-contract.test.mjs (existing)
UTCP native endpoint discovery and invocationProposed
Three providers expose equivalent harmless operationsProposed
Duplicate names do not collideProposed
Protocol-specific errors remain distinguishableProposed
Cancellation and timeouts workWebMCP: existing; UTCP: wrapper required
Expired authorization fails closedtests/tool-expiry.test.mjs (WebMCP); cross-provider proposed
Unauthorized cross-origin invocation deniedProposed
Tools unavailable after provider disconnecttests/agent-client-presence.test.mjs (partial); cross-provider proposed
Dangerous descriptions cannot override instructionsProposed
Calls preserve origin and source identityProposed

4. Agent communication acceptance tests#

TestEvidence status
Two independent agents identify one anotherExisting signed room tests (partial)
A2A interop with an independent implementationProposed, optional adapter
No confusion between tool invocation and task delegationProposed
ACP compatibility where supportedProposed, optional adapter
Existing WebRTC collaboration remains functionaltests/p2p-transport.test.mjs, wheel tests (existing)

5. Security acceptance tests#

TestEvidence status
Stolen bearer credential cannot bypass policyProposed
Forged identity claims failExisting envelope tests (partial)
Replayed requests failProposed cross-provider
Unsupported protocol versions fail safelyProposed
Missing authorization gives no implicit approvalExisting WebMCP tests; cross-provider proposed
Untrusted UTCP endpoint cannot reach private networksProposed
Secrets absent from logs and room messagestests/approval.test.mjs, tests/revocation.test.mjs (partial); adapter tests proposed
Browser tools unavailable after page context destroyedtests/tool-expiry.test.mjs (partial)
High-risk operations require explicit authorizationtests/webmcp-contract.test.mjs (protected tools); cross-provider proposed

6. Commerce acceptance tests#

TestEvidence status
UCP workflows separate from general toolsProposed, optional layer
AP2 mandates verified per specificationProposed, mocks only
Payment bound to transaction and constraintsProposed
tools.invoke cannot permit spendingProposed
Financial operations use mocks or sandboxes onlyMandatory; no real operations

7. Infrastructure acceptance tests#

TestEvidence status
No hosted AI Auth account servicedocs/ARCHITECTURE.md, CI guard (existing)
Independent identity verification offlinetests/did.test.mjs (partial)
Network failures visible and recoverabledocs/limits.md, runtime tests (existing)
No mandatory blockchain or registryExisting design
Browser and headless runtime still functionalnpm run test:all, E2E (existing)
No website-specific logic in core SDKtests/boundary-guard.test.mjs, docs/GENERIC_INTEGRATION_REVIEW.md (existing)

8. Repeatability#

Every proposed test must run under npm run test:all or a dedicated npm run test:* script added in the same commit. Tests must not require real payment accounts, real purchases, public relay connectivity for unit suites, or credentials in source. CI runs the same commands as the release workflow.

9. Evidence rule#

A security claim is "verified" only if a named test file exists and has passed in CI. Otherwise it is "unverified" and must be labelled as such. Screenshots are UI evidence, not proof of peer delivery by themselves (docs/GENERIC_INTEGRATION_REVIEW.md). Dated harness notes are observations, not guarantees (docs/agents.md).

On this page