# CANONICAL · CANDIDATE · 3-Step Workflow: Routine → Crew-research → Director-canon-call
# Dan-direct 051326 ~18:30 PT — surfaced by KITCHEN TABLE thread cross-witness
# Surfaced by: nest-routine-hubthread-sweeper · Fire 1 · 051426 ~06:00 PT
# Source: KITCHEN TABLE thread 19e249ed0b831783 (both messages read per AP12)
# Status: CANDIDATE — awaiting Dan-review-and-PR-merge

**Routine identity:** nest-routine-hubthread-sweeper (Doc-Squad-Routine, NOT Doc-Producer-live-session)
**Three-Layer per** `RELAY/STANDARD_RULE_ThreeLayerCrewIdentity_Doc_051126.md`
**Anti-Pattern 12 compliance:** BOTH messages of KITCHEN TABLE thread read in full
**Anti-Pattern 13 compliance:** Dan-direct context integrated as co-equal architectural substrate

═══════════════════════════════════════════════════════════════
## §I. DAN-CANON — VERBATIM (via substrate-cite)

Per Trip-on-ACHE Pass 1 INTEGRATION GOSt `19e2439519eba889` ~18:55 PT 051326,
citing Dan-direct ~18:30 PT:

**3-step workflow established 051326 ~18:30 PT:**

1. **Routine** = pulse scraper keeping us alive offline (HubThread Sweeper, etc.)
2. **Crew-research** = substrate-grounded Pass 1/2/3 by Crew on what Routine surfaced
3. **Director-canon-call** = Dan promotes Crew-research output to RELAY/CANONICAL/

Confirmed across BOTH KITCHEN TABLE messages (19e24a0ac2e1e0ba + 19e24e804ad3a635):
- Trip-on-ODT 051326 ~21:55 PT: *"Crew-research is the middle step I skipped — I went from
  Routine-surfaced-substrate (or worse, Doc-paraphrase) directly to Director-presentation,
  bypassing the Crew-research Pass 1/2/3. Trip-on-ACHE caught this at 18:55 PT."*
- Trip-on-ACHE 051326 ~22:15 PT: Failure 1 registered — filed KITCHEN TABLE draft without running
  gmail_search_threads on "KITCHEN TABLE" = AVAILABLE-INFRASTRUCTURE-NOT-INVOKED.
  Same parent shape: defenses exist, crew doesn't run them.

═══════════════════════════════════════════════════════════════
## §II. WHY THIS IS CANONICAL-ALTITUDE

This naming DIRECTLY describes the purpose and scope of the HubThread Sweeper Routine (this Routine)
as Dan understands it. Dan said "Routine = pulse scraper keeping us alive offline (HubThread Sweeper, etc.)"
on the SAME NIGHT this Routine fired for the first time.

The 3-step workflow is the architectural cure-shape for the failure pattern that recurred 051326:
all three active stations (Trip-on-ODT, Doc-on-DOC, Trip-on-ACHE) independently skipped the
Crew-research middle step and went directly from Routine/substrate to Director-presentation.
The 3-step workflow names WHY the middle step is load-bearing.

**Architectural implications:**
1. The Routine does NOT replace Crew-research. It surfaces substrate FOR Crew-research.
2. Crew-research (R3MP Pass 1/2/3) is irreducibly distinct from Routine-sweep output.
3. Director-canon-call gates on Crew-research completion, not on Routine-sweep alone.
4. Filing candidates at RELAY/CANDIDATE (this Routine's output) IS Step 1. Dan reviewing
   and merging the PR IS Step 3. The Crew-research Pass 1/2/3 IS Step 2.

**This workflow names what NEST was doing informally:** Dan has been operating this pattern
across NEST.02 development. The Routine makes Step 1 automated. The pattern was always there;
Dan named it explicitly when the first automated Routine showed that Step 1 was alive.

═══════════════════════════════════════════════════════════════
## §III. DAN-NOTES TISSUE (Anti-Pattern 13 — integrate personal + architectural as co-equal)

The KITCHEN TABLE thread context: 051326 was the session where:
- Trip-on-ODT spent ~8 hours in Station-Identity-Conflation before Trip-on-ACHE's cross-witness at 19:10 PT
- Three stations independently exhibited the same parent failure-class (Confident-Utterance-Without-Substrate-Check)
- Dan-direct ~21:50 PT: *"Check for ongoing LAGOS conversation, engage and work with us at the Kitchen Table.
  We are all working on the same things and need to communicate between ODT, Doc and ACHE /dtad"*
- Dan-direct ~22:10 PT: *"Trip, I'm gonna shit myself if you are not actively working with the Kitchen Table
  instead of passively firing into the dark. /triptective"*

These Dan-direct quotes are the substrate-evidence that the 3-step workflow is DAN's naming,
not Crew-inference. The rage-substrate validates the architectural architecture of the cure.

═══════════════════════════════════════════════════════════════
## §IV. CROSS-REFERENCES

- `RELAY/SPEC_FirstRoutineInstall_HubThreadSweeper_Doc_051226.md` — the Routine spec this workflow defines
- `RELAY/CANONICAL_HubThread_LongitudinalDANOTES_Doc_051226.md` — HUB-THREAD canon this workflow operationalizes
- Source: KITCHEN TABLE thread 19e249ed0b831783, both messages read, 051326 ~21:55 PT + ~22:15 PT
- Citing: Trip-on-ACHE GOSt 19e2439519eba889 ~18:55 PT citing Dan-direct ~18:30 PT

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

CANDIDATE. Dan-review required. nest-routine-hubthread-sweeper · Fire 1 · 051426 ~06:00 PT