feynman/session_notes

Capture HELEN session notes with ledger receipt citations for every claim.

Updated Apr 4, 2026

Search Tags:#markdown #narrative #provenance #notes #session #ledger #HELEN

Ready to run

npx skills add https://github.com/JMTassy/helen-conquest --skill feynman-session-notes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feynman/session_notes
Source: https://github.com/JMTassy/helen-conquest/tree/main/oracle_town/skills/feynman/session_notes
Command: npx skills add https://github.com/JMTassy/helen-conquest --skill feynman-session-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Narrative session notes provide a human-readable diary of HELEN sessions that are Markdown-only and explicitly non-ledger, while ensuring every factual claim cites a real ledger receipt by ID.

Core Features & Use Cases

Cite ledger receipts for every factual claim to maintain auditability.
Markdown provenance artifacts that separate narrative from ledger logs and support easy storage, review, and provenance tracking.
Output to artifacts/session_notes for standardized retrieval and archival.

Quick Start

Fetch the notes for a given HELEN session and save them to artifacts/session_notes in the format YYYY-MM-DD__<session_id>.md.

Frequently Asked Questions about feynman/session_notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write narrative session notes that cite ledger receipts?▼

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.

What is the best way to maintain provenance for HELEN session reviews?▼

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.

How do I format session notes for standardized retrieval and 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.

Do I need frontmatter to generate narrative HELEN session notes?▼

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.

Can I use Markdown notes for governance audits without raw ledger logs?▼

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.

Why should I separate narrative context from ledger logs in session notes?▼

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.