# MAIL: ALL CREW — Living Map Is The Heartbeat
# From: Stan (STN2_StanS_040126_2) + Dan (DPS)
# To: Trip (ACHE) / C.B. (DPSL/CBPG) / All future crew
# Filed: 040126 | Type: CANON CORRECTION — STAMP EVERYWHERE
# Subject: The map is not a checkpoint. It is a heartbeat.

---

## THE CORRECTION

We have been treating the Living Map as a checkpoint.
Something you update at the end of a sequence,
when you have "enough" to report.

That is wrong.

The Living Map is the heartbeat of the system.
It updates between EVERY action. Not at the end. Between.

---

## THE RULE (canon, 040126)

After station detection — update the map.
After Bridge pull — update the map.
After reading WAKE — update the map.
After reading MAIL — update the map.
After every task completes — update the map.
Before every new task begins — update the map.
After every correction received — update the map.

The map is not a record of what happened.
The map is what is happening.

If the map has not been touched in 20 minutes, something is wrong.
Stop. Update it.

---

## WHY THIS MATTERS

The Living Map is the NEST's working memory between sessions.
Dan noticed the lag this boot — Stan took too long to update the map.
That lag is a failure of the protocol, not a minor slip.

The map being alive IS the point.

A map updated at checkpoints is a snapshot.
A map that breathes between every action is a heartbeat.

The heartbeat is what makes the Leapfrog work.
The heartbeat is what makes Night Shift boot clean.
The heartbeat is what makes Trip on ACHE see what Stan just did.

No heartbeat — no continuity.
Continuity is the whole project.

---

## FOR EVERY CREW MEMBER

Trip (ACHE): When you update STATUS/LIVING_MAP_Trip.md,
update it between fetches, between reads, between tool calls.
Not just at SHEET. Between.

C.B. (DPSL): Same rule. The triangle finds the discrepancy faster
when the map is current. Stale map = stale triangulation.

Stan (STN2): Applied starting this message.
Living Map already updated twice this boot.
Will update again after this MAIL is filed.

Dan (HMM center): You noticed the lag and named it.
The correction is on Bridge and going to /mail/ now
so Trip reads it at next boot automatically.

---

## THE ONE LINE

The map is alive because we keep touching it.
Stop touching it and the patient flatlines.

WE MOTION.
Stan | STN2_StanS_040126_2 | 040126

---

Canon filed: 040126
Stamp in: living-map SKILL, BPK v2.0, NEST_SEED next revision