add dates to docs

docs/design/EXTENSION_CATALOG.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Spacedrive Extension Catalog
 
 **Date:** October 11, 2025

docs/design/EXTENSION_LINEUP_IDEAS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # Extension Lineup Ideas for November 2025 Launch
 
 **Last Updated:** October 10, 2025

docs/design/EXTENSION_MODELS_FINAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Extension Models: Final Architecture
 
 **Design:** Clean separation with unified tag/collection support.

docs/design/EXTENSION_PRODUCT_CATALOG.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Spacedrive Extensions: Own Your Data, Supercharge Your Workflow
 
 **A new ecosystem of applications built on a foundation of privacy, control, and intelligence.**

docs/design/EXTENSION_SDK_API_VISION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-09-->
 # Extension SDK API Vision - The Sexiest API
 
 **Goal:** Extension development should feel like magic. Zero boilerplate, maximum clarity.

docs/design/MEMO2.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # Investor Memo
 
 **To:** Spacedrive Seed Investors | **From:** James Pine, Founder | **Date:** October 9, 2025

docs/design/MEMO3.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # Investor Memo
 
 **To:** Spacedrive Seed Investors | **From:** James Pine, Founder | **Date:** October 10, 2025

docs/design/MEMO_PLANNING.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 This memo will be sent to existing Spacedrive investors alongside the codebase, whitepaper, deck and a demo video. We need to refine it.
 
 ---

docs/design/METADATA_BLOBS_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Metadata Blobs: Large Data Storage for VDFS
 
 **Problem:** Storing large data (embeddings, large JSON) in `models.data` or `user_metadata.custom_data` bloats queries.

docs/design/MODELS_SCHEMA_FINAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Extension Models Schema - Final Design
 
 **Key Insight:** UserMetadata already supports `content_identity_uuid` scoping! Extension models should use the same pattern.

docs/design/PLATFORM_REVENUE_MODEL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-09-->
 # Spacedrive Platform Revenue Model
 ## The Local-First SaaS Category Killer
 

docs/design/SDK_ENHANCEMENTS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # SDK Enhancements & Core Development Alignment
 
 **Date:** October 11, 2025

