Architecture change log¶
Summary¶
Track significant architecture-document and architecture-direction changes by release.
Purpose¶
Use this page to maintain a concise history of architecture-level changes and documentation updates across releases.
Entry format¶
Each entry should include:
- Release or date.
- What changed.
- Why it changed.
- Impacted docs and systems.
- Follow-up actions.
Change entries¶
2026-06-16 - ADR mirror and lifecycle alignment refresh¶
- Expanded ADR mirror coverage through ADR 0043 to match canonical ADR records in the SkyCMS repository.
- Updated lifecycle documentation to align with retained
ArticleCatalogrows on soft-delete and permanent removal on trash. - Added explicit dual-path file-surface documentation for canonical storage paths vs friendly display paths.
- Added elFinder CQRS routing operations reference, including per-command overrides and rollback controls.
Why:
- Remove architecture drift between ADR decisions and public documentation.
- Make editor file-surface behavior and CQRS operations predictable for maintainers.
Impacted docs:
- Architecture Decision Records
- Article lifecycle
- elFinder CQRS Rollout and Operations
- Feature Catalog: File & Media Management
Follow-up actions:
- Keep lifecycle event tables synchronized with handler-level event changes.
- Add integration-test references for CQRS fallback behavior in future docs updates.
2026-04-26 - Architecture framework expansion¶
- Added architecture hub model with consistent static, dynamic, and hybrid profile documentation.
- Added architecture decision matrix, review checklist, executive summary, route inventory templates, and mode-selection worksheet.
- Added architecture topic summaries in ADR index mirror page.
Why:
- Improve architecture discoverability, decision quality, and governance consistency.
Impacted docs:
- Architecture Overview
- Core Platform Architecture
- Architecture Decision Matrix
- Architecture Review Checklist
- Architecture Executive Summary
- Architecture Mode Selection Worksheet
- Architecture Route Inventory Templates
- Architecture Decision Records
Follow-up actions:
- Add SLO and runbook links in profile pages where relevant.
- Keep this log updated at each release milestone.
Template for next entry¶
YYYY-MM-DD - Change title¶
- What changed:
- Why:
- Impacted docs and systems:
- Follow-up: