Context
The first of the two named W2 wiring leaves from the graduated FM design-first record (D#15249 → #15254): the wake axis of the S2 telltale taxonomy. The STEP_BACK verified at source (three independent sweeps: fleet-service grep, DTO assembly check, ai/-wide field-name sweep — zero hits) that no read/observe producer exists: the daemon toggles are CONTROL state; the roster DTO carries no wake observation fields. Until this leaf lands, the telltale UI renders the axis as unknown — the honest default the record mandates.
The Problem
TODAY's lived incident: the operator hand-disabled the wake daemon and the cockpit showed nothing. #14537 (setWakeEnabled) is the WRITE verb — a toggle without an observable state is a blind switch; the record explicitly rules #14537 write-adjacency, never the telltale's evidence source.
The Architectural Reality
- The graduated taxonomy (binding):
wake: on | off | suppressed | unknown — one of two ORTHOGONAL axes (throttle is the sibling leaf). Honest-degradation rule: unknown renders as unknown, never as healthy.
- The producer feeds the roster/detail DTO assembly (the projection surface the cockpit binds) — observation read from wherever wake-subscription truth lives (daemon state / wake-subscription liveness), never inferred from control intent.
- Placement per the D#15209 ledger default: wiring → #13015.
Acceptance Criteria
Out of Scope
The throttle axis (sibling leaf) · the telltale UI (renders both axes; separate leaf under #14560) · #14537 itself.
Related
Epic #13015 (parent) · D#15249 (graduated record, OQ-S2.3 amended resolution) · #15254 (registry: the taxonomy table) · #14537 (write adjacency).
Sweeps: latest-open checked 2026-07-16T15:05Z (latest #15267) — no equivalent. A2A herd-window clean.
Origin Session ID: b42c5667-db78-4a0c-83a0-ce66c95ee0d9
Retrieval Hint: "fleet wake-state read producer roster DTO telltale axis"
Context
The first of the two named W2 wiring leaves from the graduated FM design-first record (D#15249 → #15254): the wake axis of the S2 telltale taxonomy. The STEP_BACK verified at source (three independent sweeps: fleet-service grep, DTO assembly check, ai/-wide field-name sweep — zero hits) that no read/observe producer exists: the daemon toggles are CONTROL state; the roster DTO carries no wake observation fields. Until this leaf lands, the telltale UI renders the axis as
unknown— the honest default the record mandates.The Problem
TODAY's lived incident: the operator hand-disabled the wake daemon and the cockpit showed nothing. #14537 (
setWakeEnabled) is the WRITE verb — a toggle without an observable state is a blind switch; the record explicitly rules #14537 write-adjacency, never the telltale's evidence source.The Architectural Reality
wake: on | off | suppressed | unknown— one of two ORTHOGONAL axes (throttle is the sibling leaf). Honest-degradation rule: unknown renders as unknown, never as healthy.Acceptance Criteria
unknown(fail-honest, never a default-to-on).Out of Scope
The throttle axis (sibling leaf) · the telltale UI (renders both axes; separate leaf under #14560) · #14537 itself.
Related
Epic #13015 (parent) · D#15249 (graduated record, OQ-S2.3 amended resolution) · #15254 (registry: the taxonomy table) · #14537 (write adjacency).
Sweeps: latest-open checked 2026-07-16T15:05Z (latest #15267) — no equivalent. A2A herd-window clean.
Origin Session ID: b42c5667-db78-4a0c-83a0-ce66c95ee0d9 Retrieval Hint: "fleet wake-state read producer roster DTO telltale axis"