Week 14 · 30 Mar–5 Apr 2026
Agent registry, design principles and database schema written down, with human approval built in, and a repository for the self-hosted stack.
· Written
- PRs opened
- 3
- PRs merged
- 3
- PRs reviewed
- 0
- Issues resolved
- 0
- Active repositories
- 2 of 2
Counts cover 30 Mar–5 Apr 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 writing down how the agents and workflows were meant to fit together. We set out an agent registry, design principles and a database schema, with human approval built into the workflows from the start. At the end of the week the self-hosted reference stack got a repository of its own. Written retrospectively from the project's history.
What we worked on
- Domain packs. We documented the agent registry, design principles, workflow registry and database schema for the agentic trading workflows.
- Governance. We added workflows that hold sensitive steps until a person approves them.
- Reference stack. We created the self-hosted reference stack and placed it under the Apache 2.0 licence.
01-Apr-2026
- Domain packs. We documented the agent registry, design principles, workflow registry and database tables for the trading workflows.
- Governance. We added workflows that hold sensitive steps until a person approves them.
02-Apr-2026
- Domain packs. The database schema gained a row-level security baseline and scripts for seed data.
03-Apr-2026
- Reference stack. We created the self-hosted reference stack and placed it under the Apache 2.0 licence.
Still in progress
- The workflow engine's configuration for the self-hosted stack is being prepared.
- A home for the project's documentation is being planned.
Looking ahead
Next we turn to the self-hosted stack, so the workflows have somewhere to run. A place for the project's documentation follows.