Daily Notes Governance & Archival Standards
This directory serves as the centralized high-velocity capture layer (Tier 1 Memory) for all daily activities, session logs, engineering logs, and work records.
📌 Standard Operating Procedures (SOP)
1. Consistent Nomenclature
- All files in this folder MUST follow the strict date-based naming convention:
YYYY-MM-DD.md(e.g.,2026-06-27.md). - No separate “Session Logs” subdirectories or redundant prefixes (such as “Session Log - ”) are allowed.
2. Single-Source Consolidated Log (The Full Representation Rule)
- Each file must represent a complete, unified record of all work, contexts, and sessions completed on that specific day.
- If multiple sessions occur on the same day, append or integrate the logs into the single daily file instead of creating separate files.
- CRITICAL: Do NOT delete, compress, or prune detailed historical log items during curation. The full, rich context must remain intact in the log so that automated sweep and indexing agents can search and extract relevant topics down the line.
3. Frontmatter & Metadata Parity
Every daily note must contain consistent YAML frontmatter for seamless indexing and rendering:
---
title: "Daily Work Log - YYYY-MM-DD"
lifecycle_stage: "core"
tags: "daily-note | engineering"
---🔄 Archival & Curation Lifecycle
- Capture (Active Turn): The human and AI pair program and record accomplishments in today’s daily file (
YYYY-MM-DD.md). - Promote (Sweep Turn): The Sweep Agent regularly scans the daily notes directory to extract architectural patterns, strategic SOPs, client profiles, and system milestones.
- Persist (Long-Term Vault): Distilled knowledge is written to the core business pillars (
01_Attract,02_Convert,03_Serve,04_Intelligence), while keeping the original daily log intact as an immutable audit trail.