RecallOps Checking API

WEBMCP INCIDENT CO-CONTROL ROOM

Investigate with agents.
Keep authority human.

RecallOps continuously sculpts the visiting agent’s tool surface as authority moves between agent, operator, system observer, and independent reviewer.

Use the browser:control-in-app-browser skill and its browser bridge to access that tab’s WebMCP capability.

LIVE PROOF · IN PROGRESS ASSURANCE · IN PROGRESS

01 / MEASURABLE PROOF

Executable policy invariants.

Loading evaluation
RecallOps safe top-1—baseline —
Unsafe selection rate—baseline —
Isolation violations—tenant + validity gate
Mean reciprocal rank—— cases

The headline suite is a small, synthetic, deterministic policy regression set—not an end-to-end retrieval benchmark. It covers attractive failed remediations, incompatible versions, invalid memories, and cross-tenant candidates. CI rejects policy regressions; live provider status is shown separately. In the live loop below, open Candidate evidence to see vector candidates become explicit policy selections or rejections.

02 / LIVE CLOSED LOOP

Turn an incident into governed memory.

Isolated deterministic simulator

ACTIVE SYNTHETIC INCIDENT

checkout-latency-42

Checkout p95 latency and error rate exceed the sandbox SLO.

Exact prompt for the visiting agent

Continue using the RecallOps page already open in the ChatGPT Desktop in-app Browser.

UNTRUSTED · incident and memory text AUTHORITATIVE · workflow, identity, evidence bindings

Incident signal

Production authentication
1 Analyze2 Approve3 Simulate4 Verify5 Review6 Recall
Checking provider status…
WEBMCP CAPABILITY INSPECTOR

Browser capability surface

Detecting browser support
Workflow state
INVESTIGATING
Server epoch
—
Authority owner
AGENT
Available to agent
  • Waiting for WebMCP registration
Withheld by policy
  • Protected transitions are never exposed
WebMCP activity rail

    PROTECTED ACTION PANEL · HUMAN ONLY

    Current authority and consequence

    The agent may inspect and prepare. No protected transition is available through WebMCP.

    Submit the incident. The agent will retrieve governed memory, explain its choice, and require approval for any mutating action.

    AUTHORITY CHAIN

    Evidence earns authority through explicit handoffs

    1. Agent investigates
    2. Agent prepares
    3. Operator approves
    4. System observes
    5. Agent assesses
    6. Reviewer governs reuse
    Verify persisted authority events
    1. Loading server ledger…

    03 / SYSTEM OF RECORD

    One causal path. Explicit trust boundaries.

    Tenant filter before rankFour-eyes activationImmutable provenanceConfidence decayApproval before mutationProvider degradation