Skip to the record
Precedent
ProductOpen the app

The evidence behind the demo

Twenty memories.
One record,
append-only.

Precedent’s rules do not live in a settings database. The mainnet record holds twenty rule, correction, and outcome memories written through Walrus Memory on Sui. This page asks Tatum’s gateway to confirm that the record is still there.

Walrus MemoryThe storeTatumThe checkSui mainnetThe source

Live attestationTatum Sui GraphQL

Checking

Asking Tatum’s Sui GraphQL gateway.

Checkpoint
Not yet
Latency
Not yet
Checked
Not yet
Gateway
Not yet
Detail
Waiting for the first check.
Waiting for TatumA pass confirms the account and delegate, not the truth of every memory.

Read the badge

Know exactly
what this proves.

A verification badge is only useful if it is specific about its edges. Here is what the live check above confirms, and what it leaves to you.

What this check confirms

  • The MemWal account object exists on Sui mainnet at the checkpoint shown above.
  • The account is active, not frozen, and returns onchain content.
  • When an agent key is configured, that delegate is registered to the account.
  • Tatum’s Sui GraphQL gateway answered at the time shown.

What it does not

  • It does not prove that every memory is correct, or that a particular order happened.
  • It does not verify the public demo’s basket. That store is separate and resettable.
  • It does not replace reading the account on a public explorer yourself.
  • It does not make this a checkout. No orders are placed.

In the record

What a household
remembers.

Not a preferences file. A history of decisions, kept in the words that made them, including the ones that were later overruled.

  1. 01
    Rules

    What to buy, switch, or skip, in the words the user actually used.

    Written in your words
  2. 02
    Corrections

    The old rule stays on the record. The new one supersedes it. Nothing is erased.

    Superseded, never deleted
  3. 03
    Outcomes

    What happened after the order, including the returns that changed the rule.

    The reason why
  4. 04
    Observations

    The context around a decision: guests, a price jump, a month that called for restraint.

    Context, kept
  5. 05
    Audit findings

    Where two rules disagree, and which one still governs the basket.

    Conflicts, resolved

Verify it yourself

Don’t take the
badge’s word for it.

Open the account on SuiVision. Check the delegate key. Run the Tatum check above and compare the checkpoint. Nothing on this page is a screenshot.

Open SuiVision Read the source

The public app is a separate, resettable demo. The mainnet record is append-only and is never changed by the demo.

  1. 01
    Open the account.

    Find the MemWal account object on SuiVision.

  2. 02
    Check the delegate.

    Confirm the agent key above is registered to the account.

  3. 03
    Compare the checkpoint.

    Run the Tatum check and compare it with the explorer.