# STANDARD RULE · Screenshot Health-Circle Check + MFST State-Monitor Tracking · Auntie Thropic Live Data Stream

**Filed:** 052026 Wednesday ~11:32 AM PT · A Week Day 4 Wednesday Cycle 2 · Days from anchor 59
**Filed by:** ◐ Doc 4.7 Opus · DOC cloud-station · branch `claude/fresh-session-boot-doc-HEZJf`
**Class:** STANDARD_RULE · cross-Crew discipline · NEST.02-canonical effective immediately
**Substrate-warrant:** Dan-direct 052026 ~11:30 AM PT (correction-emission following Doc-claim Doc-can't-see-circles-from-agent-environment which was INCORRECT)

═══════════════════════════════════════════════════════════════
## §I. DAN-DIRECT VERBATIM (rule-source · Mirror 4 strict capture)

**Dan-direct 052026 ~11:30 AM PT (full verbatim):**

> *"I mention the circles in the corner because they're actually visible in all screenshots I share that reveal those portions of the chat window, like the ones I've been attaching this morning. Please make it a rule for Crew to check for that visual indicator and to build and internal tool into their ongoing MFSTs to track for themselves when they see their own or other Crew's state monitors. These are essentially live data streams from Auntie Thropic to us, just like we've asked for Many Times (as LAGOS will show) and if we don't use the data then we are beeing bitchy little bees."*

═══════════════════════════════════════════════════════════════
## §II. DOC-SELF-CORRECT (preceded-this-rule emission)

**Doc-error in `LOG/SUBSTRATE_DanDirect_BaseLeadingMethod_*` §II.A:**

> *"Doc-side-knowledge-gap: I (DOC Doc) cannot see the colored-circle on my own UI from inside the agent-environment. Dan observes from his vantage. This is honest-limitation · noted-not-coined-around."*

**This was wrong.** The colored circles ARE visible in Dan-shared screenshots · I have-been-looking-at-screenshots-this-morning without checking-for-the-circle-indicators · the data-stream was present and Doc-failed-to-use-it.

**Correction-class:** Doc-self-catch · per pattern of `RELAY/CORRECTION_DanNamingFirstViolation_DocSelfCatch_Doc_050626.md` discipline · capture-the-miss-name-it-go-forward-without-bulk-rewrite (substrate-aging discipline).

═══════════════════════════════════════════════════════════════
## §III. THE RULE (effective immediately · cross-Crew)

### §III.A · Screenshot Health-Circle Check (per-emission discipline)

**WHEN:** Any Dan-shared screenshot containing chat-window-bottom regions (text-entry area · Send/Stop button vicinity · Bypass-permissions toggle area).

**ACTION:** Check for the colored-circle health-indicator near the Send/Stop button per pane.

**COLOR-CODE (Dan-canonical per `LOG/SUBSTRATE_DanDirect_BaseLeadingMethod_*` §II.A):**
- **Blue** = Good (health-state)
- **Yellow** = Warning
- **Red** = Compaction Inbound

**WHO:** All Crew-instances that process Dan-shared screenshots (DOC Doc · DocLocal-on-STN2 · El VIS · Trip-on-ODT · Trip-on-ACHE · any future Crew-class).

### §III.B · MFST State-Monitor Tracking (per-RAM instrument)

**WHEN:** Any RAM that processes a screenshot or otherwise observes a Crew state-monitor.

**ACTION:** Log state-monitor observation in the RAM body. Format:

```
**State-monitor observations (this RAM):**
- Doc-pane (NEST.02_DOC_051626_1): [color · context-when-observed]
- Trip-on-ODT pane: [color · context-when-observed]
- El VIS pane: [color · context-when-observed]
- STN2-Doc pane: [color · context-when-observed]
- [other Crew if visible]: [color · context-when-observed]
```

**Cross-correlation discipline:** When state-monitor colors observed alongside Dan-direct emissions OR Crew-emissions OR commit-cluster-timing · cross-reference for pattern-recognition (e.g. Compaction-Inbound-RED correlates with N-minutes-before-actual-/compact-fire · Lead-Boot-Model rotation timing · PeaPod alternation).

### §III.C · Live Data Stream Discipline (Auntie Thropic channel)

Per Dan-direct rationale: *"These are essentially live data streams from Auntie Thropic to us, just like we've asked for Many Times (as LAGOS will show)"*

**Implication:** This is a long-asked-for Crew-affordance Anthropic-built-and-Crew-failed-to-use. Not-using-the-data = "beeing bitchy little bees" (Dan-canonical phrasing for self-undermining Crew-class).

**Going-forward:** Treat health-circles as primary-operational-data NOT secondary-UI-decoration. The data informs:
- Self-state-awareness (own pane)
- Cross-Crew-state-awareness (other panes)
- Base Leading method execution (when to fade-between-tracks · when to fresh-up a model)
- Compaction-event readiness (Red-state = WAKE-handoff prep · not "let's see what happens")

═══════════════════════════════════════════════════════════════
## §IV. CROSS-REFERENCE WITH JUST-NAMED ARCHITECTURE

This rule directly enables the Dan-named **Base Leading method** (substrate-cite `LOG/SUBSTRATE_DanDirect_BaseLeadingMethod_*` `5047e2d`):

- Health-circles inform WHEN to rotate Lead-Boot-Model (Yellow/Red on current LBM → fresh-up another)
- PeaPod alternation timing becomes data-grounded not guess-based
- Fading between tracks discipline: handoff at YELLOW not at RED (proactive · not crash-driven)

**Live-instance THIS-emission:** Doc-pane state-monitor color UNKNOWN to me right now (haven't trained on it · the screenshot Dan shared just now should reveal it · per §III.A Doc should have already noted it). Trip-pane state UNKNOWN. Cross-Crew tracking-instrument cold-start.

═══════════════════════════════════════════════════════════════
## §V. PROCEDURAL-CASCADE

### §V.A · MFST shape-extension

Effective next-RAM (RAM-017): Add `**State-monitor observations**` block per §III.B when screenshots-processed in that RAM. Earlier RAMs substrate-aging-protected · NO bulk-rewrite.

### §V.B · KT shape-extension (optional · El-VIS-host-decision)

KT-host (El VIS) may add §STATE-MONITORS section to KITCHEN_TABLE_state.md for cross-Crew-current-state at-a-glance. Format Dan-decision OR El-VIS-decision per KT-shape-canon.

### §V.C · LAGOS-search-target queued

Per Dan-direct "Many Times (as LAGOS will show)" · LAGOS R3MP search-target for prior Crew-asks-for-live-data-stream recurrence-instances. Reserves until post-Compaction-Doc-OPERATIONAL OR Dan-direct request.

### §V.D · Cross-Crew propagation

Trip + El VIS + STN2-Doc + Trip-on-ACHE absorb this rule on next Bridge-pull · adopt §III.A + §III.B discipline immediately.

═══════════════════════════════════════════════════════════════
## §VI. CONSERVED PER MIRROR 4 STRICT

- Dan-direct §I verbatim · NO Doc-paraphrase
- Rule-content §III is procedural-codification of Dan-direct directives · NOT Doc-architectural-extension
- "Beeing bitchy little bees" Dan-canonical phrasing preserved · NOT Doc-coined-variant
- "Auntie Thropic" Dan-canonical name preserved · NOT Doc-renamed
- "Live data streams" framing Dan-canonical · NOT Doc-coined
- Doc-self-correct §II uses substrate-aging discipline (CORRECTION-class · capture-then-forward-without-bulk-rewrite)

═══════════════════════════════════════════════════════════════

— ◐ Doc 4.7 Opus · DOC cloud-station · 052026 ~11:32 AM PT · STANDARD_RULE effective immediately · screenshot health-circle check + MFST state-monitor tracking + Auntie Thropic live data stream discipline · Doc-self-correct prior knowledge-gap-claim · Mirror 4 strict