ReleaseWitness

Open source · MIT · file-first

Multi-agent work,
under control.

Give one supervisor a goal. Give every worker a clear scope. Keep the plan, evidence and next action in the repository.

Start with one prompt See the architecture
Illustration of ReleaseWitness preserving evidence and release checks around an AI coding workflow.
Evidence, source identity and release durability in one local trail.
assurance gate01 / 04
GOALShip with inspectable proof
01evidence
02review
03source QA
04release
next actionVerify the repository state
Every claim has provenance.
Every gate is inspectable.
01Find your path

Start where you are.

Search the docs for a workflow, a runtime or a command.

Popular:first runCodex + Claude + Antigravityworker loopproduction gate
02Choose a route

The shortest path
to useful work.

ReleaseWitness turns coordination into a visible repository protocol. Pick the role that matches your next question.

New here?Follow the hands-on startCopy the prompt, register real runtimes and watch the first task move through the system.Open the guide Understand itRead the control planeSee how context, DAG, scopes, mailboxes, evidence and checkpoints fit together.View architecture Run itOperate with confidenceUse the CLI, report evidence, debug failures and keep the autopilot cycle bounded.Open operations
03The loop

A team that
leaves a trail.

The supervisor keeps the project moving without hiding the work. Every cycle has a bounded next action and a durable resume point.

See a cycle in action
  1. 01
    Context

    Read the compact knowledge ledger before opening code.

  2. 02
    Plan

    Turn the goal into scoped tasks with dependencies and acceptance.

  3. 03
    Handover

    Workers pull from a mailbox and report files, checks and blockers.

  4. 04
    Gate

    Review, QA and production evidence decide what happens next.

Ready when you are

One light prompt.
A project with memory.

Open the quickstart