the-loopThe loop for everything!

An opinionated product-development lifecycle, shipped as an executable process graph and a daemon that runs it. Nodes are the steps, hooks are the checks at their boundaries, edges route on outcomes — so the process is a declaration, not a habit.

What is the-loop?

Quickstart

the-loop CLI

Python SDK

View on GitHub

Two loops, one process

An outer loop per work item (brainstorm → requirements → design → testing plan → tasks → implementation → verification → review → complete), running in the repository the ticket was created in, and an inner loop per pull request — one per contributing repository, each in its own session. They meet at one seam: the work item waits until every pull request delivering it has finished.

How the graph works

The process is executable

Both loops ship as data inside the CLI. A gate reads checked-in artifacts, never prose; a claim carries no verdict; a forced transition moves the pointer and never forges a result. The graph assigns work as well as judging it.

A CLI that drives it

A lightweight, extensible Python CLI (the-loop) turning ticket and pull-request activity into agent runs: webhook and poll ingress, one record per work item with a session per pull request, execution control, and a structured event log.

Explore the CLI

Or embed it in your own service

The same package is importable. the_loop.sdk mounts the control plane's own router into a FastAPI app you already deploy — behind your auth, your middleware and your lifespan, in one process — or drives the capabilities directly with no HTTP at all.

Embed the-loop

Gated, reviewed, documented

Every phase is gated by human review, and testing is planned before it is executed. Every decision leaves a paper trail. Capability docs and the user-facing docs are updated in the same pull request as the change that made them wrong.