Week 31 · 27 Jul–2 Aug 2026
The website and the shared design system began, and the specification gained a machine-readable facts layer checked on every change.
· Written
- PRs opened
- 4
- PRs merged
- 4
- PRs reviewed
- 0
- Issues resolved
- 0
- Active repositories
- 5 of 7
Counts cover 27 Jul–2 Aug 2026 (UTC) across the project's tracked repositories. Pull request figures count only pull requests opened during these dates; merged, closed and reviewed mean that also happened within them, so one can count in more than one category. They count pull requests of any size, including many prepared by AI coding agents and some fully automated ones. Reviewed means a submitted review by someone other than the author, not approval.
A busy week in which two new pieces of the project began. The shared design system and the website were both started, the website with a first chat agent that answers from the knowledge base. The specification gained a machine-readable layer of facts, checked automatically on every change and used to generate its reference pages. Written retrospectively from the project's history.
What we worked on
- Platform specification. We added a machine-readable layer of facts to the specification, with a linter and generated reference pages checked on every change, and extended the metrics specification with platform mapping and service-level objectives.
- Website and docs. The website began with a first version of the marketing site and a chat agent that answers from the knowledge base, followed by a pass on mobile and tablet layouts. The documentation site gained clearer navigation and a dark mode.
- Brand. The shared design system was set up and grew quickly through the week.
- Content. We rewrote the tenth post in the blog series around its consequences for the reader, and set a fortnightly publishing cadence with rules against repetition.
- Reference stack. The reference stack now links back to the specification it implements.
28-Jul-2026
- Content. We rewrote the tenth post in the blog series around its consequences for the reader, and set a fortnightly publishing cadence with rules against repetition.
- Brand. The shared design system was set up and its first version brought in.
29-Jul-2026
- Platform specification. We added a machine-readable layer of facts to the specification, with a linter and generated reference pages checked on every change. The metrics specification gained platform mapping and service-level objectives, and the agent interaction patterns were expanded.
- Website and docs. The documentation site gained clearer navigation, icons and a dark mode.
- Reference stack. The reference stack now links back to the specification it implements.
30-Jul-2026
- Brand. The design system grew substantially, and places where the brand had drifted were brought back in line.
01-Aug-2026
- Website and docs. We built a first version of the marketing site, together with a chat agent that answers from the knowledge base.
02-Aug-2026
- Website and docs. The website's mobile and tablet layouts and its brand styling were refined.
Still in progress
- The website is being prepared for its first public version.
- The machine-readable facts are being extended to more of the specification.
Looking ahead
Next we turn to the agent registry and to getting the website ready to go live. The blog series continues on its new fortnightly cadence.