KP-DEV-HQ architecture

The site is a static-first Astro application deployed through GitHub Pages. Portfolio content is typed TypeScript data; Developer HQ operational pages consume committed JSON snapshot envelopes shaped as { "fetchedAt": string, "data": ... }.

System map

Portfolio routes → typed portfolio data → Astro static HTML
Developer HQ routes → public/data/*.json snapshots → Astro static HTML + optional islands
GitHub Actions → npm ci → snapshot fetchers with warnings → npm test → blocking typecheck → build → Pages

Developer HQ subsystem

Developer HQ is operational evidence, not the homepage. It links repository health, development board, discussions, docs, labs, legacy dashboard, and visualizer compatibility routes.

Content model

Projects and case studies live in src/data/portfolio.ts with evidence levels: verified-public, documented-design, active-development, and concept-research.

Deployment and rollback

Rollback by reverting the portfolio overhaul PR on the protected branch, rerunning Pages, and confirming static routes still build. No Terraform Cloud variables or secret values are stored in this repository.

Visualization compatibility

The visualizer remains a compatibility route for static diagrams. Illustrative graphs are labeled as non-authoritative and never represented as live control-system telemetry.