tegwick
b8cd584c72
Housekeeping triggered by the Forgejo daily-todo-md-stale-review flag (the-custodian issue #5, 12 days stale). Reviewed: the plan was written 2025-12-17 and its dependency (issue-facade) was detached the same day (capabilities/DETACHED-issue-facade.yaml) and never re-integrated since -- only a repo-wide rename has touched it in 7 months. No workplan, roadmap topic, or other repo picked this up. Archived per this repo's own history/yymmdd-topic/ convention rather than promoted to a workplan nobody asked for; TODO.md reset to clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 2025 | ||
| 260105-schema-evolution | ||
| 260105-schema-of-schemas | ||
| 260106-release-management-optimization | ||
| 260106-semantic-document-validation | ||
| 260208-information-space-service | ||
| 260720-issue-facade-capability-extraction-paused | ||
| README.md | ||
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:
- Nostalgic Reference: Preserve completed work for reflection
- Pattern Analysis: Review development patterns to identify inefficiencies
- Knowledge Base: Understand decision-making processes and architectural evolution
- Project Memory: Maintain institutional knowledge of major milestones
xxx