I3223 — The homepage hero lets a visitor switch between recorded scenarios, each ending in the refusal it proves

○READY wave 1 · p2 · implementation profile · parallel safe

Part of a-visitor-understands-and-checks-majordomus — A first-time visitor of majordomus.dev understands what Majordomus does and can check every claim it makes.

Objective

Offer in the hero's left column, under the reassure line, a short list of links: the challenge as the default, described as refused and then accepted, and every use case that site/data/generated/terminal.json names among its refusals, each linking to its /use-cases/<id>/ page with at most its one derived verdict line, naming the homepage problem it answers, with the build's commit; homepage-check and case 333 hold it.

Why

On 2026-10-10 the owner asked for a friendlier, interactive, derived landing page with no big rewrite; ChatGPT proposed switchable real scenarios instead of one static terminal. The scenario corpus and replay already exist (I1600). Sources: chatgpt-majordomus:c215#8, chatgpt-majordomus:c137#5, chatgpt-majordomus:c134#3.

Current state

Verified on master 707a04c7ce8: site/templates/index.html links /challenge/ and does not inline a replay (only challenge.html includes partials/challenge-replay.html); site/data/homepage.toml holds html_bytes = 160000; terminal.json `refusals` lists every recorded lifecycle step that exited non-zero; committed derived data carries no commit (test/cases/51_derived_artifacts_committed.sh).

Desired state

scripts/generate-site-data writes the eligible choices from terminal.json; homepage-check refuses a choice without a recorded run, and holds the order and budget.

Scope

• site/templates/index.html
• scripts/generate-site-data
• scripts/ci/homepage-check

Out of scope

• A typed demo transcript
• A new homepage section

Dependencies

• I2417✓DONE The landing page is a click-through story: an editorial hero and an evidence chain a visitor steps through

What waits on this

• I3324✕BLOCKED After every deploy the published homepage's hero choices are probed and found reachable

Acceptance criteria

• Every offered scenario resolves to a recorded run
• Scripts off: every scenario is reachable
• homepage-check passes with the declared order and budget

Validation

• scripts/site-check
• scripts/ci/homepage-check
• bash test/run.sh 333_homepage_narrative

Evidence required

• homepage_check_scenarios

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3223.yaml. Read it back with majordomus plan show I3223.