I3918 — README, CONTRIBUTING and the homepage say truthfully how big the tool is and what its registry counts are
README.md and CONTRIBUTING.md stop saying the tool needs bash 3.2 and nothing else: they say that the shell tool is small and portable and hands every other command to the Rust executable it ships, prebuilt. The homepage's surfaces section (index.html:328-332) says what its numbers are: the capabilities are the builtin ones plus one generated resource per object of the layer (208 plus 3092 at 2026-10-22), and the MCP tools and HTTP routes are those builtin capabilities projected, so a reader does not read a small tool and a 3300-capability platform as a contradiction.
READY wave 0 · p1 · implementation profile · runs alone
Ready. Every dependency is done, so majordomus plan start I3918 will be accepted.
Objective
README.md and CONTRIBUTING.md stop saying the tool needs bash 3.2 and nothing else: they say that the shell tool is small and portable and hands every other command to the Rust executable it ships, prebuilt. The homepage's surfaces section (index.html:328-332) says what its numbers are: the capabilities are the builtin ones plus one generated resource per object of the layer (208 plus 3092 at 2026-10-22), and the MCP tools and HTTP routes are those builtin capabilities projected, so a reader does not read a small tool and a 3300-capability platform as a contradiction.
Why
On 2026-10-22 an outside reviewer found the size contradictory and not credible: CONTRIBUTING.md:3 says small on purpose, README.md:129 says bash 3.2 or newer, git and sha256sum or openssl, nothing else, while the homepage shows 3300 capabilities, 197 MCP tools, 202 HTTP routes and a Rust executable. bin/majordomus:96-113 hands every command it does not know to the Rust majordomus-cli, and mcp, serve, generate and worktree exist only there. The owner chose to explain the registry figures.
Current state
README.md:129 and CONTRIBUTING.md:3,36 as quoted; product.json telemetry counts 3300 capabilities as 208 builtin and 3092 declarative, one per object (site.rs:1247-1260).
Desired state
README and CONTRIBUTING state the Rust executable as a requirement of every command beyond the shell tool's own; the surfaces section names builtin capabilities and generated resources apart, each from the dataset, and site-check holds both figures.
Scope
- README.md
- CONTRIBUTING.md
- site/templates/index.html
- site/data/marketing.toml
- scripts/site-check
- .ai/repo/project/issues/I3918.yaml
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- No tracked document says the tool needs bash and nothing else
- The homepage names builtin capabilities and generated resources apart, each from the dataset
- site-check fails when either figure disagrees with the dataset
Validation
- bin/majordomus plan validate
- scripts/site-check
Evidence required
- size_said_truthfully
- registry_figures_explained
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/I3918.yaml. Read it back with majordomus plan show I3918.