Week 40 · 28 Sep–4 Oct 2026
The specification took on tenancy, identity and metering, plan governance gained its specification stage, and the website was checked for launch.
· Written
- PRs opened
- 93
- PRs merged
- 77
- PRs closed unmerged
- 5
- PRs reviewed
- 62
- Issues resolved
- 4
- Active repositories
- 7 of 8
Counts cover 28 Sep–4 Oct 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 heaviest specification week so far. The platform gained a tenancy model, with specifications for tenancy and for identity and access, a tenant key on every event, and stricter separation of tenant data. Metering, authority and autonomy followed by Sunday. Plan governance gained its specification stage, and the website had an accuracy pass ahead of launch. Written retrospectively from the project's history.
What we worked on
- Platform specification. We adopted a tenancy model, with new specifications for tenancy and for identity and access, a tenant key on every event, and stricter separation of tenant data. A metering and entitlement specification followed, together with authority conventions and autonomy levels for the agents.
- Governance. Plan governance gained its specification stage, with intent and specification templates, sandbox checks, request-to-plan traceability and a roadmap to its first complete version. Every repository now requires the project's own account for commits and changes, and gained AI code review on request.
- Domain packs. The trading schema was rebuilt on the platform's tenant-safe tables.
- Agents and runtime. Each agent invocation is now recorded from start to outcome.
- Website and docs. The website had an accuracy pass ahead of launch, with clearer home page diagrams and the product named consistently.
29-Sep-2026
- Governance. Plan governance gained request-to-plan traceability scoring, incident records for the maintenance stage, and a roadmap to its first complete version.
30-Sep-2026
- Governance. We drafted plan governance's specification stage, with intent and specification templates, authoring and reviewing skills, and sandbox checks.
01-Oct-2026
- Governance. Every repository now requires the project's own account for commits, pushes and changes on GitHub.
- Platform specification. The vocabulary, the responsibility matrix and the layer taxonomy were brought up to date.
02-Oct-2026
- Platform specification. We adopted a tenancy model, with new specifications for tenancy and for identity and access, a tenant key on every event, and stricter separation of tenant data.
- Domain packs. The trading schema was rebuilt on the platform's tenant-safe tables.
03-Oct-2026
- Agents and runtime. Each agent invocation is now recorded from start to outcome.
- Governance. The repositories gained AI code review on request.
04-Oct-2026
- Platform specification. We drafted a metering and entitlement specification, set authority conventions and autonomy levels for the agents, and completed the data-plane schema.
- Website and docs. The website had an accuracy pass ahead of launch, with clearer home page diagrams and the product named consistently.
Still in progress
- The tenancy and metering specifications are being reviewed.
- Plan governance is working towards its first complete version.
- The website is being prepared for launch.
Looking ahead
Next we turn to settling the tenancy and metering specifications. The website's launch preparation continues alongside.