I3136 — The copy refuses hype words that no recorded comparison permits

○READY wave 0 · 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

Add to site/data/homepage.toml [promises] the words the positioning work ruled out (revolutionary, revolutionize, 10x, next-generation, AI-powered orchestration, unlock, transform), each \"\" until a claim permits it, so homepage-check refuses them in the copy files it reads.

Why

The 2026-10-10 and 10-13 positioning work ruled out vague AI-platform words and comparative speed claims without evidence; the promise vocabulary today covers only autonomy words. Sources: chatgpt-majordomus:c250#5, chatgpt-majordomus:c218#3.

Current state

site/data/homepage.toml [promises] lists unattended, autonomous, fully automated, self-healing, zero-touch, hands-off and merge/release automation words.

Desired state

The listed words are refused while no claim permits them; a case or homepage-check fixture holds one of them.

Scope

• site/data/homepage.toml
• scripts/ci/homepage-check

Out of scope

• Words in docs other than the copy files the check reads

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• homepage-check fails when marketing.toml uses one of the new words
• The current copy passes

Validation

• scripts/ci/homepage-check

Evidence required

• promise_words_refused

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