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

I2671

A provider offers its cache as a signed, expiring mesh record, and a stopped provider goes stale

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
development-runtime
Milestone status
ACTIVE
Wave
1
Waiting on
I2670
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI2670I2670 is not DONE

Moves

plan.transition
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 I2671

majordomus plan verify I2671

majordomus plan done I2671

What it is

Objective
Let a node publish its offer through the mesh journal so peers discover it without a committed endpoint, and let the offer expire when the provider stops.
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 advertisement datagram carries transports only and is size-bound; no generic service event exists in the journal.
Wanted
A signed service record kind in the journal with a lifetime shorter than a few heartbeats, refreshed only while the provider's own health probe passes, replayed and expired by the existing liveness rules.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • A peer sees an offer within one heartbeat of the provider becoming healthy
  • The offer is stale within its lifetime after the provider stops
  • A record from a key that is not trusted is not an offer (mesh-is-observation-not-authority)
  • The record carries no secret
Validation
bin/majordomus plan validateMJ_TEST_JOBS=2 bash test/run.sh 3013_a_mesh_build_cache
Evidence required
offer_discovery_caseoffer_expiry_case
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/mesh/docs/MESH.md
Not
Provisioning the store: I2674
Depends on
I2670
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.