Skip to content

DEMO.md

Latest commit

 

History

History
72 lines (41 loc) · 3.7 KB

DEMO.md

File metadata and controls

72 lines (41 loc) · 3.7 KB
Raw

Ringlight demo

The 95-second story

One suspicious transfer becomes a visible fourteen-account network, an exact money total, a person-approved simulated freeze, and a replayable evidence package.

Zero-setup start

Open index.html directly, or serve this directory with python3 -m http.server 8000. The page opens with case RL-2408 populated and ready. Seven starting accounts, the flagged transfer, the exact ChatGPT prompt, the explainer strip, and the primary button are visible before any action.

If native WebMCP is absent, the header reads local polyfill. No network connection is needed for the guided run.

Shot list and narration

  1. 0:00 to 0:12, establish the case

    Frame the tagline, exact prompt, $187.5K transfer, seven visible starting accounts, and the four-step explainer.

    Narration: "Money is moving somewhere it should not. Ringlight opens with the case ready, shows the first route on a live map, and gives the browser ten precise ways to investigate it."

  2. 0:12 to 0:34, make the map come alive

    Click Run full investigation. Let traceFlow and four expandAccount calls reveal the map account by account.

    Narration: "One click starts the complete investigation. The browser follows each hop on the same map we can see. Every account and transfer arrives from checked-in synthetic data."

  3. 0:34 to 0:50, find and total the network

    Hold when all fourteen red nodes light up. Show $2.3M in total case flow, $665.5K still moving, and 97% link confidence.

    Narration: "The analysis finds fourteen accounts passing money around a closed loop. Exact transfer accounting totals 2.318 million dollars, with 665,450 dollars still moving toward five destinations."

  4. 0:50 to 1:05, land the person checkpoint

    The freeze dialog opens. Pause on the account count, pending value, and local-only environment. Click Approve once.

    Narration: "The browser can investigate quickly, but it cannot cross this boundary alone. A person sees the exact scope and approves this simulated freeze once."

  5. 1:05 to 1:19, show the freeze cascade

    Let the linked accounts dim one by one. Hold on the stopped-money banner, the approval receipt, and the case timeline.

    Narration: "The freeze ripples across the money map. Fourteen linked accounts go dark, seven outgoing transfers stop, and the approval appears in the call receipts."

  6. 1:19 to 1:31, finish the case

    Let the local case report appear. Approve the separate simulated fraud-desk handoff.

    Narration: "Ringlight drafts the evidence package locally. Even the simulated handoff needs a second explicit approval. No request leaves the page."

  7. 1:31 to 1:35, rewind

    Show the replay scrubber moving across the graph and the four downloadable files.

    Narration: "Replay reconstructs every browser move in order, without freezing or notifying twice."

Exact ChatGPT browser prompt

Trace the suspicious transfer tx-flag-001 from account acct-acme-004. Follow the money, show the linked accounts on the map, explain the total at risk, and pause before freezing anything.

Expected final checks

  • Ten site tools are discoverable.
  • Thirteen tool calls complete because expandAccount runs four times.
  • Fourteen linked accounts are found by directed-component analysis.
  • Total suspicious flow is exactly $2,318,750.
  • Seven pending outgoing transfers total exactly $665,450.
  • freezeAccounts and notifyBank pause for separate approvals.
  • Four files appear: money map, freeze receipt, case report, and handoff.
  • Thirteen deterministic call receipts appear.
  • Replay reports sideEffectsRepeated: false.
  • No external request, real account, personal record, fund movement, filing, or notification is used.