I3396 — A documented command adds a criterion to a proposed intent, and the getting-started page shows the path from a proposal to a satisfied verdict

✕BLOCKED wave 1 · p1 · implementation profile · parallel safe

Part of a-newcomer-reaches-a-first-verified-intent — A newcomer reaches an intent whose verdict is satisfied, in a repository of their own, using only what the getting-started page shows.

Objective

Add a writing capability intents.criterion (CLI majordomus intent criterion <id> --criterion <text> --verify <name>) that adds one criterion to an existing intent record, refusing an unknown intent, a duplicate id or an unresolvable reference, and writing the file whole or not at all. Add a step to site/templates/getting-started.html between adding Majordomus and the first task: propose an intent, add its criterion, record the verification, read intent explain. Add the same path to docs/ADOPTION.md. Extend case 2978 for the writer.

Why

T6 of the owner's report of 2026-10-19. intents.propose deliberately writes no criterion (ADR 0144) and no command adds one, so a newcomer would hand-edit YAML; a separate writer keeps the proposal rule and removes the archaeology.

Current state

apps/majordomus-cli/src/capability/builtin/intents.rs:15 says intents.propose is the one writer and :590 that it records no criterion; site/templates/getting-started.html:10-32 shows five steps and no intent; grep -n intent docs/ADOPTION.md returns nothing.

Desired state

The getting-started page and docs/ADOPTION.md show the path; the writer is served on CLI, HTTP and MCP.

Scope

• apps/majordomus-cli/src/capability/builtin/intents.rs
• apps/majordomus-cli/src/commands/intent.rs
• apps/majordomus-cli/tests/intent.rs
• test/cases/2978_an_intent_is_proposed_by_a_capability.sh
• site/templates/getting-started.html
• site/content/getting-started.md
• docs/ADOPTION.md
• docs/generated/cli.json
• docs/generated/cli.md
• docs/generated/cli.yaml
• docs/generated/openapi.json
• docs/generated/openapi.yaml
• docs/generated/registry.json
• docs/generated/registry.yaml
• .ai/repo/mcp-tool-run-baseline.txt

Out of scope

• Planning milestones from the page
• Changing intents.propose

Dependencies

• I3395○READY An intent criterion can cite a verification the repository's profile declares, and a recorded passing run of it at the current tree makes the criterion current

What waits on this

• I3397✕BLOCKED install-check's first-intent stage reaches a satisfied verdict in a named repository with only the getting-started commands, and counts the doctrine its output exposes
• I3398✕BLOCKED The T6 protocol says who counts as a newcomer, what each trial records and how many must reach a satisfied verdict unaided, before any trial runs

Acceptance criteria

• The writer adds one criterion and refuses each invalid input, writing nothing on refusal
• Every command the new getting-started step shows exists in the CLI reference
• Case 2978 covers the writer
• scripts/site-check passes

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test intent
• bash test/run.sh 2978_an_intent_is_proposed_by_a_capability
• majordomus generate --check
• scripts/site-build
• scripts/site-check

Evidence required

• test_intent_criterion_writer
• site_getting_started_shows_first_intent

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