A five-minute tour of Inside

• The top row has the three sites, each with its gate result, the time from push to live and its open findings. The values are read from the records each site publishes, when the page loads.
• Further down: the latest published pieces, a deploy feed of the last 12 runs, the apps, and five Grafana dashboards (deploys, Claude Code, local LLM, search engines, host).
• One search box in the top bar covers the docs, the services and every page on the map. The / key moves the cursor there.

In your company: the one page a new hire opens first, with what is live, what shipped today, where the docs are, and one search over all of it.

• Open Inside
• Dashboards
• Search

• The catalog has 12 services, one YAML file each. The build stops when a file has no owner, tier, lifecycle, or list of docs and runbooks.
• Local LLM has an owner, tier 3, lifecycle production, its Grafana dashboard, three docs and two SLOs with targets: 99% of requests without an upstream error, and 95% of streamed requests with a first token within 4 s.
• Its runbook list is empty, and the page shows "No runbook yet". The Conformity gate, a tier 1 service, links two runbooks.

In your company: every service has a named owner, a tier that sets what gets fixed first, and its dashboard, runbooks and SLOs one click away, so the person on call starts from one page.

• Open the service page
• All 12 services
• Conformity gate

• Six spaces: Engineering, Observability, FinOps, Research, SRE Handbook, Standards and Compliance. Each hand-written page names an owner, the date of its last review, the date of its next review and its type (tutorial, how-to, reference or explanation, after Diátaxis), with a link to report an issue.
• ADR-0002 records why a deploy waits for the checks: context, decision, consequences, status accepted. The decision records are numbered from ADR-0001; three are superseded and stay, each with a link to the record that replaced it.
• The docs health page lists pages past their review date, due within 30 days, without an owner or without a type. On 2026-10-09 none was late and none lacked an owner; the pages imported from the knowledge vault are marked as never reviewed.

In your company: docs that name who keeps them correct and when they were last checked, and one page that lists the ones going stale.

• Open ADR-0002
• All six spaces
• Decision records
• Docs health

• The entry: Prometheus reported USD 1,970,946.62 of Claude Code spend for a week whose per-request events sum to USD 1,003.45 at list price. No money moved; the meter was wrong, and the spend alert had been in firing state 73% of the time.
• The cause, from the write-up: up to about 12 parallel Claude Code processes wrote one counter series, so each export from a process with a lower total counted as a reset, 230,328 times in a week.
• The trail: the write-up with timeline and lessons, a runbook with the check queries, the fix in agent-observability c163b42 (spend and the alert now summed from per-request events), and ticket #29 on the board for the follow-up that is still open.

In your company: each incident leaves the same trail, with a status entry, a blameless write-up, a runbook for the next time, the fix commit and a ticket for the open work.

• Open the status entry
• Write-up
• Runbook
• Ticket #29
• Fix commit

• On 2026-10-08 at 14:05 UTC a push to the map page failed the link check, because a link was written inside a JavaScript template string. The conformity job failed, the deploy job was skipped, and readers kept the previous build.
• Finding F-1753a6d2d038 was opened on that commit and closed at 14:06:59 UTC, when the fix passed. Closed findings stay on the conformity page; the history of every run is kept in git. The status page records the same event as an incident with no reader impact.
• Every push to the three sites runs the same checks before the deploy. They test the mechanical requirements of a working draft, Continuous Conformity for Deployed AI Systems (draft 0.3, 36 requirements), published as a reference text.

In your company: a release that fails a check stops before customers see it, and the record shows which check failed, on which commit, and when the fix passed.

• Open the blocked run
• Conformity record
• Status entry
• The definition draft

• The FinOps space has six pages under one index: cost model, unit economics, showback, the anomaly from stop 4, budgets and alerts, and a FOCUS-format CSV export.
• Showback: Claude Code usage from 2026-10-01 15:21 UTC to 2026-10-09 00:00 UTC came to USD 1,021.01 at list price over 5,505 API calls. The billed amount is a flat subscription.
• The map shows every page, post, repository and thread across four sites, plus the docs, services and dashboards, with the links between them.

In your company: spend per team and per service from the usage data you already have, and one view of what exists and what links to what.

• Open the FinOps space
• FOCUS export (CSV)
• Open the map