I2677 — The build cache is documented, governed by a rule and described on the site and the Pages

✕BLOCKED wave 2 · p2 · implementation profile · runs alone

Part of development-runtime — The runtime has a development surface.

Objective

Say once, derived, what the cache is, how a node offers and uses it and how to see it, on the handbook, the site and the landing's account of how the cluster compiles.

Why

The owner, 2026-10-13, with full clearance: set up MinIO, an sccache server and every mesh node, verified and validated. The cluster compiles the same Rust on every machine from a cold cache; two declared offload hosts were under their disk minimum that day. See ADR 0157.

Current state

Measured on master b29cf4e487 on 2026-10-13: the docs describe sharing between worktrees only.

Desired state

docs/BUILD_CACHE.md, a project rule that a build never depends on the cache, the site page and the Pages, all generated from the canonical model and rule.

Scope

• docs/BUILD_CACHE.md
• .ai/repo/rules/project/
• site/

Out of scope

• Private addresses in any public page

Dependencies

• I2672✕BLOCKED The offers and the selection are one read, projected to CLI, MCP, HTTP and OpenAPI

Acceptance criteria

• Public pages carry no private address or key
• The rule is enforced by the case of I2676
• majordomus generate --check and scripts/pages current are clean

Validation

• bin/majordomus plan validate
• majordomus generate --check
• scripts/pages current

Evidence required

• docs_and_rule

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