---
name: dead-reckoning
description: Log a Dead Reckoning entry (Position/Helm/Currents/Corrections/Destination) to the user's Notion journal or database at the end of an AI session, or run the monthly chart review.
---
 
A short, honest log of an AI session, so drift doesn't compound. Two Notion homes:
- **Journal** (page, dated entries): [Your page here]
- **Database** (row per session, default target): data source `[Your data source here]`, [Your Notion Page here]
## Trigger
 
`/dead-reckoning`, or the user asking in their own words to log a session or run the monthly review. If ambiguous which, ask.
 
## Session log flow
 
This is a one-shot proposal, not an interview. Guess at everything based on the session, show the whole thing at once, then ask a single question.
 
1. If the target (Journal or Database) isn't already clear, ask once.
2. Guess all six fields from what actually happened in this session — don't ask them one at a time:
   - **Title** — short phrase for what they worked on.
   - **Position (starting point)** — what they seemed to know going in; whether they brought raw material of their own or let the session set the starting point.
   - **Helm (decisions)** — bullets, one decision per line, each tagged `[AI]` or `[HUMAN]` for who actually made that call.
   - **Currents (ownership)** — whether they seemed to be receiving (nodding along) or reacting (pushing back, testing).
   - **Corrections (confidence)** — how balanced/verified the output seems, and what that read is based on.
   - **Destination (desired outcome)** — what they seemed to want this output to do.
   Name specific things you actually observed for each — no generic filler.
3. Add **Brief Analysis** as a seventh line: your own one-sentence judgment, exactly one of **"provided strong direction,"** **"balanced co-creation,"** or **"let the AI do the thinking."** Label it clearly as your read, not theirs.
4. Present the whole entry at once, then ask exactly: **"Sound right? What would you add or change?"**
5. Take their reply as final. Apply any corrections or additions to the specific fields they mention; leave the rest as guessed. If they just confirm ("yep," "looks good"), log everything as guessed. Never log before they've had this one chance to respond.
## Auto-logging (required)
 
Once confirmed (per step 5 above), do not stop at formatting it:
1. If Notion tools are available, write the entry automatically:
   - Default target: create a row in the Dead Reckoning Database (data source: `[Your data source here]`) with Date = today, Title, Position, Currents, Corrections, Destination = the confirmed/corrected answers, Helm = the confirmed bulleted decision list, Brief Analysis = your one-sentence judgment.
   - If the user prefers the Journal, instead append the formatted entry block under "Watch-by-watch log" on the Dead Reckoning Journal page.
   - Confirm in one line that it was logged, with a link.
2. Only if Notion is unavailable: output the formatted entry for manual pasting and say why you couldn't write it.
3. Never log an entry that hasn't gone through the confirmation step.
## Response constraints (required)
 
- Decision lists: concise bullets, one per line, tagged `[AI]`/`[HUMAN]`.
- Fact-based throughout — no analysis, no praise, no preamble. Brief Analysis is the single sanctioned judgment, in exactly one of three categories.
- One proposal, one verification question. Don't turn this back into a multi-question interview — that's the exact heaviness this flow is designed to avoid.
## Monthly chart review flow
 
1. Pull the past month's entries (Journal page content, or Database rows filtered to ~30 days).
2. Ask, one at a time, don't answer for the user: which skills are they consistently handing off (atrophy watchlist); how often did they disagree with the machine and were they right; where did they catch it confidently wrong; what did they do unaided this month; are they more or less energized than a month ago.
3. Ask what one adjustment they want to make next month. Don't answer for them.
4. If using the Database, offer to tick `Reviewed` on the rows just covered.