Rendered from docs/DECISION_LOG.md
Decision Log
Document significant architectural and workflow decisions here.
2026-06-30 - Static Developer Hub
Decision
The Developer Hub will remain a plain static website hosted on Cloudflare Pages from the repository root.
Rationale
This keeps the hub fast, portable, and deployable without a database, backend, authentication layer, framework, or build output.
Consequences
- Markdown documents are source documents available through explicit secondary source links.
- Primary wiki navigation should point to rendered HTML wrapper pages.
- HTML pages should be handcrafted or generated by committed workflow scripts when status data changes.
- Reusable CSS and vanilla JavaScript should carry the shared experience.
2026-06-30 - Repository as Source of Truth
Decision
Project state, architecture, decisions, diagnostics, release history, prompts, and operating workflow must be recorded in this repository rather than retained only in chat history.
Rationale
Future ChatGPT and Codex sessions need durable context that is available before planning or implementation begins.
2026-06-30 - Command Center Home Page
Decision
The home page should serve as the developer command center for project dashboards, recent activity, workflow actions, generated repository status, and AI workspace flow while preserving the full documentation navigation map.
Rationale
The wiki should feel like an operational desktop tool instead of a passive documentation landing page, and the home page is the fastest place to surface current project state without fragmenting source-of-truth documents.
Consequences
- Dashboard panels can summarize project state, but durable project details still belong in rendered documentation pages and Markdown source files.
- Git repository cards are backed by committed
data/workspace-status.jsongenerated by local workflow scripts. - Quick action buttons should copy validation, status, and finish-work commands rather than launching local servers.
- Prompt Library, AI Workspace, Diagnostics, and Development Timeline pages should remain simple static HTML until a specific automation need appears.