---
card_id: 40X_sim_<slug>
title: "<Sim title in plain prose, no Sim-prefix>"
schema_version: 3
estimated_minutes: <int, typically 3-30>
audience_cluster: <clinical | legal | gov | it | research | civic | recovery>
mock_ui_theme: <generic_modal | lab_console | voting_portal | claim_console | records_filer | home_hub | hearing_room>
sources:
  - sources/40X_sim_<slug>_source.md
supersedes:
  - ../40X_sim_<slug>.md (canonical V2 card; remains live until cards_v2 promotes)
---

# <Sim title in plain prose, no Sim-prefix>

> EDIT GUIDE: each `## H2` is one step. The HTML comment immediately
> above each H2 binds the prose to the source step ID. Do not edit
> the comment. Edit the prose freely; the build script round-trips it
> back to the JSON sidecar.

<!-- step.id = landing -->
## Landing

You're a <persona> who's been <inciting incident> — or you're carrying
the weight of one in the back of your mind.

The hook on Merkle Trust's landing names the feeling: <one or two
specific tangible things this audience already knows by their first
names>.

<!-- step.id = install -->
## Picking how you'd evaluate

This walkthrough is the test drive — no install required.

Most <persona>s won't self-host anyway; the realistic install path is
to subscribe to a regional <audience-compliance>-compliant operator
who runs the infrastructure for you.

Three other paths exist, with the full set described at the close.

<!-- step.id = first_concrete -->
## The first concrete moment

Meet <named persona>, your <synthetic something>. <2–4 sentences that
describe what's loaded and why this person matters to the sim.>

<2–3 sentences describing what the cursor does next, in passive
narrative voice — "the sim opens X," "the panel surfaces Y," not
"you see X" or "the visitor sees Y." This is the calm moment.>

<!-- step.id = is_this_real -->
## "Is this real?"

Skeptical right now? That's the right reaction.

The "Show me what just happened" panel breaks it down in three
plain-English bullets — no jargon.

"Anchored here" opens a real receipt: a timestamp, a merkle root, and
one line explaining each.

If you'd like a different LLM to check whether any of this is
exaggerated, the **.md** button copies a structured version of this
step. Paste it into your own assistant for an independent read.

No "patent pending." No "revolutionary blockchain." Just the
mechanics, with a live receipt you can click.

<!-- step.id = ceremony -->
## The ceremony moment

Before the sim moves on, a ceremony runs. Fifteen seconds, and it's
what makes everything you just saw defensible. It runs again at the
same time tomorrow, and the day after, and the day after.

The ceremony is the daily practice — the bot does the math, you read
the morning report. The progress bar finishes. The numbers settle.
The card moves on.

<!-- step.id = close -->
## The close

Three ways to leave, no pressure either way.

Whichever direction the sim takes from here, you take a signed
package with you — yours to keep, downloaded directly when you finish.
The package contains a manifest with the merkle root of every file in
the simulated set, a certificate of registration carrying your earliest
attestation timestamp, the architecture docs that explain what Merkle
Trust does, the verification scripts (`verify.sh` and `verify.py`,
stdlib only) that re-prove the package against itself, a
`claude_prompt.md` you can paste into any LLM for an independent
audit, the JSON schemas the verifier reads to validate your manifest
and certificate offline, and a `DISCLAIMERS.md` covering the legal,
data-handling, and LLM-risk terms.

<!-- finish_text -->
# Finish text

That was the simulated <thing>. The full card breaks out the savings,
<card-specific topic>, and a prediction that's yours to test.

<!-- voice_check -->
> Voice rules — apply to every line above:
>
> - TO the visitor (you / your)
> - ABOUT the sims (named characters in third person)
> - Never narrate the page itself ("the visitor sees", "this card surfaces")
> - Never induce catastrophe-mindset
> - No italic markdown (no `*…*`, no `_…_`)
> - Bold (`**…**`) is OK on bullet labels and button names
> - Inline quotes use double quotes, not italic