DOCUMENTATION · v0.12.2

Implementation plan

Status: proposed plan. No implementation work is authorized by this document. Each task is small, independently testable and subject to independent review before merge. The first breaking change is explicitly out of scope.

0. Gates#

Before any task starts:

  1. Council decision accepted (COUNCIL_REPORT.md).
  2. Threat model reviewed by the Security Supervisor (THREAT_MODEL.md).
  3. Conformance fixtures defined (CONFORMANCE_PLAN.md).
  4. No task may change the identity format, consent version or wire protocol.

1. Task sequence#

#TaskOwnerDepends onDeliverableAcceptance test
T0Baseline and code inventoryWorker (reviewer)—Test baseline report; flaky tests identifiednpm run test:all baseline recorded; no new test skipped
T1Unified tool descriptorWorker (engineering)T0packages/p2p/tool-descriptor.js + typesDescriptor validation tests; no native field silently weakened
T2Source-aware registryWorker (engineering)T1packages/p2p/tool-registry.js, tool-audit.jsNamespaced IDs, duplicate isolation, bounded audit, no payloads
T3WebMCP catalog through registryWorker (engineering)T2Refactor of packages/p2p/webmcp.jsExisting tests/webmcp-contract.test.mjs unchanged and passing
T4MCP adapterWorker (engineering)T2packages/mcp/adapter.jsNative errors preserved; no OAuth substitution; existing MCP tests pass
T5UTCP adapter behind flagWorker (engineering)T2packages/p2p/utcp-adapter.js, optional dependencyDiscovery and direct invocation with official SDK; destination policy tests
T6Cross-provider policyWorker (security)T3,T4,T5Policy module and deny-by-default rulesCross-origin, expiry, disconnect and high-risk tests
T7Additive identity adaptersWorker (identity)T6Verifier for standardized proofs, additive onlyOffline verification; no change to agent: identity
T8Delegation experimentsWorker (identity)T7Separate experimental packageDocumented limitations; no core dependency
T9A2A / ACP adaptersWorker (interop)T6Optional adaptersIndependent implementation interop; task ≠ tool test
T10UCP / AP2 layerWorker (commerce)T6Separate optional package, mocks onlyNo tools.invoke path to spending; no real financial operations
T11MCP revision migrationCouncil decision requiredT4New adapter revisionSeparate compatibility plan; breaking change, not in this milestone

2. Ownership rules#

  • Workers must not edit overlapping files concurrently.
  • Each task has one author and one independent reviewer.
  • Security-sensitive tasks (T5, T6, T7, T10, T11) require Security Supervisor sign-off.
  • The Engineering Supervisor resolves integration ordering, not design disputes.
  • The Governor resolves disagreements after independent arguments are recorded.

3. Compatibility policy#

Change classAllowed now?
Additive exports behind new subpathsYes, with docs/BOUNDARIES.md updated (DTC-06)
New optional dependency behind a flagYes
Refactor with identical wire behaviorYes
Change to agent: identity derivationNo
Change to consent version or signed envelopeNo
Change to WebRTC wire eventsNo
Removal of existing CTA or package exportNo
MCP 2026-07-28 revision migrationNo, separate approval
Real payment or purchase operationNo

4. Rollback#

Each task is one focused commit. Rollback is git revert of that commit plus removal of any generated docs entries. Feature flags default off for new providers. The previous catalog path stays live until conformance passes.

5. Documentation updates required by implementation#

  • docs/BOUNDARIES.md export list must match live root exports exactly (DTC-06).
  • docs/TRACEABILITY.md needs feature → code → test rows for each new provider.
  • STANDARDS_MATRIX.md conformance rows move from "not implemented" to "implemented and tested" only after tests pass.
  • docs/README.md may link to architecture/*.md only after those pages are added to the renderer's doc list and verify:docs passes.
  • CHANGELOG.md records each shipped milestone with the actual test results.

6. Definition of done for the first milestone#

The first milestone is T1–T6: a single API for listing and invoking tools from MCP, WebMCP and UTCP, preserving native auth and authorization. It is done when:

  1. All three providers expose the same harmless test operation through the registry.
  2. Duplicate names do not collide and protocol-specific errors remain distinguishable.
  3. Cancellation, timeout, expiry and disconnect fail closed.
  4. Unauthorized cross-origin invocation is denied.
  5. Native MCP OAuth is not substituted or proxied.
  6. UTCP calls respect the destination policy and credential isolation.
  7. Independent review and Security Supervisor sign-off are recorded.
  8. npm run test:all, npm run build, npm run verify:docs, npm run format:check and package verification pass.
On this page