Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2677

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

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
2
Waiting on
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI2672I2672 is not DONE
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2677

majordomus plan verify I2677

majordomus plan done I2677

What it is

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.
Now
Measured on master b29cf4e487 on 2026-10-13: the docs describe sharing between worktrees only.
Wanted
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.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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 validatemajordomus generate --checkscripts/pages current
Evidence required
docs_and_rule
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/BUILD_CACHE.md.ai/repo/rules/project/site/
Not
Private addresses in any public page
Depends on
Priority
p2
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-13
Updated
2026-10-13
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.