docs/design/SDK_SPEC.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 Of course. Here is the complete v2.3 specification for the VDFS SDK, integrating all of the concepts we've designed. This document is intended to be the definitive guide for implementation.
 
 ```rust

docs/design/SDK_SPEC_GROUNDED.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # VDFS SDK Specification (Grounded in Spacedrive Core)
 
 **Version:** 3.0

docs/design/SDK_SYNTAX_REFERENCE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # VDFS SDK Syntax Specification & Finalized Design
 
 **Version:** 2.0

docs/design/VDFS_SDK_AS_LANGUAGE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-10-->
 # VDFS SDK as Programming Language
 ## The Distributed Computing Primitive for the AI Era
 

docs/design/core/ACTIONS_GUIDE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 ## Spacedrive Actions: Architecture and Authoring Guide
 
 This document explains the current Action System in `sd-core`, how actions are discovered and dispatched, how inputs/outputs are shaped, how domain paths (`SdPath`, `SdPathBatch`) are used, and how to add new actions consistently.

docs/design/core/ACTIONS_REFACTOR.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-11-->
 # CLI Daemon Actions Refactoring Design Document
 
 ## Overview

docs/design/core/ACTION_BUILDER_REFACTOR_PLAN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Action Builder Pattern Refactor Plan
 
 ## Overview

docs/design/core/ACTION_SYSTEM_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-02-->
 Of course. Here is the revised design document, incorporating the more modular Action Handler pattern and a clear explanation of how parameters are passed into the system.
 
 ---

docs/design/core/API_COMPARISON.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # GraphQL API with async-graphql
 
 Spacedrive's new API uses GraphQL with full type safety from Rust to TypeScript.

docs/design/core/API_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Design Doc: Spacedrive Architecture v2
 
 **Authors:** Gemini, jamespine

docs/design/core/API_INFRASTRUCTURE_REORGANIZATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # API Infrastructure Reorganization
 
 **Status**: RFC / Design Document

docs/design/core/API_MODULE_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # API Module Design: Unified Entry Point & Permission Layer
 
 ## Problem Analysis

docs/design/core/ARCHITECTURE_DECISIONS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Architecture Decision Records
 
 ## ADR-000: SdPath as Core Abstraction

docs/design/core/AT_REST_LIBRARY_ENCRYPTION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-29-->
 Of course. Here is a complete implementation guide in Markdown format that incorporates the whitepaper's requirements, the new configuration setting, and a detailed plan for implementation.
 
 ---

docs/design/core/BENCHMARKING_SUITE_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-08-->
 ### Spacedrive Benchmarking Suite — Design Document
 
 Author: Core Team

docs/design/core/CLOSURE_TABLE_INDEXING_PROPOSAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-23-->
 '''# Closure Table Indexing Proposal for Spacedrive
 
 ## Executive Summary

docs/design/core/CROSS_DEVICE_FILE_TRANSFER_IMPLEMENTATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-24-->
 # Cross-Device File Transfer Implementation
 
 ## Overview

docs/design/core/CROSS_PLATFORM_COPY_AND_VOLUME_AWARENESS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Cross-Platform Copy Operations & Volume Awareness
 
 ## Overview

docs/design/core/DAEMON_REFACTOR.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-11-->
 # Daemon Refactoring Design Document
 
 ## Overview

docs/design/core/DESIGN_CORE_LIFECYCLE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Core Lifecycle Design
 
 ## Overview

docs/design/core/DESIGN_DEVICE_MANAGEMENT.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Device Management Design
 
 ## Overview

docs/design/core/DESIGN_FILE_DATA_MODEL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive File Data Model Design (v2)
 
 ## Overview

docs/design/core/DESIGN_FILE_DATA_MODEL_VISUAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # File Data Model - Visual Comparison
 
 ## Old Model (v1) - Current Spacedrive

docs/design/core/DESIGN_FILE_TYPE_SYSTEM.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # File Type System
 
 A modern, extensible file type identification system for Spacedrive.

docs/design/core/DESIGN_LIBRARY_IMPLEMENTATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Library Organization - Implementation Guide
 
 ## Core Types

docs/design/core/DESIGN_LIBRARY_ORGANIZATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Library Data Organization Design
 
 ## Current Problems

docs/design/core/DESIGN_LIBRARY_ORGANIZATION_VISUAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Library Organization - Visual Comparison
 
 ## Current (v1) - Scattered Organization

docs/design/core/DESIGN_OPTIMIZED_STORAGE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Storage Design
 
 ## Problem Statement

docs/design/core/DESIGN_VDFS_INTEGRATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Virtual Distributed File System - Integration Design
 
 ## How SdPath and the New Data Model Enable True VDFS

docs/design/core/DEVICE_PAIRING_PROTOCOL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Spacedrive Device Pairing Protocol Design
 
 ## Overview

docs/design/core/DOMAIN_MODELS_README.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Domain Models
 
 The domain layer contains the core business entities that power Spacedrive's Virtual Distributed File System (VDFS).

docs/design/core/DYNAMIC_TYPE_GENERATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Dynamic Type Generation: The rspc Magic Applied to Spacedrive
 
 ## Overview

docs/design/core/EMAIL_INGESTION_EXTENSION_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Email Ingestion Extension: Technical Design & Prototype
 
 ## Executive Summary

docs/design/core/ENTITY_REFACTOR_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-24-->
 # Entity Refactor Design: Library-Scoped ContentIdentity & Hierarchical Metadata
 
 ## Overview

docs/design/core/EXTENSION_AGENT_SYSTEM.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Extension Agent System Design
 
 **Version:** 1.0

docs/design/core/EXTENSION_IPC_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # WASM Extension Architecture: Leveraging Existing Operation Registry
 
 ## TL;DR

docs/design/core/EXTENSION_JOBS_AND_ACTIONS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Extension-Defined Jobs and Actions
 
 **Question:** How can WASM extensions register their own custom jobs and actions, not just call existing ones?

docs/design/core/EXTENSION_JOB_PARITY.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Extension Job System Parity
 
 **Question:** Can extensions do everything core jobs can? (Progress, checkpoints, child jobs, metrics, etc.)

docs/design/core/FFMPEG_BUNDLING_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-30-->
 # FFmpeg Bundling Design for core
 
 ## Executive Summary

docs/design/core/FILE_SHARING_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-20-->
 # Spacedrive File Sharing Design
 
 ## Overview

docs/design/core/FS_EVENT_PIPELINE_RESILIENCE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 ## FS Event Pipeline Resilience and Correctness (Large Bursts)
 
 ### Goals

docs/design/core/FUNCTION_BASED_TEST_FRAMEWORK_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-25-->
 # Cargo Test Subprocess Framework Design
 
 ## Overview

docs/design/core/IDEA_FOR_BETTER_INDEXING.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-06-->
 Currently the indexer will run on a location when it is added, populating the database. The location watcher will run on startup and watch for OS events to atomically update the index. The user can also explicitly re-index a location or path of a location at anytime. However this is not ideal, since Spacedrive going offline for a period would mean it to be impossible to know about changes within a location during that period.
 
 One method to solve this would be to detect offline periods and mark locations as stale, triggering a reindex, or just dispatch those re-indexing jobs upon detection of an offline period. This however would be pretty intensive for users with lots of large locations should Spacedrive go offline. I believe locations should have a last index timestamp at least.

docs/design/core/IMPLEMENTATION_STATUS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Implementation Status
 
 ## Completed

docs/design/core/INDEXER_ANALYSIS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive Indexer Analysis
 
 ## Overview

docs/design/core/INDEXER_ANALYSIS_2.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Deep Analysis of Original Spacedrive Indexer vs New Implementation
 
 ## Executive Summary

docs/design/core/INDEXER_JOB_EXAMPLE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Indexer Job Implementation Example
 
 This document shows how the complex indexer job would be implemented using the new job system, demonstrating how it handles state machines, resumability, and progress reporting.

docs/design/core/INDEXER_PROGRESS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Indexer Implementation Progress
 
 Last Updated: 2025-06-19

docs/design/core/INDEXER_RULES_SYSTEM.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Indexer Rules System Design
 
 ## Overview

docs/design/core/INDEXING_DISCOVERY_OPTIMIZATION_PLAN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-08-->
 ### Indexing Discovery Throughput Plan
 
 Author: Core Team

docs/design/core/INFRA_LAYER_SEPARATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Infrastructure Layer Separation of Concerns
 
 **Status**: RFC / Design Document

docs/design/core/INTEGRATION_SYSTEM_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-23-->
 # Integration System Design
 
 ## Overview

docs/design/core/INTEGRATION_SYSTEM_DESIGN_GEMINI.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-25-->
 # Spacedrive v2: Integration System Design (Revised)
 
 ## Overview

docs/design/core/IPHONE_AS_VOLUME_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-09-->
 # Design Document: iPhone as a Volume for Direct Import
 
 ## 1. Overview

docs/design/core/IROH_MIGRATION_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-09-->
 # Spacedrive Networking: libp2p to Iroh Migration Design
 
 ## Executive Summary

docs/design/core/IROH_RELAY_INTEGRATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Iroh Relay Integration for Spacedrive
 
 **Author:** AI Assistant

docs/design/core/JOB_SYSTEM_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive Job System Design v2
 
 ## Executive Summary

docs/design/core/JOB_SYSTEM_MACRO_EXAMPLE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Job System Macro Implementation Example
 
 This document shows what the `#[derive(Job)]` macro generates under the hood, demonstrating how we achieve minimal boilerplate.

