rai-session-close

To persist CLI session outcomes and memory for project continuity, you close sessions by capturing decisions and updating the knowledge graph. This writes a session record to the index and produces a structured YAML state for future context.

Session governance is the practice of enforcing session-level records and patterns for auditability. You need to persist governance artifacts at the end of each working session to ensure compliance and maintain structured records of decisions across projects.

You generate a structured session state for handoff by finalizing the active session and appending outcomes. This produces a YAML session state that records decisions, next actions, and artifacts to ensure continuity across collaborators.

No, the session close process requires no external dependencies to update the knowledge graph. It operates independently to append outcomes, update coaching data, and write session records to the index.

The best way to capture patterns and outcomes across multiple projects is to apply a session close routine at the end of each working session. This ensures outcomes, patterns, and governance artifacts are consistently persisted to memory for ongoing continuity.