Week 33 · 10–16 Aug 2026
The documentation site was rebuilt over the source repositories, the chat agent gained tracing, and the specification described each platform.
· Written
- PRs opened
- 86
- PRs merged
- 81
- PRs closed unmerged
- 1
- PRs reviewed
- 0
- Issues resolved
- 0
- Active repositories
- 6 of 7
Counts cover 10–16 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.
The busiest week so far, most of it from Friday to Sunday. The documentation moved to a site of its own that brings together the specification and the reference stack, the website's chat agent gained tracing and a knowledge base that refreshes itself, and the specification gained a reference page for each of the twelve platforms. The teaching material also began. Written retrospectively from the project's history.
What we worked on
- Platform specification. We added a reference page for each of the twelve platforms in the stack and specified how agent memory is governed, with a single curator committing what is kept.
- Website and docs. The documentation moved to its own site, built from the source repositories and organised around what a reader is trying to do. The website gained platform detail pages, and its chat agent gained tracing, usage tracking and clearer citations.
- Agents and runtime. The chat agent's knowledge base now refreshes automatically when the documents change, one document at a time, and its answers favour prose over fragments.
- Reference stack. The automation that keeps the repositories' generated overviews and the knowledge base up to date moved onto the project's own hardware.
- Content. The first teaching material was written, with a study plan.
- Brand. The shared design system reached its first complete version, and the documentation site took on its colours and mark.
13-Aug-2026
- Content. The first teaching material was written for the platform.
14-Aug-2026
- Website and docs. Documentation publishing moved to a site of its own, built from the source repositories.
- Agents and runtime. The chat agent gained tracing, usage tracking, more reliable answers and clearer citations.
- Content. The teaching material gained a study plan, revised after a full read from start to finish.
- Brand. The shared design system reached its first complete version.
15-Aug-2026
- Reference stack. The automation that refreshes the repositories' generated overviews moved onto the project's own hardware, and the runners behind it were documented.
16-Aug-2026
- Platform specification. We added a reference page for each of the twelve platforms and specified how agent memory is governed, with a single curator committing what is kept.
- Agents and runtime. The knowledge base now refreshes automatically, one document at a time, whenever the documents change, and answers favour prose over fragments.
- Website and docs. The website gained platform detail pages and more suggested questions. The documentation site was reorganised around what a reader is trying to do and took on the design system's colours.
Still in progress
- The chat agent's answer quality is being measured and improved.
- The teaching material is being extended chapter by chapter.
Looking ahead
Next we turn to measuring how well the chat agent answers, so improvements can be checked rather than assumed. The specification and the teaching material continue alongside.