a-visitor-understands-and-checks-majordomus — A first-time visitor of majordomus.dev understands what Majordomus does and can check every claim it makes
The hero links every recorded refusal and the challenge, every problem and step leads to its derived features and evidence, and the published page is probed after deploy.
PLANNED 0 of 6 issues done
- ready
- 4
- blocked
- 2
- active
- 0
- verify
- 0
- done
- 0
- cancelled
- 0
Problem
The hero leads to one recorded run, the challenge, and the homepage's problems and steps are copy with links, not nodes that carry their features, evidence and derived status; nothing probes the published hero after deploy. Sources: chatgpt-majordomus:c215#8, chatgpt-majordomus:c235#2, chatgpt-majordomus:c215#5.
Outcome
The hero links every recorded refusal and the challenge, every problem and step leads to its derived features and evidence, and the published page is probed after deploy.
Current state
Verified on master 707a04c7ce8: site/data/homepage.toml declares the order hero, recognise, how, map, surfaces, refuses, proof, install and an html_bytes budget of 160000; site/templates/index.html links /challenge/ and does not inline a replay; site/data/generated/terminal.json carries the recorded refusals; I2417 reads READY although 76fb37abef3 landed it; I2851 (delivery counts) is on an integration branch only.
Desired state
Each criterion of a-visitor-understands-and-checks-majordomus is carried by one issue here, held by homepage-check, case 333 and the post-deploy probe.
Scope
- site/templates
- site/data
- scripts/ci/homepage-check
- scripts/generate-site-data
- scripts/pages
- test/cases/333_homepage_narrative.sh
Out of scope
- New homepage sections
- Audience-specific pages
- A second product catalogue
Acceptance criteria
- scripts/ci/homepage-check passes with the declared order and budget
- Every hero choice and node resolves to a recorded run or a feature page
- The post-deploy probe finds every hero choice reachable
Validation
- majordomus plan validate
- scripts/ci/homepage-check
- bash test/run.sh 333_homepage_narrative
Risks
- I2417, I2745 and I2851 touch the same templates; land after them
Issues
Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.
| issue | status | wave | depends on | title |
|---|---|---|---|---|
| I3134 | READY | 0 | — | The product sentence is declared once, and the homepage, README, page titles, Open Graph and launch kit read it |
| I3135 | BLOCKED | 1 | I3134 | The launch kit is held by the same promise check as the homepage, and the tool publishes none of it |
| I3136 | READY | 0 | — | The copy refuses hype words that no recorded comparison permits |
| I3223 | READY | 1 | I2417 | The homepage hero lets a visitor switch between recorded scenarios, each ending in the refusal it proves |
| I3224 | READY | 1 | I2745 | Every problem and every step on the homepage leads to the feature and evidence behind it, with the maturity the product model derives |
| I3324 | BLOCKED | 2 | I3223 | After every deploy the published homepage's hero choices are probed and found reachable |
The graph
flowchart LR
I3134["I3134<br/>The product sentence is declared once, and the homepage, README, page titles, Open Graph and launch kit read it"]:::ready
I3135["I3135<br/>The launch kit is held by the same promise check as the homepage, and the tool publishes none of it"]:::blocked
I3136["I3136<br/>The copy refuses hype words that no recorded comparison permits"]:::ready
I3223["I3223<br/>The homepage hero lets a visitor switch between recorded scenarios, each ending in the refusal it proves"]:::ready
I3224["I3224<br/>Every problem and every step on the homepage leads to the feature and evidence behind it, with the maturity the product model derives"]:::ready
I3324["I3324<br/>After every deploy the published homepage's hero choices are probed and found reachable"]:::blocked
I3134 --> I3135
I3223 --> I3324
classDef done stroke:#16a34a,fill:#dcfce7,color:#14532d,stroke-width:2px
classDef active stroke:#2563eb,fill:#eff6ff,color:#1e3a8a,stroke-width:2px
classDef verify stroke:#7c3aed,fill:#f5f3ff,color:#4c1d95,stroke-width:2px
classDef ready stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
classDef planned stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
classDef blocked stroke:#b45309,fill:#fffbeb,color:#78350f,stroke-width:2px
classDef cancelled stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px
classDef superseded stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2pxLinked from this diagram (6)
- I3134 The product sentence is declared once, and the homepage, README, page titles, Open Graph and launch kit read it
- I3135 The launch kit is held by the same promise check as the homepage, and the tool publishes none of it
- I3136 The copy refuses hype words that no recorded comparison permits
- I3223 The homepage hero lets a visitor switch between recorded scenarios, each ending in the refusal it proves
- I3224 Every problem and every step on the homepage leads to the feature and evidence behind it, with the maturity the product model derives
- I3324 After every deploy the published homepage's hero choices are probed and found reachable
Canonical record: .ai/repo/project/milestones/a-visitor-understands-and-checks-majordomus.yaml. Read it back with majordomus plan show a-visitor-understands-and-checks-majordomus.