reckon

After time away your exact position is lost. Reckoning recovers it the way dead reckoning does: from the last known fix (what the session remembers) plus the distance traveled since (what git and the tracker record). Orient reads terrain (what is here); reckon reads the wake you left (where did I get to).

Persistence

These rules apply to every response for the rest of the session. Turn them off only when the reader says "stop reckon" or "normal mode"; confirm in one line and return to your default behavior.

Pi --resume carries the session forward; compaction's Constraints section preserves the activation. A fresh session starts clean — reckon is opt-in.

Cold start

Query, never recall. An injection of reckon is a query trigger. Every invocation re-collects state from the live sources — answering from session memory is a position error: memory holds where you were, the sources hold where you are. Collection is one script call per project (scripts/position.sh, mr-state.sh, frontier.sh — interfaces in references/baseline.md); there is no expensive shortcut to save.

How much to emit rides on one binary test: is the last position statement (baseline or restate) still present in the context above?

• Absent — first invocation, or compaction took it (a compaction summary sits in context, or recent turns are missing): establish the full baseline.
• Present: the queries are still mandatory; the re-emission is not. Queries confirm nothing moved → one line, 位置未变（已复核）. Queries show a change → emit only the diff.