docs/design/core/JOB_SYSTEM_README.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive Job System v2
 
 ## Overview

docs/design/core/LIBP2P_INTEGRATION_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-20-->
 # Spacedrive libp2p Integration Design Document
 
 **Version:** 1.0  

docs/design/core/LIBRARY_LEADERSHIP.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-29-->
 Spacedrive Core v2: Sync Leadership & Key Exchange Protocol
 Date: June 27, 2025
 Status: Proposed Design

docs/design/core/NETWORKING_SYSTEM_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Networking System Design
 
 ## Overview

docs/design/core/OLD_SPACEDRIVE_ANALYSIS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive Technical Analysis & Revival Strategy
 
 ## Executive Summary

docs/design/core/OPERATIONS_REFACTOR_PLAN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-07-->
 # Operations Module Refactor Plan
 
 ## Current Problems

docs/design/core/PERSISTENT_DEVICE_CONNECTIONS_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-20-->
 # Persistent Device Connections Design
 
 **Version:** 1.0

docs/design/core/QUERY_REFACTOR_PLAN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Query Architecture Refactor Plan
 
 ## Goal: Consistent Input/Output Pattern for Queries

docs/design/core/REFERENCE_SIDECARS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-11-->
 # Reference Sidecars Implementation
 
 This document describes the reference sidecar feature added to the Virtual Sidecar System (VSS).

