Synedrix OS
Engineering Room

Week 22 · 25–31 May 2026

A quieter week on the self-hosted stack, prepared for an NVIDIA DGX Spark with adjusted databases and dashboards.

· Written

PRs opened
0
PRs merged
0
PRs reviewed
0
Issues resolved
0
Active repositories
2 of 5

Counts cover 25–31 May 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 quieter week, spent mostly on the self-hosted stack. We prepared it to run on an NVIDIA DGX Spark, adjusted its databases and pointed its dashboards at the long-term metrics store, and on Sunday set up workflows as code for the workflow engine. Written retrospectively from the project's history.

What we worked on

  • Reference stack. We prepared the self-hosted stack to run on an NVIDIA DGX Spark, adjusted its databases for local development and pointed its dashboards at the long-term metrics store.
  • Agents and runtime. We set up workflows as code for the workflow engine, with an agent that helps author them.

26-May-2026

  • Reference stack. We added configurations for running the self-hosted stack on an NVIDIA DGX Spark, with improvements to its observability.

27-May-2026

  • Reference stack. The time-series database's file limits were raised, and the local database setup gained an MCP configuration for development.

30-May-2026

  • Reference stack. The workflow dashboards were pointed at the long-term metrics store.

31-May-2026

  • Agents and runtime. We set up workflows as code for the workflow engine, with an agent that helps author them.

Still in progress

  • The stack's configuration for the new hardware is being tested.
  • The runbook for the self-hosted stack is being updated.

Looking ahead

Next we turn to running the stack on the new hardware. Specification work resumes alongside.