REPLAY / SIMULATION

Frozen protocol fixtures. No live transaction, AI attestation or physical verification is claimed.

Mode & demo role

Live control · read-only

The testnet API, without a live runner.

This console verifies the configured MEND API and shows its LIVE_TESTNET health. It does not execute testnet actions and does not start the scenario lifecycle. If the API is missing, unreachable or not in LIVE_TESTNET mode, the app stays in REPLAY / SIMULATION with frozen fixtures.

READ-ONLY TESTNET CONSOLE — TEST VALUE ONLYREPLAY is the default · MAINNET is never selectable

API mode

REPLAY

TEST VALUE ONLY

No mainnet, no deploy, no real funds, no scenario runner. Explorer links are testnet-only and only appear for plausible NEAR transaction hashes returned by the API.

Hub
mend-hub-v2.testnet
Token
mend-usdc.testnet
Checks
GET /api/mend/health

LIVE_TESTNET is not verified

The app is in REPLAY / SIMULATION. Selecting LIVE TESTNET performs a fresh health check against /api/mend/health. The mode only changes when the API answers with mode LIVE_TESTNET and is not degraded.

Open mode & demo role

API health · read only

Health check, not a scenario runner

The page calls GET /api/mend/health through the same-origin proxy. It never calls /v1/live/run-scenario and never claims a transaction.

Checking
API modechecking…
Health statusnot checked
Databasenot reported
Runner flagnot checked

Checking the same-origin API proxy…

Last checked — · No demo role stored (see /demo)
The web UI exposes no live scenario runner. This deployment is expected to run with MEND_LIVE_SCENARIO_ENABLED=false; the same-origin proxy also refuses the runner endpoint unless it is explicitly enabled. There is no “run scenario” button, no wallet creation and no transaction from this page. Switching to LIVE TESTNET only enables this read-only status view.

Recorded reference · no live transaction

The recorded repair, clearly labelled

This is the frozen canonical repair from protocol-v1 / fixtures-2026-11-10. It is a recording — not a testnet execution — and receives no explorer links.

REPLAY / SIMULATION

Every event below is a fixture. No wallet, faucet call or transaction occurred.

The live console verifies API health only. It does not replay fixtures into a live claim and never converts recorded hashes into explorer links.

  1. Report

    Report received without a wallet

    Photo and description submitted. EXIF/GPS metadata removed in the browser before upload.

    anonymous reporter · case_7J2mQ9xLk4Pz1VbN

    • Redacted media hashaaaaaaaaaa…aaaaaa
  2. Report

    Second report received

    A nearby reporter describes the same bench damage.

    anonymous reporter · case_3Hs8Kd2Lm9Qw4XcR

    • Redacted media hashbbbbbbbbbb…bbbbbb
  3. Triage

    Duplicate cluster confirmed by a human steward

    Private AI proposed 94% confidence. The steward confirmed the merge; no automatic merge was applied.

    steward.mend.testnet

    • Cluster fixtureCL-0001
    • Human decisionsteward.mend.testnet
  4. Authorization

    Scope and maximum budget approved; DAO proposal attached

    Steward approves the repair scope. The DAO envelope and scoring policy are referenced, not invented by AI.

    steward.mend.testnet + mend-dao.sputnikv2.testnet

    • Scope hash441a425d51…91d092
    • Policy hash1a8a985878…42357d
  5. Funding

    Sponsor funded 100 test USDC

    Exact-token, exact-amount funding into the work-order escrow. Test value only.

    sponsor.mend.testnet

    • Funding tokenmend-usdc.testnet
  6. Sealed bids

    Sealed bidding opened

    Three rostered contractors may commit. Competing values are invisible until the reveal phase.

    steward.mend.testnet

  7. Sealed bids

    Three sealed commitments recorded

    Commitment hashes are public; price, duration and warranty remain sealed.

    3 rostered contractors

    • BID-A-BENCH-0011e1b013855…2d67a0
    • BID-B-BENCH-001fcb0780b0d…79d968
    • BID-C-BENCH-001008850641e…dbfce2
  8. Sealed bids

    Reveals checked against commitments

    Every revealed bid matched its commitment hash, arrived in the reveal window and came from the approved roster.

    Hub contract

  9. Deterministic score

    Deterministic score produced

    A hash-pinned WASM policy ranks total value. No LLM chooses the winner.

    OutLayer execution (replay fixture)

    • WASM hash790f3eb4e0…a3ef42
    • Input hashf44bd67a69…35e947
    • Output hash792aba5f6d…71304d
  10. Award

    Steward confirmed the rank-1 eligible bid

    contractor-b.mend.testnet awarded at 80 USDC. The unallocated 20 USDC returns to the sponsor.

    steward.mend.testnet

    • Human award confirmationsteward.mend.testnet
  11. Work

    Contractor started work

    Only the awarded contractor can start and submit completion for this work order.

    contractor-b.mend.testnet

  12. Evidence

    Redacted completion evidence submitted

    Six checklist items expected. Evidence is stored privately and referenced on-chain by redacted hash only.

    contractor-b.mend.testnet

    • Completion evidence629d602928…40fb88
  13. Inspection

    Independent human inspector accepted completion

    The inspector is not the contractor. Acceptance releases exactly 90% and starts the durability window.

    inspector.mend.testnet

    • Human acceptanceinspector.mend.testnet
    • Notes hashcaef7d9ff1…44a9f2
  14. Payment

    72 USDC completion payment recorded

    90% of the 80 USDC award. The remaining 8 USDC is held for durability.

    Escrow

    • No live transaction hash in replay
  15. Inspection

    Durability inspection passed; 8 USDC holdback released

    Same work order. Same asset history. The durability timestamp was fixed before the repair began.

    inspector.mend.testnet

    • Human durability decisioninspector.mend.testnet
    • Physical observationSeat and armrest stable after loading check
  16. Payment

    8 USDC holdback released; work order CLOSED

    Total: 20 refunded + 72 completion + 8 holdback = 100 funded. Released exactly once.

    Escrow

    • No live transaction hash in replay

REPLAY / SIMULATION. The API was not verified in LIVE_TESTNET mode. Frozen protocol fixtures are shown; no live transaction or attestation is claimed.