rai-session-diary

Documenting session decisions is done by writing narrative diary entries that capture the decision arc, rationale, and turning points. This preserves the context of why specific choices were made for team review and governance.

Yes, you can publish session diaries to Confluence or the filesystem. The publishing process uses the project's docs adapter and includes a quality checklist and review step before the entry goes live.

Compiling a narrative record involves integrating git commits, conversation context, and session artifacts. This extracts evidence and direct quotes to accurately document the decision arc and next steps for future reference.

Preserving design pivots is best achieved by authoring an end-of-session diary entry in a first-person narrative voice. This honestly documents mistakes, highlights tensions, and makes session memory actionable for follow-up work.

A docs adapter is required for publishing session diaries to Confluence or the filesystem. However, the core task of drafting the narrative entry from conversation context and git commits does not depend on it.

You should write a session diary entry at the end of a design-heavy workflow. This is specifically needed when design decisions, pivots, or process insights must be preserved for team review and future reference.