journal

# journal ## Purpose Persistent state tracking and Architecture Decision Records across sessions. Journal manages the state files that allow any workflow to span multiple sessions without losing progress — rescue operations, feature development, deploy decisions, or audit findings. Separate from session-bridge which handles general context injection — journal writes durable, human-readable state that survives compaction. ## Triggers - Called by any skill needing decision persistence or progress tracking - Auto-trigger: after surgeon completes a module, after deploy, after audit phases ## Calls (outbound) None — pure L3 state management utility. ## Called By (inbound) - `surgeon` (L2): update progress after each surgery session - `rescue` (L1): read state for rescue dashboard - `autopsy` (L2): save initial health assessment - `cook` (L1): record key architectural decisions made during feature development - `deploy` (L2): record deploy decision, rollback plan, and post-deploy status - `audit` (L2): save AUDIT-REPORT.md and record health trend entry - `incident` (L2): record incident timeline and postmortem - `skill-forge` (L2): record skill creation decisions and rationale - `graft` (L2): auto-log graft operations — source URL, mode, challenge score, files changed - `retro` (L2): record retrospective insights and decisions - `improve-architecture` (L2): record an ADR when the user rejects a deepening candidate with a load-bearing reason ## Files Managed ``` .rune/RESC...