Skip to content
208SoftwareSolutions

Product

From card to pull request,
under supervision.

An orchestration layer for Claude agents: it watches your board, runs the role the card calls for, completes the work and opens a pull request. Nothing moves forward without passing the policy and verification gates — working autonomously is not the same as working unsupervised.

internal use · early access
12:04:18 CardPoller — 3 kart alındı
12:04:22 PolicyGuard — geçti (main'e push yok)
12:11:07 AgentRunner — 14 dosya değişti
12:19:41 VerificationGate — build ✓ test ✓
12:19:55 GitPublisher — feature/pr-248
12:20:02 GitHubClient — PR #312 açıldı
12:31:18 PolicyGuard — #250 durduruldu: şema silme

How it works

Five stops, two gates.

The output of every step is visible on the card. Agents never talk to each other; the state of the card is their only channel.

  1. 01

    Card is picked up

    The board is scanned at regular intervals. Which column triggers which role is defined in advance.

  2. 02

    Policy gate

    Work that touches a hard boundary is stopped here and routed to human approval.

  3. 03

    Agent runs

    Depending on the role, the analyst, developer or test agent takes over.

  4. 04

    Verification gate

    Build and tests are run independently. An agent's own report does not count as verification.

05 · PR is opened

The branch is pushed, a pull request is opened and the card moves to the next column.

Safety by design

Autonomous
does not mean unsupervised.

What agents may not do is blocked at code level. A warning in an instruction is not a control mechanism.

Gate 01

Policy gate

Writing directly to the main branch, skipping control steps, touching configuration and deployment files, bulk data updates — all blocked.

Gate 02

Verification gate

Every repository carries its own verification command. Build and tests are run independently; if the result is not clean, the branch is not pushed.

Safeguard

Database discipline

Schema changes go through a separate runner and are reported. Bulk correction scripts are written but never executed automatically.

Why we built it

It was our own team's
concrete bottleneck.

PrimoRoute had three repositories, a single production database and a board in constant motion. Small but repetitive work was consuming a significant share of the team's time. Orchestrator took that work over — without loosening a single safety rule in the process.

.NET 8SQLiteGitHub APITrello APIMailKitClaude Agent SDK

Automate your delivery pipeline
without giving up control.

Join the early access list and we will set it up with you.