Delete fabricated operator status writer

This commit is contained in:
Meta Vens 2026-07-12 22:00:20 +01:00
commit 60911fda96
9 changed files with 19 additions and 130 deletions

View file

@ -196,11 +196,13 @@ explicit bootstrap as a common preflight, nearly every run refreshed an
operator observation that no observer had produced.
Bootstrap now writes declaration/initialization state only and leaves operator
status absent. `epiphany-cultmesh-status write` is the explicit owner of the
positive operator-status path. The read loader returns `None` without opening
or creating a missing store, and the `read` CLI therefore reports `missing`
without filesystem mutation. Its smoke is fixed beneath `.epiphany-smoke` and
rejects every store override before creation.
status absent. The follow-up audit showed `epiphany-cultmesh-status write` was
not an observer: it had no production caller and hard-coded `status=ready` plus
doctrine fields from a template. The shipped binary is deleted, and its default
constructor/writer are test-only. The fixed CultMesh smoke no longer fabricates
operator status; it retains its separate source-JSON-derived operator snapshot
contract proof. Production keeps the typed operator-status schema and a
filesystem-pure reader for future genuine observed ingest.
## Agent-state projection body boundary

View file

@ -123,9 +123,10 @@
persisted loaders; only the daemon-ID-bounded publisher may lower templates
into provider-owned documents.
- Generic bootstrap owns declarations and initial control state, not operator
observation. Operator status remains absent until the dedicated status writer
publishes it. Missing reads do not create a CultCache store; status smoke is
fixed beneath `.epiphany-smoke`.
observation. The template-based operator-status writer binary is deleted and
its constructor/writer are test-only. Production retains the typed schema and
a filesystem-pure reader for genuinely observed future ingest; operator
snapshots remain source-artifact-derived documents.
- Agent-state SoA sync requires an existing bootstrapped Verse before mirroring
the persisted agent store. SoA report is filesystem-pure on a missing store.
Wrapper mode `agent-state-soa` explicitly composes sync then report; the

View file

@ -43,8 +43,9 @@ The confirmed conceptual substitutions have been cut:
Consumers can load persisted provider documents but cannot request seven
plausible advertisements/surfaces/tools from topology.
- bootstrap no longer writes default operator status. Only the dedicated
operator-status writer publishes it; missing reads are filesystem-pure and
the status smoke is fixed beneath `.epiphany-smoke`.
operator-status writer was then found to be a dead `ready` template and
deleted. Its constructor/writer are test-only; production retains typed
reading for genuine observed ingest and source-derived operator snapshots.
- agent-state SoA sync requires bootstrap; report preserves missing filesystem
state. The wrapper explicitly composes sync then report rather than hiding a
refresh inside readback.