kidus-tiliksew/conveyor

Intent on paper, agents on the line, and every merge remembers why.

8

stars

1,315

commits

Go

primary language

Sep 7, 2026

updated

README

Conveyor

Generating code is easier than ever. Checking that the code matches product intent is now the bottleneck, and it is a bottleneck that gets worse as agents get faster: a queue of unsupervised agents can ship more unread code per day than a team can read.

A software factory is the answer to this shape of problem. You do not inspect every screw; you fix the process so that inspection happens at the points where mistakes can happen, and you make every unit traceable so that when something is wrong you know what else is affected.

Conveyor is a software factory for agent-written code.

It queues work from Requirements, System Design documents, and Decisions. Human operators confirm the documents, and approve plans when required. Agents on your machines plan, implement, and review that work.

Conveyor has used this process to build itself since July 2026.

Contributions go through the factory too. To start contributing, request access first by opening an issue, and you will get a workspace account to plan and pick up work from.

The Conveyor board with tasks in planning, implementation, review, and verification
Task board
A confirmed System Design document with its architecture diagram
Confirmed System Design
A requirement with a delivery drift signal awaiting operator judgment
Requirement drift
A merged task with its plan, pull request, and lineage
Task plan and lineage
A task timeline with changes requested and the following implementation round
Review feedback returning to implementation
The MCP setup dialog for coding clients
MCP client setup

The knowledge graph

Conveyor links each change to the documents, task, review, and test evidence behind it.

flowchart LR
    intent["Confirmed requirements<br/>and designs"] --> task["Task"]
    task --> delivery["Delivered change"]

    intent -.-> check{"Misalignment checks"}
    delivery -.-> check
    repository["Observed repository"] -.-> check

    check -->|mismatch found| signal["Signal"]
    signal --> followup["Judgment or gated follow-up"]
    followup -->|re-enters the factory| task

Conveyor checks each delivery against confirmed requirements and governing designs. When a delivery and its confirmed intent disagree, Conveyor raises a signal. Repository drift and post-merge failures raise signals too. Conveyor never rewrites code or documents on its own. An operator can acknowledge the signal or send follow-up work through the normal gates.

Architecture

   Operators in a browser              Agents such as Codex or Claude
             |                                      |
      React dashboard                       MCP work-order server
      board, tasks, docs                    claim, plan, review
             |                                      |
             +------------------+-------------------+
                                |
                         conveyord in Go
                  REST API, dashboard, event log
                                |
                           PostgreSQL
                  events, documents, links, queue
                                |
                    conveyor worker on your machine
                       supervises your agent CLIs
                                |
                    Git worktrees, repositories, PRs

conveyord is one Go binary. PostgreSQL stores the event log, documents, lineage projection, and River queue. The worker launches agent CLIs with your local credentials.

Installation

A factory host needs PostgreSQL 15 or newer, Git, an authenticated gh CLI, an API key for an OpenAI-compatible model endpoint, and the agent CLIs you plan to run.

Install the latest conveyor and conveyord binaries into ~/.local/bin:

curl -fsSL https://raw.githubusercontent.com/kidus-tiliksew/conveyor/main/install.sh | sh

The installer verifies the release checksum before replacing either binary and does not need sudo. Pinning a reviewed version, building from source, and upgrades are covered in Installation.

From there, Getting started (solo) stands up a factory end to end on one machine, and Getting started (multiplayer) covers a shared team server.

Documentation

Full docs live in docs/. There's no docs site yet.

Getting started

Guides

The factory

  • Concepts: the software factory, the knowledge graph, light and dark factory patterns
  • The document corpus: requirements, System Designs, decisions, and the propose-confirm cycle
  • Tasks: how work is created, given context, executed, reviewed, and linked
  • Misalignment: drift, staleness, and pending proposals

Operations

Playbooks (installable as agent skills with conveyor skills install)

  • Planning: draft and push documents from a local agent session
  • Task filing: file well-formed tasks and dependency chains
  • Working a task: the claim, checkout, submit, review lifecycle

Status

Conveyor is under active development. Its event log records defects and reconciliation work alongside successful merges.

License

Conveyor is available under the MIT License.

Contributors

kidus-tiliksew

1,297 commits

v0

12 commits

claude

5 commits

vercel[bot]

1 commits

kidus-tiliksew/conveyor

