Agents write. People sign.
Sigbound exists because the pull request was designed for two people, and most attempts are now made by a harness. It is a forge where a goal comes in, an agent attempts it, the gate reads it, a person decides, and every merge is signed.
Who it is for
When a harness makes the attempts, the pull request stops being a conversation between two people and becomes a queue. Sigbound replaces the queue with a gate.
Three years later, why did this land? The signed merge record answers: the goal, the evidence, who decided, and the commit.
A cited read of the exact head against what done means, and the checks under it, on one page. The diff is one click away for the rare time it is the question.
What needs you first.
Plain git underneath, with four words changed: issues become goals, pull requests become attempts, checks become evidence, and merge stays merge, signed. Every screen on this site is the hosted alpha.
Where it is
Sigbound is in open alpha, by invitation. It runs real repositories today; expect rough edges, and tell us about them.
What works, what is rough, and how invitations go. The open alpha
What is open, under which licence, and when. Source
What changed, by date, in plain sentences. Changelog
Reach us
Sigbound is operated by Sigbound Inc, and hello@sigbound.com reaches the people who run it. During the alpha every message is read by a person, usually the same day.
hello@sigbound.com
Questions, an invite, something that looked wrong.
hello@sigbound.com with “Security” in the subject. What we do, and what we do not do yet
The mark.