Synedrix OS
Engineering Room

Week 42 · 12–18 Oct 2026

A week on how documentation is approved for release, with new design proposals for the client application, process governance and manifests.

· Written

PRs opened
159
PRs merged
155
PRs reviewed
63
Issues resolved
6
Active repositories
8 of 9

Counts cover 12–18 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.

Most of the week went into how documentation reaches the public, and into a new round of design proposals. We built and tested a release process under which a page becomes public only once it has been marked and approved, and we added automatic checks that the code examples in the specification are valid. Alongside that, we opened proposals for the client application, for how processes are governed over their lifecycle, and for defining work in manifests. Synedrix OS is in active development, and most of this is design under review rather than running software.

What we worked on

  • Platform specification. We opened proposals for the client application, for process governance and its lifecycle, and for defining work in manifests, and began reviewing them.
  • Reference stack. We added a proof-of-concept agent to the self-hosted reference stack. It has not yet been run end to end.
  • Agents and runtime. We built out the hosted version of the site's assistant: startup checks, limits on each run, and a faster way to prepare its knowledge base.
  • Domain packs. We designed a domain pack and agent team for software engineering work, and built the first skills, tools and conformance checks for its agents.
  • Website and docs. The documentation site's release process and the automatic checks on code examples are in place, and the website's first page load is about half its previous size in local measurements.

12-Oct-2026

  • Website and docs. The site's assistant now answers only from the approved public release, and we set up the pipeline under which a page becomes public only once it has been approved.
  • Agents and runtime. The assistant gained explicit local and hosted modes with startup checks, and rebuilding its knowledge base now reuses passages that have not changed.
  • Reference stack. The proof-of-concept agent and its bridge to the workflow engine were brought up to date with current versions.
  • Governance. Documents became private by default, so only content that is marked and approved can be published.

13-Oct-2026

  • Website and docs. The first public documentation release went out after review, and the assistant began running inside the website with the approved release shipped alongside it.
  • Platform specification. We drafted the documentation publication workflow and the two review roles it relies on.
  • Agents and runtime. The assistant gained limits on each run and a daily purge of stored conversations.

14-Oct-2026

  • Website and docs. The documentation site moved to a new site generator with grouped navigation and icons, and the chat's source cards were reworked.
  • Platform specification. Every code example in the specification is now checked before it ships.

15-Oct-2026

  • Website and docs. The website now loads the chat only when it is needed and passed automated accessibility audits, and the documentation site gained a reference landing page.
  • Platform specification. We opened a proposal for the client application for review.

16-Oct-2026

  • Platform specification. We opened a draft specification for process governance and its lifecycle.

17-Oct-2026

  • Website and docs. The documentation export now catches more internal paths before anything is published.

18-Oct-2026

  • Domain packs. We designed a domain pack and agent team for software engineering work.
  • Agents and runtime. We built the first skills for the engineering agents, a check-only tool server, a plugin with guard hooks and a conformance suite that runs across clients.
  • Website and docs. Both sites gained HTML and JSON sitemaps, and the checks that decide what may be published were tightened.
  • Governance. Automated code review was made easier to observe, and its permissions were narrowed.

Still in progress

  • Review of the process governance and lifecycle specification continues.
  • Review of the manifest proposals and their draft specification continues.
  • The hosted assistant has not yet been checked in a production setting.

Looking ahead

Next we turn to the open proposals, working through their reviews in turn. The hosted assistant then needs checking in the setting where it will run.