Intent on paper, agents on the line, and every merge remembers why.

8

stars

1,315

commits

Go

primary language

Sep 7, 2026

updated

README

Conveyor

Generating code is easier than ever. Checking that the code matches product intent is now the bottleneck, and it is a bottleneck that gets worse as agents get faster: a queue of unsupervised agents can ship more unread code per day than a team can read.

A software factory is the answer to this shape of problem. You do not inspect every screw; you fix the process so that inspection happens at the points where mistakes can happen, and you make every unit traceable so that when something is wrong you know what else is affected.

Conveyor is a software factory for agent-written code.

It queues work from Requirements, System Design documents, and Decisions. Human operators confirm the documents, and approve plans when required. Agents on your machines plan, implement, and review that work.

Conveyor has used this process to build itself since July 2026.

Contributions go through the factory too. To start contributing, request access first by opening an issue, and you will get a workspace account to plan and pick up work from.

The Conveyor board with tasks in planning, implementation, review, and verification
Task board
A confirmed System Design document with its architecture diagram
Confirmed System Design
A requirement with a delivery drift signal awaiting operator judgment
Requirement drift
A merged task with its plan, pull request, and lineage
Task plan and lineage
A task timeline with changes requested and the following implementation round
Review feedback returning to implementation
The MCP setup dialog for coding clients
MCP client setup

The knowledge graph

Conveyor links each change to the documents, task, review, and test evidence behind it.

flowchart LR
    intent["Confirmed requirements<br/>and designs"] --> task["Task"]
    task --> delivery["Delivered change"]

    intent -.-> check{"Misalignment checks"}
    delivery -.-> check
    repository["Observed repository"] -.-> check

    check -->|mismatch found| signal["Signal"]
    signal --> followup["Judgment or gated follow-up"]
    followup -->|re-enters the factory| task

Conveyor checks each delivery against confirmed requirements and governing designs. When a delivery and its confirmed intent disagree, Conveyor raises a signal. Repository drift and post-merge failures raise signals too. Conveyor never rewrites code or documents on its own. An operator can acknowledge the signal or send follow-up work through the normal gates.

Architecture

   Operators in a browser              Agents such as Codex or Claude
             |                                      |
      React dashboard                       MCP work-order server
      board, tasks, docs                    claim, plan, review
             |                                      |
             +------------------+-------------------+
                                |
                         conveyord in Go
                  REST API, dashboard, event log
                                |
                           PostgreSQL
                  events, documents, links, queue
                                |
                    conveyor worker on your machine
                       supervises your agent CLIs
                                |
                    Git worktrees, repositories, PRs

conveyord is one Go binary. PostgreSQL stores the event log, documents, lineage projection, and River queue. The worker launches agent CLIs with your local credentials.

Installation

A factory host needs PostgreSQL 15 or newer, Git, an authenticated gh CLI, an API key for an OpenAI-compatible model endpoint, and the agent CLIs you plan to run.

Install the latest conveyor and conveyord binaries into ~/.local/bin:

curl -fsSL https://raw.githubusercontent.com/kidus-tiliksew/conveyor/main/install.sh | sh

The installer verifies the release checksum before replacing either binary and does not need sudo. Pinning a reviewed version, building from source, and upgrades are covered in Installation.

From there, Getting started (solo) stands up a factory end to end on one machine, and Getting started (multiplayer) covers a shared team server.

Documentation

Full docs live in docs/. There's no docs site yet.

Getting started

Guides

The factory

  • Concepts: the software factory, the knowledge graph, light and dark factory patterns
  • The document corpus: requirements, System Designs, decisions, and the propose-confirm cycle
  • Tasks: how work is created, given context, executed, reviewed, and linked
  • Misalignment: drift, staleness, and pending proposals

Operations

Playbooks (installable as agent skills with conveyor skills install)

  • Planning: draft and push documents from a local agent session
  • Task filing: file well-formed tasks and dependency chains
  • Working a task: the claim, checkout, submit, review lifecycle

Status

Conveyor is under active development. Its event log records defects and reconciliation work alongside successful merges.

License

Conveyor is available under the MIT License.

Contributors

kidus-tiliksew

1,297 commits

v0

12 commits

claude

5 commits

vercel[bot]

1 commits

Languages

Go

79.7%

TypeScript

19.4%