feynman/session_notes

To write narrative session notes with ledger citations, you generate Markdown artifacts that explicitly separate human-readable context from ledger logs, enforcing a citation ID for every factual statement. This ensures full auditability.

Maintaining provenance for HELEN session reviews requires creating Markdown-only narrative notes where every factual claim is anchored to a real ledger receipt by ID. This separates narrative context from raw logs while supporting easy archival.

Formatting session notes for standardized retrieval involves outputting Markdown artifacts to a dedicated artifacts/session_notes directory using the YYYY-MM-DD__<session_id>.md naming convention. This ensures consistent storage and provenance tracking.

Yes, generating narrative HELEN session notes requires frontmatter that defines the name and description of the notes. This metadata is strictly required before the Markdown provenance artifacts can be properly generated and archived.

Yes, you can use narrative Markdown notes for governance audits by ensuring every factual statement cites a specific ledger receipt ID. This explicitly separates the human-readable narrative from the non-ledger text while maintaining auditability.

Separating narrative context from ledger logs in session notes ensures that human-readable diaries remain Markdown-only while every factual claim is backed by a real ledger receipt ID. This prevents unverified claims and supports rigorous provenance tracking.