Who it is for

The product is the same for everyone. What changes is which seat is empty, and what the record is for.

A solo builder

You are the author and the judge. That is not a degraded case; it is the common one, and Constat is built for it. When you seal a record, it says author and judge: the same person — a declared trade rather than a hidden one, so a reader years later can weigh it for what it is.

What it gives you. An answer to the question you cannot answer alone at eleven at night: did the thing I asked for actually get done, or does the agent merely say so. The record remembers what you asked, in the words you asked it, from before the work started.

What to expect. One room, one project, one judge. Invitations and seats can wait. The first hour is about ten minutes.

A startup

Two or three people, one or two products, agents doing most of the typing.

What changes. The author and the judge start to be different people, and that is when the record earns its keep: the person who wrote the ask can tell whether what came back is what they meant, without reading the diff. A judge is named per project, so the person who knows the mobile app judges the mobile app.

What it gives you. A history you did not have to write. When somebody asks in three months why a thing works the way it does, the requirement is there in the words somebody chose at the time, with the evidence beside it.

What to expect. One room, several projects. Readers invited by email. The board — Where things stand — becomes the screen you actually live on, because it shows every requirement in exactly one cell, including the ones that are finished and going nowhere.

A company

Several teams, agents from more than one vendor, and somebody who has to answer for what shipped.

What changes. The record stops being a convenience and becomes the artefact. A sealed Constat is linkable, shareable with a client, and readable by somebody who has no account and no access to your code. The honesty ledger publishes how often an agent's claim contradicted what CI saw, and how often a door was held shut — numbers nobody else has, from a real deployment.

What it gives you. A boundary you can point at. Your harness accepts its own work; Constat is where a person does. That difference is the thing an auditor, a client or a board can be shown.

What to expect. Seats used properly: authors who write, judges named per project, readers who never sign in to anything but a link. Agents arriving through pull requests as well as through Constat's own runner, because a team running Devin, Copilot or Cursor should not have to change tools to get a record.

What does not change, at any size

Constat never runs your tests, never writes your code, and never accepts anything. A verdict is a person's, always, and the seal says whose.