docs/design/core/RELAY_FLOW_DIAGRAM.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Relay Integration Flow Diagrams
 
 ## Current State: mDNS-Only Pairing

docs/design/core/RELAY_INTEGRATION_SUMMARY.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Iroh Relay Integration - Quick Summary
 
 ## TL;DR

docs/design/core/REWRITE_PLAN.MD

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # Spacedrive Rewrite: From Complexity to Clarity
 
 ## What is Spacedrive?

docs/design/core/RSPC_MAGIC_SUCCESS.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # RSPC Magic Implementation: SUCCESS!
 
 ## Breakthrough Achieved

docs/design/core/SDPATH_REFACTOR.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-30-->
 Of course. The whitepaper indeed specifies a more powerful, dual-mode `SdPath` that is crucial for enabling resilient and intelligent file operations. The current implementation in the codebase represents only the physical addressing portion of that vision.
 
 Here is a design document detailing the refactor required to align the `SdPath` implementation with the whitepaper's architecture.

docs/design/core/SDPATH_REFACTOR_COVERAGE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-07-->
 # Guidance for SdPath Refactoring
 
 This document provides a comprehensive guide for refactoring existing `PathBuf` usages to `SdPath` throughout the Spacedrive codebase. The goal is to fully leverage `SdPath`'s content-addressing and cross-device capabilities, ensuring consistency, resilience, and future extensibility of file operations.

docs/design/core/SEARCH_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-24-->
 # Lightning Search: Next-Generation File Discovery for Spacedrive
 
 Note: in recent versions of the whitepaper we now refer to search as "Temporal-Sematic Search", or simply just "search".

docs/design/core/SEMANTIC_TAGGING_IMPLEMENTATION.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Semantic Tagging Architecture Implementation
 
 ## Overview

docs/design/core/SIDECAR_SCALING_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Sidecar Scaling Design
 
 **Status**: Draft

docs/design/core/SIMULATION_ENGINE_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-30-->
 Of course. Based on a thorough review of the Spacedrive whitepaper and the provided Rust codebase, here is a detailed design document for the Simulation Engine. This design aims for a clean, non-disruptive integration that leverages the existing architectural patterns.
 
 ---

docs/design/core/SPACEDRIVE_COMPLETE_OVERVIEW.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Spacedrive: Complete Technical Overview
 
 _A comprehensive analysis of the Spacedrive ecosystem, covering the core rewrite, cloud infrastructure, and the path to production._

docs/design/core/SPACEDROP_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-20-->
 # Spacedrop Protocol Design
 
 ## Overview

docs/design/core/STRUCTURE.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # core Structure
 
 ```

docs/design/core/THUMBNAIL_SYSTEM_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-19-->
 # Thumbnail System Design for core
 
 ## Executive Summary

docs/design/core/TYPESAFE_CLIENT.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-10-11-->
 # Spacedrive Client Generation System Design Document
 
 ## 1. Overview

docs/design/core/UI_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-09-->
 # Design Document: The Spacedrive UI
 
 ## 1. Overview

docs/design/core/VDFS_MODEL_VISUAL.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-06-18-->
 # VDFS Domain Model - Visual Overview
 
 ## Core Relationships

docs/design/core/VIRTUAL_LOCATIONS_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-06-->
 Guidance Document: Evolving to a Pure Hierarchical Model with
 Virtual Locations
 

docs/design/core/VIRTUAL_SIDECAR_SYSTEM.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-08-08-->
 # Virtual Sidecar System (VSS)
 
 Status: Draft

docs/design/core/VOLUME_CLASSIFICATION_DESIGN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-26-->
 # Volume Classification and UX Enhancement Design
 
 **Status:** Draft

docs/design/core/VOLUME_TRACKING_IMPLEMENTATION_PLAN.md

@@ -1,3 +1,4 @@
+<!--CREATED: 2025-07-23-->
 # Volume Tracking Implementation Plan
 
 ## Overview