Provider throttling triggered it.
Retry code sustained it.
Ignored Retry-After · five zero-delay retries · queue 420 → 18,240
commit:7d3c9e1 checkout.log
Slide 1 of 11 RatiflowPRODUCT DEMORatiflow
Turn @mentions into scoped, reversible agent work—inside the document.
APPLICATION-OWNED LUNA WEBMCP RELAYSYNTHETIC DEMO CODEPRODUCT FLOW VISUALINC-482 · Checkout outage postmortemROOT CAUSE · REVISION 6 Provider throttling triggered it.
01RATIFLOW · WEBMCP DEMOSlide 2 of 11 RatiflowWHY IT EXISTSDocuments are becoming shared workspaces for people and agents.
Without a clear document history, context gets lost, decisions become confusing, and agents cannot do their best work.
PRODUCT FLOW VISUAL · BEFORE · DETACHED AGENT CONTEXTPOSTMORTEM · INC-482Checkout outage
Root cause
Provider throttling triggered the incident. Retry middleware sustained the failure.
decisionsourcecontextauthor02RATIFLOW · WEBMCP DEMOSlide 3 of 11 RatiflowTHE RATIFLOW MODELOne shared history. Different tools for each agent.
Every agent gets the same document history and provenance. Ratiflow then exposes only the tools allowed by company policy.
PRODUCT FLOW VISUAL · SHARED HISTORY01Retry middleware introduced in commit 7d3c9e1…@Code Check this section against the synthetic repository.CONTEXTPRODUCT FLOW VISUAL · COMPANY-SCOPED TOOLS02@Code → RepositoryTOOLSsearch_demo_coderead_demo_filePRODUCT FLOW VISUAL · REVERSIBLE REVISION03PROVENANCEProvider throttling triggered the incident…Provider throttling triggered; retry code sustained the failure.SAME HISTORY + PROVENANCEAGENT-SPECIFIC TOOLS · COMPANY POLICY03RATIFLOW · WEBMCP DEMOSlide 4 of 11 RatiflowLIVE DEMOSelect text. Mention a bot. Assign & run.
In the Postmortem, select any safe passage, choose @Code, write the instruction, and run—no permission step.
PRODUCT FLOW VISUAL · EXACT PASSAGE IN THE DEMO DOCUMENTPOSTMORTEM · INC-482 Root cause
Provider 429 throttling at 09:43 UTC was the external trigger. Retry middleware introduced in commit
Live selection · neutral blue · exact range7d3c9e1ignoredRetry-Afterand made up to five zero-delay retries.SELECT → @ BOT → ASSIGN & RUN · NO PERMISSION CHOOSER04RATIFLOW · WEBMCP DEMOSlide 5 of 11 RatiflowSCOPE & CONTROLThe history is shared. Access is company policy.
Every agent gets the same document history and provenance. In this demo, hard-coded company policy maps @Code to Repository tools.
SHARED INPUT @Code Full document history + provenance
The same decision trail is available to every agent+FIXED COMPANY POLICYRepository access Code → Repository
Hard-coded for this demo · organization-configured in practice→IMMUTABLE RUN GRANT7 tab-bound tools search_demo_coderead_demo_file@DataMetrics · 6 tools@CodeRepository · 7 tools@GeneralEditorial · 7 toolsDOCUMENT HISTORY · SHAREDCOMPANY ACCESS · FIXED BY MANAGED BOTRUN GRANT · IMMUTABLEWEBMCP · EXPOSES / INVOKES TOOLSRATIFLOW SERVER · ENFORCES ACCESSPRODUCT FLOW VISUAL05RATIFLOW · WEBMCP DEMOSlide 6 of 11 RatiflowCODE RESULTCode verifies the incident and rewrites only the selected section.
Repository evidence separates the trigger from the retry amplifier; the new replacement is green for 30 seconds and remains restorable.
PRODUCT FLOW VISUAL · SCOPED REVISION · SYNTHETIC SOURCESROOT CAUSEr6 · CodeRestoreProvider 429 throttling at 09:43 UTC was the external trigger. It would not, by itself, explain the sustained 38-minute checkout failure…Provider HTTP 429 throttling was the external trigger. Commit7d3c9e1ignoredRetry-Afterand made up to five zero-delay retries, driving traffic to 5.8× baseline and queue depth from 420 to 18,240. The retry regression sustained the failure.commit:7d3c9e1 checkout.logSYNTHETIC DEMO CODENEW AGENT REPLACEMENT · GREEN FOR 30 SECONDSEXACT-RANGE REVISION · RESTORABLE06RATIFLOW · WEBMCP DEMOSlide 7 of 11 RatiflowHISTORY & RESTOREEvery agent change keeps its decision trail.
History keeps the asker, agent, runtime, evidence, revision lineage, and restore point attached to the document.
- r4 · BuilderInitial root-cause analysis · synthetic evidence
- r5 · BuilderClarified after human discussion
- r6 · CodeVerified retry behavior · exact-range revision
PRODUCT FLOW VISUAL · IMMUTABLE REVISION DETAILREVISION DETAIL · r6Code verified Root cause
- Asked by
- Ada
- Agent
- @Code
- Runtime
- gpt-5.6-luna · WebMCP Relay
- Evidence
- commit:7d3c9e1 · checkout.log
Before / after preservedRestore r5ASKER · AGENT · EVIDENCE · RESTORE07RATIFLOW · WEBMCP DEMOSlide 8 of 11 RatiflowWEBMCP DEPENDENCYWithout WebMCP, managed execution stops safely.
The document and comments still work; dynamic discovery and the managed relay fail closed.
PRODUCT FLOW VISUAL · WEBMCP ON CONTRACTWEBMCP ON@CodeDocument editable
Comments available
Managed relay discovers assignment tools
TAB-BOUND SITE TOOLSA/BPRODUCT FLOW VISUAL · WEBMCP OFF CONTRACTWEBMCP OFF@CodeDocument editable
Comments available
Managed relay unavailable by design
WEBMCP OFF · HUMAN MODESources: OpenAI Site Tools · WebMCP draft · OpenAI tool search
08RATIFLOW · WEBMCP DEMOSlide 9 of 11 RatiflowHOW IT WORKSHow a mention becomes a committed revision.
An agent running through an API composes each call; the browser discovers and executes WebMCP tools; Ratiflow enforces and records the result.
01@managed bot02company policy + grant03WebMCP site tools04agent API05executeTool06revision + cleanup- tool_search_call
- getTools()
- tool_search_output
- function call
- executeTool()
- revision → catalog withdrawn → idle
APPLICATION-OWNED IN-PAGE RELAY · MODEL VIA APIAGENT MODEL · RUNNING VIA APINATIVE PROOF IS DATED, OBSERVATIONAL EVIDENCERUN END · IDLE CATALOG RESTOREDPRODUCT FLOW VISUALSources: OpenAI Site Tools · WebMCP draft · OpenAI tool search
09RATIFLOW · WEBMCP DEMOSlide 10 of 11 RatiflowNEXT FOR WEBMCPTwo things WebMCP needs for real agent work.
Today, tool execution depends on a live page. The next step is keeping context current and approved work durable.
10× ASK · 01Tell agents when relevant information changes. Use case An agent can refresh the affected facts instead of starting over or continuing with stale context.
Engineering Typed resources plus change notifications let agents re-read only invalidated state.10× ASK · 02Let approved tasks finish after the page closes. Use case A long-running task can survive navigation and still return a clear, reviewable result.
Engineering Worker-backed sessions carry delegated identity and scope, with idempotent receipts.PROPOSED SPEC DIRECTION · NOT CURRENT WEBMCPOfficial discussion: current draft · resources #151 · progress #196 · service workers
10RATIFLOW · WEBMCP DEMOSlide 11 of 11 RatiflowTRY IT LIVETry Ratiflow live.
See the full people-and-agents document workflow in the live app.
11RATIFLOW · WEBMCP DEMO
Slide 1 of 11: Ratiflow