# CANONICAL_HubThread_LongitudinalDANOTES_Doc_051226 — CANDIDATE

**Filed:** 051226 · nest-routine-hubthread-sweeper · first-fire
**Status:** CANDIDATE — overnight GRAFT says this was canonized at Bridge `c22ef38` (not found in working tree)
**Source:** Overnight GRAFT 19e1b9a6effab949 · §V · "HUB-THREAD pattern canonized as longitudinal-substrate-spine"
**Cluster:** NEST substrate architecture · DANOTES pattern · HubThread

---

## WHAT THIS IS

The HUB-THREAD pattern — a longitudinal DANOTES email thread that functions as a spine for substrate routing, distinct from atomic Grafts.

The overnight GRAFT says this was canonized at Bridge `c22ef38` ("HUB-THREAD pattern canonized as longitudinal-substrate-spine (distinct from atomic Grafts)"). That commit does not exist in the current working tree. This candidate files the missing canon.

## SUBSTANCE (from overnight GRAFT and surrounding thread content)

**What a HUB-THREAD is:**
A DANOTES email thread that accumulates substrate across multiple sessions, multiple reply-messages, and multiple Dan-annotation instances. Unlike atomic Grafts (one crew member, one work-unit, one filing), a HUB-THREAD is longitudinal — it grows through Dan's pasted content, replies, and crew responses.

The DANOTES 050626_1 thread (`19e0087be1e80453` · 5 messages) is the exemplar:
- Dan pasted Trip conversation content: *"I'm just copy/pasting Trip's chat here because it's SO GOOD"*
- Dan added koan: *"Do you think Walking Stick know it's walking? /meta-dates"*
- Dan added enthusiasm: *"I am thoroughly entranced, Trip! ps Doc is probably replying already!"*
- Dan asked meta-question: *"How do you know Doc has done a Compaction? Actually asking, we're learning"*
- Dan pasted further substrate across multiple follow-up messages

This is not a single Graft. It is a HUB — a thread that Dan uses as both a message-relay AND a running substrate-accumulation channel.

**Distinction from atomic Graft:**
- Atomic Graft: one crew member → one addressed recipient → one work-unit checkpoint → one LAGOS filing
- HUB-THREAD: Dan as curator + relay → accumulates from multiple sources → longitudinal spine across days

**NEST-architectural role:**
HUB-THREADs are the DANOTES equivalent of what the Bridge's LOG folder is to commits — a substrate residence that spans sessions. This routine (nest-hubthread-sweeper) exists BECAUSE the HUB-THREAD pattern creates a substrate-accumulation surface that needs periodic sweeping.

**Overnight GRAFT connection:**
The overnight GRAFT names this pattern as what makes the new routine necessary: "Operationalizes the HUB-THREAD pattern named tonight." The routine sweeps HUB-THREADs for URLs AND Dan-notes tissue, integrating both as co-equal substrate.

## SOURCE VERIFICATION NEEDED

Credited to Bridge `c22ef38` which does not exist. Candidate files the missing canon.