Service status for the lab.
A status-page view for the site, APIs, and publishing system. It is intentionally modeled like a product status console, but stays honest about what is actually running in this repo.
All monitored site surfaces are green
The status board highlights the pieces the site actually depends on: published content, tools, APIs, and the build/publish path.
The published thesis and field notes are online and reachable.
Ask My Work, Research Lens, and the supporting routes are available.
The systems pages, stack maps, and project artifacts are intact.
What is up right now
These are the components that matter for visitors and for the publication workflow behind the site.
Static pages, navigation, and shared lab chrome are rendering normally.
Updated from the latest local build and previewed in browser QA.
The source-grounded research interface is available on the /ask route.
Backend responses stay constrained to the site context and uploaded notes.
The visitor-lens summaries and adaptive profiles are wired behind server routes.
OpenRouter-backed responses fall back to curated copy when unavailable.
Field notes, systems pages, and project write-ups are generated from the Gatsby source tree.
No external CMS dependency.
Production builds complete successfully; Gatsby still emits the known configstore EPERM warning in this sandbox.
The build output is still produced and verified in preview.
The static preview server is the fastest way to inspect the published output in this workspace.
Use it for visual QA after each significant UI change.
What was verified most recently
This section summarizes the last manual verification pass across the website and the lab pages.
Where to go next
The status page is a lightweight operations view. The other pages explain the systems and the active work behind it.