Board
The work on machinebehavior.io and the platform behind it. Each card is an issue on the public repository; GitHub Issues is the system of record and this page is a snapshot of it.
Issues as of the last build, 2026-10-09; the snapshot of the last deploy loads in the browser.
Backlog 8
- #40 CI check: generated pages match their sources
- #39 Toil: the bot commit on main forces a rebase before every push
- #25 Retention statement for the metrics and log stores
- #24 Accessibility pass to WCAG 2.2 AA
- #23 Withdrawn-page pattern
- #22 Postmortem index
- #21 Onboarding path for a new engineer or agent session
- #20 Templates space
Ready 4
In progress 0
Blocked 6
Done in the last 30 days 26
- #44 Home page as the portal front page
- #43 Structured data: Person, WebSite with search, Article and TechArticle, DefinedTermSet
- #42 Mission Control at /inside/mission-control/
- #35 SRE principles in practice: one page per principle, linked to the services that apply it
- #34 One design system: tokens and component CSS, reading and app layouts
- #33 Topic hubs at /topics/<topic>/
- #32 Section sidebars for Research and Inside
- #31 One navigation source: site/nav.yml, one top bar, breadcrumbs on every page
- #30 Founder tour at /inside/tour/
- #28 Left sidebar for Inside pages
- #19 Numbered decision records and a changelog
- #18 On-call and escalation page, and Alertmanager
- #17 Access model page and public demo banner
- #16 One top bar and one search
- #15 Status page at /inside/status/
- #14 Owner and review date on every docs page
- #13 Service catalog at /inside/services/
- #9 Report an issue link on every docs page
- #8 Ticket board at /inside/board/
- #7 FinOps space in the docs
- #6 SearXNG search engines dashboard on Inside
- #5 Remove internal host details from the public dashboards
- #4 No third-party requests on page load
- #3 Inside and infrastructure in the menu on every page
- #2 Docs pages in the map of the work
- #1 Docs tree at /inside/docs/
How the board works
The column comes from the status label on each issue: status: ready, status: in progress or status: blocked. An open issue without one sits in Backlog; a closed issue is Done for 30 days. Labels also set the type, the area and the priority, P0 first. The same issues, with those of the other public repositories, by area of the CTO job: the cockpit.
The deploy job reads the issues from the GitHub API and writes issues.json next to this page, so opening the board sends no request to GitHub. New reports appear here once a maintainer gives them a type label. Details, labels and the workflow: Ticket board in the Engineering docs.
Inside board · data: issues.json, written at each deploy from GitHub Issues by board_snapshot.py