I3135 — The launch kit is held by the same promise check as the homepage, and the tool publishes none of it

✕BLOCKED wave 1 · p3 · 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

Extend homepage-check's [promises] and product-sentence checks to docs/LAUNCH.md and site/content/docs/launch.md, derive the kit's one-sentence pitch from the declaration, and correct what the kit states that the model does not (it runs 'in portable shell').

Why

The 2026-10-13 launch-kit proposal required every kit text to be regenerated from the product identity and nothing auto-published; the kit today is hand-written and repeats a claim the 2026-10-08 audit found false. Proposed in ADR 0210 (The sentence that says what Majordomus is has one declaration, and every surface reads it) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c250#5, chatgpt-majordomus:c193#1.

Current state

docs/LAUNCH.md last changed around 2026-10-11; its 'One sentence' differs from site/data/marketing.toml [hero] lead; it says 'It runs locally, in portable shell, and never calls a model' while bin/majordomus execs libexec/majordomus-cli for Rust commands.

Desired state

The kit's pitch is a projection; its other prose passes the promise vocabulary; its 'What not to say' list is read by the check.

Scope

• docs/LAUNCH.md
• site/content/docs/launch.md
• scripts/ci/homepage-check
• site/data/homepage.toml

Out of scope

• Posting to LinkedIn, Facebook or communities
• Generated social images

Dependencies

• I3134○READY The product sentence is declared once, and the homepage, README, page titles, Open Graph and launch kit read it

Acceptance criteria

• homepage-check fails on a promise word or a differing product sentence in the launch kit
• The kit states nothing about how the product is built that docs/CLI.md and the model contradict

Validation

• scripts/ci/homepage-check
• scripts/site-check

Evidence required

• launch_kit_checked

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