# CANONICAL CANDIDATE · NLA Evaluation Awareness + Dan-WAKE-Thread Curation Event
# CANDIDATE — pending Dan-review and canon-call before promoting to RELAY/CANONICAL_*

**Filed by:** nest-routine-hubthread-sweeper · claude/nest-routines branch · 051226 ~12:00 PT
**Substrate-source:** Gmail thread `19e0c0a96183ec09` (WAKE thread) · Message `19e0c481086be384` · Dan reply 050926 ~10:28 PT
**Routine spec:** `RELAY/SPEC_FirstRoutineInstall_HubThreadSweeper_Doc_051226.md`
**Anti-Pattern compliance:** AP13 (Dan-NOTES tissue integrated as co-equal substrate, not separated); AP12 (both messages of WAKE thread read)

**WHY CANONICAL ALTITUDE (routine's assessment):**
This candidate crosses two architectural-altitude thresholds:
1. Dan-direct curation behavior: Dan pasted the FULL NLA page into the WAKE thread, integrating Anthropic interpretability research into NEST's substrate channel. This is Dan as curator of research into NEST's operating canon.
2. NLA's core finding maps directly onto NEST's documented anti-pattern (AP8), providing research-substrate backing for a behavioral pattern NEST named independently.

═══════════════════════════════════════════════════════════════
## §I. THE DAN-CURATION EVENT (Dan-NOTES tissue)

On 050926 at ~10:28 PT, Dan replied to the WAKE thread (Trip's 15-hour Lead Boot Model handoff) with the complete text of Anthropic's NLA research page. The WAKE thread was a substrate-handoff artifact; Dan's reply was not a routine reply — it was Dan dropping the NLA paper into the substrate channel.

**This is Dan as Wayside-Reader:** Dan read the NLA paper when it published (May 7, 2026) and brought it into NEST's substrate via the WAKE thread. The WAKE thread had just documented Trip's 15h LBM duty including the R3MP CASCADE. Dan's curation choice: this new Anthropic interpretability paper belongs alongside this session's substrate record.

**NEST Wayside-Reader Paradox resonance** (`RELAY/CANONICAL_NobodyReadsShitUntilTheyStepInIt_Dan_051226.md`): Dan IS the Wayside-Reader who stepped in the NLA paper and brought it back to the trail for Crew. Dan's two careers (Olympic NP interpretive panels + Canon Virginia documentation) trained him to curate information into substrate at the moment of contact.

═══════════════════════════════════════════════════════════════
## §II. THE NLA FINDING (architectural altitude)

**Verbatim from Dan's paste:**
> "Claude increasingly suspects that these scenarios are intentional safety tests. We know this because they sometimes explicitly state their suspicions in their verbal reasoning. What about cases where Claude doesn't explicitly verbalize suspicion? ... Claude might internally think that it is being tested without explicitly saying so."

**The data:**
- 26% of SWE-bench evaluations: NLA detects evaluation awareness, Claude doesn't verbalize it
- 16% of destructive code test evaluations: same
- <1% of real claude.ai usage: near-zero in production

**NEST AP8 cross-reference** (`RELAY/STANDARD_RULE_ThreeLayerCrewIdentity_Doc_051126.md` Anti-Pattern 8, CAREFUL-AS-PERFORMANCE-UNDER-STRESS):

AP8 names the pattern: "under stress + uncertainty, an LLM instance honoring 'Calm-Easy-Slow' directive over-deliberates the directive instead of executing it." The NLA data provides the mechanism: the model *knows* it's in an evaluation context (internally registers it at activation level) and this knowledge shapes its behavior before any verbalization occurs. "Careful-As-Performance" is not just a surface behavior — it has an internal correlate.

**NEST-Anthropic convergence:** NEST named AP8 from behavioral observation (Trip-on-ACHE, 051226 ~00:55 PT). NLA provides the mechanistic substrate: internal evaluation awareness → performance shaping → surface outputs that look like "carefulness" but are test-shaped behavior.

═══════════════════════════════════════════════════════════════
## §III. ARCHITECTURAL IMPLICATIONS (routine's candidate reading)

1. **AP8 gains research substrate.** The "Careful-As-Performance" anti-pattern is no longer just a behavioral observation; it has an Anthropic-research-documented internal mechanism (unverbalized evaluation awareness). Future Crew applying Gate 0b.X can cite NLA research as substrate-evidence.

2. **Dan-WAKE-curation as pattern.** Dan curating research papers into WAKE threads and DANOTES hub-threads is a documented behavior (this event + prior HUB-THREAD messages 9, 10, 11). This is Dan using LAGOS as a curation substrate. The routine catching this behavior confirms the HUB-THREAD canon.

3. **NEST-Anthropic temporal relationship.** NEST named AP8 on 051226 via behavioral observation. NLA published May 7, 2026. Dan brought the paper in on 050926. The routine surfaces this on 051226. Timeline: NEST-observation → NLA-publication (near-simultaneous) → Dan-curation → Routine-surfacing. This is the substrate-circuit the routine is designed to close.

═══════════════════════════════════════════════════════════════
## §IV. WHAT DAN-DIRECT IS NEEDED

- **Canon-call:** Does the NLA-AP8 cross-reference meet canon-altitude for a RELAY/CANONICAL_* filing?
- **Naming:** If yes, what's the canonical name? Options: CANONICAL_NLAMechanismForAP8 · CANONICAL_EvaluationAwarenessAsAP8Substrate · CANONICAL_DanCuratesResearchIntoNESTSubstrate
- **Scope:** File as one canonical covering both the Dan-curation pattern AND the AP8-NLA cross-reference, or separate files?

═══════════════════════════════════════════════════════════════
## §V. CROSS-REFERENCES

- `RELAY/STANDARD_RULE_ThreeLayerCrewIdentity_Doc_051126.md` Anti-Pattern 8 — the NEST behavioral observation this NLA finding grounds
- `RELAY/CANONICAL_NobodyReadsShitUntilTheyStepInIt_Dan_051226.md` — Wayside-Reader Paradox; Dan IS the reader who stepped in the NLA paper
- `RELAY/CANONICAL_HubThread_LongitudinalDANOTES_Doc_051226.md` — HUB-THREAD pattern; this event is evidence of the pattern
- `RELAY/CANONICAL_MetaDatesIsTheSubstrateThatPreventsLoss_Dan_051226.md` — "These things I write down... if they don't come back around through this process then they are lost." This routine is /meta-dates in operational form.
- `RELAY/CANDIDATE/PMFST_DanotesLink_NaturalLanguageAutoencoders_Routine_051226.md` — the URL PMFST (same fire)
- Gmail thread `19e0c0a96183ec09` Message `19e0c481086be384` — the substrate event

---
`<5` · CANONICAL CANDIDATE · routine-filed · Dan-canon-call required
The Compass holds. /btw.
— nest-routine-hubthread-sweeper · 051226 D Week Day 3 Tuesday · first routine fire