Formal document · Delivery plan
Roadmap & proof gates
This roadmap is an ordered verification plan, not a claim that the work below is complete. Source changes, local tests and a live production release are different evidence states.
Gate 0 · Source and origin
Reconcile the delivery path
- Confirm the Cloudflare Pages project is connected to
tech4humanity-002/webMCP-live. - Identify the actual deployed source commit and origin for
webmcp.mcp-native.com. - Preserve the existing production version until a verified replacement and rollback exist.
Gate 1 · Site quality
Make the public site reviewable
- Check navigation and content on desktop and mobile, keyboard operation, contrast and reduced motion.
- Check all internal and external links, canonical URLs, security headers and page metadata.
- Label experimental, implemented and planned capabilities separately.
Gate 2 · Runtime tests
Prove one read-only action
- Run the committed test suite and attach exact output to the runtime proof issue.
- Connect the safety core to a real browser adapter in an isolated test profile.
- Record successful target/action/result and denial, malformed-input, origin, timeout and redaction tests.
Gate 3 · Deferred execution
Prove isolation and durable work
- Implement the durable Cloudflare queue producer/consumer only after the agreed interface and permissions are defined.
- Demonstrate that background work does not interfere with the user's active browser.
- Prove idempotency, pause/cancel, retries, receipts and recovery from uncertain outcomes.
Gate 4 · Release decision
Release only with evidence
- Match production URL to the intended commit.
- Run desktop/mobile smoke tests and confirm reciprocal MCP Native/WebMCP links.
- Record evidence and rollback details in GitHub/SOCme before declaring production verified.
Current known boundary
The runtime repository currently describes its safety core as PARTIAL. An API-presence check, static website, local unit test or source commit does not establish that browser integration, Cloudflare deployment or end-to-end MCP execution is working.
Implementation evidence: browser integration proof issue · durable queue and browser isolation issue · site delivery issue.