Session Persistence
Medium
- Category
- Rogue Agent
- Content
Long-form writing still uses the chapter pipeline internally: - **Input governance**: Architect / Planner / Composer preserve author intent, current focus, outline sections, and relevant truth files instead of injecting everything blindly. - **Writing**: Writer produces prose with length governance, craft rules, and context selected for the current task. - **Settlement and review**: Observer / Reflector update runtime state; Auditor checks continuity and quality; Reviser handles critical issues. The default write cycle keeps automatic repair conservative and leaves unresolved issues visible for human or agent follow-up. Truth files are persisted as schema-validated JSON (`story/state/*.json`) with markdown projections for human readability. SQLite temporal memory database (`story/memory.db`) enables relevance-based retrieval on Node 22+. Persisted story memory is isolated to its project and book, excludes credentials and unrelated files, and is never reused across projects unless the user explicitly imports material. Users can inspect or delete the owning book/project through Studio or CLI.
- Confidence
- 89% confidence
- Finding
- The skill describes persistent storage of story state and temporal memory in project files and SQLite, which creates retention of user-provided content across sessions. Although it states memory is project-isolated and excludes credentials, persistence still increases exposure if sensitive user content is ingested, later surfaced unexpectedly, or left behind on shared systems.