Skip to content

Wayloop

Wayloop

Spec-driven agentic loop.

From idea to merged code, in your issues, with humans at the gates.

Wayloop runs a software project with coding agents, from the first idea to the merged pull request. Specifications capture intent, a deterministic loop moves the work forward, the plan lives in your issue tracker, and people decide at the gates.

How the loop works Architecture

Status

Pre-alpha. There is no release yet. The concept pages describe the design and state, on each page, what of it exists today. What comes next is in the roadmap.

  • The engine decides


    A state machine written in Rust chooses every step and verifies it with deterministic checks. A model never declares its own work finished.

    Architecture

  • Your tracker is the database


    Plan, progress, decisions and questions live in your issues; specifications live in the repository. Remove Wayloop and the project still reads.

    State in the tracker

  • Humans at the gates


    The loop runs unattended between approval states and stops at them, with a question in a fixed format on the issue.

    Gates

  • A deterministic ledger


    Append-only, hash-chained events. The state is a function of the ledger, and every session hands over a validated summary.

    Ledger

  • Greenfield and brownfield


    On an existing codebase, a survey maps the code and writes documentation that cites file and line for every claim. No embeddings.

    Brownfield survey

  • Tokens are a budget


    Every phase has a budget and the ledger measures the cost of each issue, so that the cost of the loop is known, not guessed.

    The loop

For agents

This documentation is also published as plain text for agents: llms.txt and llms-full.txt.