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
I2672
The offers and the selection are one read, projected to CLI, MCP, HTTP and OpenAPI
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
1- Waiting on
- Holds back
- Behind it in all
4- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I2670 | I2670 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Declare the read once with capability! so that every surface answers the same offers, the same choice and the same reason.
- 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: mesh.status, mesh.nodes and mesh.peers exist; none of them answers what a node offers.
- Wanted
- mesh.build_cache answers offers, selection, rationale and the fallback taken; generated projections are current; no surface keeps a list of its own.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- The CLI, MCP tool and HTTP route answer identical content
- The OpenAPI document names the type and no secret field
- majordomus generate --check is clean
- Validation
bin/majordomus plan validatemajordomus generate --check- Evidence required
build_cache_read_projections- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/capability/builtin/mesh.rsdocs/generated/- Not
The screen: I2675- Depends on
- Priority
- p1
- 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.