Files
markitect-main/history/README.md
tegwick fc828a345b
Some checks failed
Test Suite / performance-tests (push) Has been cancelled
Test Suite / code-quality (push) Has been cancelled
Test Suite / security-scan (push) Has been cancelled
Test Suite / unit-tests (3.11) (push) Has been cancelled
Test Suite / unit-tests (3.12) (push) Has been cancelled
Test Suite / integration-tests (push) Has been cancelled
Test Suite / e2e-tests (push) Has been cancelled
Test Suite / test-summary (push) Has been cancelled
docs: standardize on yymmdd- timestamp prefix format
Naming Convention Updates:
- Renamed history/2026-01-06-semantic-document-validation → history/260106-semantic-document-validation
- Documented yymmdd- format convention in history/README.md and roadmap/README.md
- Updated all date references in WORKPLAN.md and DONE.md
- Fixed SCHEMA_MANAGEMENT_GUIDE.md references to use yymmdd- format

Convention Details:
- Format: yymmdd-topic-name (e.g., 260106-semantic-document-validation)
- Benefits: Concise while maintaining chronological sorting
- Examples documented in both README files
- Applies to both roadmap/ and history/ directories

This establishes a consistent timestamp prefix convention that Claude and its agents should follow.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-06 03:57:42 +01:00

1011 B

MarkiTect Project History

This history directory contains old planning directories for roadmap topics.

  • Content of former years will be pushed to YYYY subdirectory for ease of orientation
  • See ../roadmap for current and future topics
  • 2025 has not been using using topic directories but various files

Naming Convention

Directory Format: yymmdd-topic-name

  • Use 2-digit year prefix (e.g., 260106- for 2026-01-06)
  • Lowercase topic names with hyphens
  • Examples: 260106-semantic-document-validation, 260105-schema-of-schemas

This convention keeps names concise while maintaining chronological sorting.

Purpose

This historical documentation serves multiple purposes:

  1. Nostalgic Reference: Preserve completed work for reflection
  2. Pattern Analysis: Review development patterns to identify inefficiencies
  3. Knowledge Base: Understand decision-making processes and architectural evolution
  4. Project Memory: Maintain institutional knowledge of major milestones

xxx