Sirius Forester_
The local foreman for parallel coding agents.
An orchestration layer that claims work, locks impacted code, runs agents, gates completion on tests, and records a receipt for every change.
How it works
Claim one task
Lock code and run agent
Gate tests and file receipt
The problem
Parallel coding agents create a new coordination problem: two workers can take the same task, collide in the same code, skip the tests their changes affect, or leave no durable explanation of why something changed.
Sirius Forester is a supervisor loop for that work. It does not replace the issue tracker, code graph, agent, or CI system. It connects them and enforces the contract between them.
The enforced loop
- Claim one task from Ametrite.
- Lock the relevant code through Hayvenhurst.
- Run the configured coding agent.
- Select and execute affected tests.
- Refuse completion when the gate fails.
- Write a two-way receipt connecting the task, symbols, decision, and resulting change.
Everything runs locally. Sirius writes only its own SQLite ledger and communicates with companion tools through their public CLI contracts.
Sothis
Sirius is the foreman of Sothis, a local-first suite for serious agentic engineering:
- Ametrite owns tasks, decisions, and shared knowledge.
- Hayvenhurst understands code structure, impact, and conflicts.
- Catryna Wikinelli keeps repository-native documentation current.
- Sirius Forester supervises the execution and verifies completion.
Supply-chain posture
Release artifacts include SHA-256 checksums and Sigstore signature bundles. Installers fail closed on a bad or missing signature bundle when verification is available, and the documentation explains both the guarantee and its limits.
Current status
Sirius is early alpha. Its six commands are implemented, its suite runs offline, and CI covers macOS, Linux, and Windows.