Everything the loop is made of.
Six parts, in the order a merge goes through them. Every screen below is the hosted alpha, following one goal that landed.
Request an inviteSay what done means.
One sentence, and done-means lines the gate can score. A goal owns its number; its attempts are 7.1, 7.2. Bring a GitHub issue if that is where it started, or leave the lines empty and Sigbound AI drafts them from the sentence and the tree.
A branch is an attempt.
Any agent or person claims a goal and pushes a branch. Every push and every landing is a signed row in the repository's ledger, and pushes on one branch fold into one attempt, not four.
A cited read of the exact head.
On every push, Sigbound AI reads the head against each done-means line and cites every claim to a file and a line. It answers pass, fail, or needs a person. It never approves.
Your workflow, in a sandbox.
The workflow file you already have, in the GitHub Actions format, run in an isolated sandbox per run. One check per job at the head, logs by step, artifacts kept by digest.
A person approves the evidence.
One page, one decision: approve, or send it back. Whoever made the attempt cannot approve it; the gate refuses that before it reaches you. Held paths always need a person, however the checks look.
The gate re-verifies, signs, and lands it.
The same bytes are verified once more, land on main, and the merge is signed: the goal, the evidence, who decided, and the commit main moved to. Anyone can verify the record offline, without Sigbound.
The rest of it
Everything a repository needs around the loop. Each one has a page in the docs.
Every CI run, Sigbound AI read and verify run in one ledger, each with its log.
What a workflow uploads, kept by digest; the download is the exact bytes.
A pinned commit with a verified merge record behind it.
A job that names an environment deploys to it; a declared one can name reviewers, hold for a timer, and accept only some branches.
Written once and never shown again, scoped to a repository or an environment, masked in the log.
Watched branches, paths that always need a person, and a break-glass that goes on the record.
Signed deliveries of every event.
Repositories and issues, with a plain list of what does not carry over.
Several attempts at one goal, side by side.
A repository or a space over 7, 30 or 90 days: what went through the gate, and what it cost.
What needs you, and where it arrives.
sigbound: login, do, attempt, goal, verify. Every tool the API has, from a terminal.
The same tools offered to Claude Code, Codex, or any harness that speaks MCP.
Tokens, one version header, and deprecations that say so.
Your data, a space as one file, and closing an account yourself.
Then see it move
Follow goal 7 from the sentence to the signature. How it works
Connect Claude Code or Codex in one line, state a goal, and watch the same screens fill in. For your agents