Skip to content

I3224 — Every problem and every step on the homepage leads to the feature and evidence behind it, with the maturity the product model derives

Make the recognise section's problems and the how section's steps nodes that name the features answering them, derived and never declared (a problem's features are its domain's; a step's are the product.json features whose commands contain its lifecycle command), with those features' evidence and each feature's declared status and claims' evidence verdict; a step that no feature names is labelled as such.

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.

Ready. Every dependency is done, so majordomus plan start I3224 will be accepted.

Objective

Make the recognise section's problems and the how section's steps nodes that name the features answering them, derived and never declared (a problem's features are its domain's; a step's are the product.json features whose commands contain its lifecycle command), with those features' evidence and each feature's declared status and claims' evidence verdict; a step that no feature names is labelled as such.

Why

On 2026-10-12 ChatGPT proposed a clickable 'how it works' that never overclaims; the owner asked on 2026-10-10 for a project-oriented, click-through page. I2745 makes the page state no present it does not read; this extends that to the problem and step nodes. Sources: chatgpt-majordomus:c215#8, chatgpt-majordomus:c235#2.

Current state

Verified on master 707a04c7ce8: site/data/homepage.toml problems = [context, coordination, completion], each problem card links #domain-<id> on the map; the how section's steps link their recorded runs; feature status is stable, draft or deprecated (share/schemas/majordomus/feature/feature.v1.schema.json); site/data/registry/product.json carries features[].commands and evidence.claims.

Desired state

Node membership and labels are derived from site/data/registry/product.json, and homepage-check refuses a node without a feature and a label that is not the derived one.

Scope

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

Out of scope

  • New sections
  • Audience variants

Dependencies

Acceptance criteria

  • Every node links to at least one feature page and its evidence

Validation

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

Evidence required

  • homepage_check_node_maturity

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/I3224.yaml. Read it back with majordomus plan show I3224.

Searches the titles and descriptions of every page this site publishes.