A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2417
The landing page is a click-through story: an editorial hero and an evidence chain a visitor steps through
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- Give the homepage the editorial typography and the click-through interactivity of the prismatic case reports: a serif display hero and section heads, and an interactive evidence chain in the proof section — what the repository declares, what the registry generates, the interfaces it reaches, the rules a machine decides, the guaranteed claims, the executable use cases and what a recorded run supports — in which every node is a button that opens its figure, its sentence and its source, and every edge is solid where a machine holds the link and dashed where it is declared and awaits evidence.
- Why
- Owner order of 2026-10-11: the landing page should look and behave like the case reports (prismatic-platform cases, report v57): a serif display with an italic accent, a mono eyebrow, an ownership graph whose boxes and edges open what is known with links to the source, solid lines for recorded facts and dashed for inference. The homepage showed its evidence as static cards, and nothing on it could be stepped through.
- Now
- The hero and section heads are a sans display; the proof section shows claim counts as static cards; nothing on the homepage shows how a declaration reaches a recorded run, and no figure distinguishes what a machine holds from what is only declared.
- Wanted
- The hero title and every landing section head are set in the serif display, the subtitle italic in the brand colour, the eyebrow mono and tracked. The proof section opens with the evidence chain (site/templates/partials/evidence-chain.html): seven nodes in two lanes, every figure derived from the product model, the claims matrix and the catalogue, every node's sentence an existing derived or marketing.toml one, the last edge dashed while the evidence verdict supports fewer than the guaranteed claims. Without JavaScript every node's detail is shown in order; with it, Alpine shows the chosen one. The behaviour spec evidence-chain proves that choosing a node shows that node alone, pressed, with its figure. No graph runtime, no new script, no remote asset.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- Every node of the chain is a button; choosing one shows its detail alone and marks it pressed; the behaviour spec evidence-chain claims exactly those buttons
- Every figure in the chain is derived; the evidence edge is dashed while the supported count is below the guaranteed count
- scripts/ci/homepage-check, scripts/ci/interaction-check and scripts/site-check pass; the homepage stays within its asset budget
- At 390 px the page does not scroll horizontally and the chain stacks into one column
- Validation
bin/majordomus plan validatescripts/ci/interaction-checkscripts/ci/homepage-checkscripts/interaction-probe --only '/'- Evidence required
evidence_chain_interaction_probe- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
site/templates/index.htmlsite/templates/components.htmlsite/templates/partials/evidence-chain.htmlsite/data/marketing.tomlscripts/lib/interaction-specs/evidence-chain.mjs- Not
Chart.js or any charting runtime: the figure is markup and the homepage's budget is unchanged.A new homepage section: the chain sits inside the proof section homepage.toml already declares.Rewriting the copy: the only new sentence is the chain's legend in marketing.toml, within its budget.- Depends on
- none
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-11
- Updated
- 2026-10-11
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares site/templates/components.html with I2653; they may not run concurrently | majordomus plan validate |