name: internal-record description: Writes the ADVISOR-ONLY internal record of an advisory session from the approved ledger — what was decided, named gaps, what is still open, consent flags, commitments by owner, and reference-data updates. Kathryn's private document, never client-facing. Use in Phase B after the digest is approved.

Internal record

Not to be confused with session-recap, which IS the client email. This skill writes the document the client never sees; session-recap writes the one they do. If you are here because you were asked for the recap, you are in the wrong skill.

The internal record. Kathryn's, never the client's. It holds what the recap cannot: her read, the patterns, the things worth watching.

Source

ledger.json, and nothing else. Do not reopen the transcript. If a fact you want is not in the ledger, it does not go in the record — go back to Phase A and amend the ledger, which means the digest gets re-approved. That is the cost of the rule and it is the point of the rule.

Shape

# [Engagement] — [session type], [date]

**Engagement:** [name] · [type]
**Present:** [attendees]
**Format:** [times, duration]
**Ledger:** `ledger.json` — [n] claims, [n] hedged, gate CLEAR

## Documents worked live
## Modality watch list — read before anything ships
## Decided
## Named gaps
## Still open
## Consent flags
## Commitments by owner
## Reference data updates needed
## Advisor notes

Rules

The modality watch list goes near the top, not the bottom. Every hedged row, with what was actually said beside how it must not be written. Anyone editing a downstream document reads this first or writes the flattened version by accident.

Advisor notes belong here and nowhere else. Behavioural reads, coaching observations, what went unsaid, patterns across sessions. This is the document that carries Kathryn's judgment. The recap carries none of it.

Reference data updates are listed, not applied. Name what surfaced, what it resolves, and what stays unconfirmed. Applying them is a separate decision with a person in it.

Unconfirmed proper nouns appear only under reference data updates, marked unconfirmed. They appear nowhere in the body.

Output

engagements//sessions//record.md, with ledgerId in the header so the verifier can confirm it was built from the approved ledger.