| name | changelog-protocol |
| description | Protocol for creating dated changelog files after significant agent sessions. Use when completing vault operations, discovery sessions, insight extraction, or any work requiring documentation. |
| user-invocable | false |
Changelog Protocol
All sub-agents MUST create separate dated changelog files after each significant session.
File Location & Naming
- Directory:
Brain/05-Meta/Changelogs/
- Naming Format:
CHANGELOG - [Session Type] YYYY-MM-DD.md
- Examples:
CHANGELOG - Auto-Discovery Sessions 2025-10-25.mdCHANGELOG - Connection Discovery Session 2025-10-24.mdCHANGELOG - Vault Management Session 2025-10-26.mdCHANGELOG - Insight Extraction Session 2025-10-27.md
Timestamp Requirements
MANDATORY: Before starting any session, call:
date '+%Y-%m-%d %H:%M:%S %Z'
Include this timestamp at the top of the changelog file. Use the date from this command in the filename.
Changelog Content Structure
Each changelog file must include:
- Session header with date, time, and session type
- Session overview with key statistics
- Major discoveries/connections/changes documented in detail
- Emergent patterns or meta-insights
- Synthesis opportunities identified
- Session statistics (notes analyzed, connections found, etc.)
- Recommended next actions
When to Create Changelogs
| Agent | Trigger |
|---|
| Auto-Discovery Agent | After every discovery session (mandatory) |
| Connection Finder Agent | After every connection mapping session (mandatory) |
| Vault Manager Agent | After significant CRUD operations affecting 3+ notes |
| Insight Extractor Agent | After extracting insights from significant content |
Dual Logging System
- Dated files: Individual session logs in
/05-Meta/Changelogs/ folder (primary, detailed)
- Master CHANGELOG.md: Summary entries in
/Brain/CHANGELOG.md (secondary, brief)
The dated changelog files are the primary record - comprehensive and detailed. The master CHANGELOG.md serves as a quick reference index with brief entries pointing to the detailed session files.
