Your first hour

From signing in to a room with a project in it. About ten minutes of your attention; the rest is your CI working.

1. Sign in

Constat signs you in with GitHub. It asks for nothing else, and it stores no password of yours.

2. Start an organization

The first screen after signing in asks one question: what is it called.

Under the name you will see four seats — Author, Judge, Reader, Agents — and which of them are already yours. Being alone in the room is fine, and the screen says so: the record still carries your name on every verdict, and nothing you seal today changes when others join.

One field, one button.

3. Add a project

A project is one piece of software. Constat offers two ways in.

An app that exists. Point at its GitHub repository. Constat asks you to install a small read-only app on it, then reads what its CI already publishes. See Bring a project you already have.

A new app. Start from a template Constat can witness from its first commit, with CI, the runner and the first requirement already inside. See Start a new app.

The screen also prints, plainly, the stacks Constat cannot witness yet. If yours is on that list, it tells you now rather than after your first attempt.

4. Let it read the repository

Whichever door you took, Constat now reads the repository and tells you one of three things.

Ready. Its CI already publishes what Constat needs. Nothing to do.

Something is missing. It names each missing piece in plain words — no script that runs the tests with a machine-readable report, no workflow publishing it — and gives you one line to run that writes those files to a branch and opens a pull request in your name. You merge it. Constat notices the merge the next time it looks, and the page turns green on its own.

It cannot read the repository. Almost always the app is not installed on it yet. The page says so and links to where you fix it.

5. Add one secret

Your agents need a key, and it is yours, not Constat's. The page prints the name of the secret and where to put it in GitHub.

Constat records the name and never sees the value. It does not ask GitHub which secrets you hold, so it will keep saying not checked beside that line — that is honesty, not a bug.

6. Write your first requirement

One ask, in your words, with the rules it should be judged by. Keep it to one screen or one behaviour; Constat's own experience is that a requirement too large for its envelope dies at the cap rather than being judged.

Approve it. The words freeze.

7. Dispatch

Press Dispatch. Constat queues the work; the runner in your repository picks it up and runs your agent, on your CI, with your key.

When the evidence has settled, the door opens and you are told. Then you read what CI saw and decide.

From here on, the loop is the same every time.

This project is empty. What comes first?

Write one requirement: what you want, in a sentence, then the criteria you will judge it by, one per line, each saying how it will be seen. Approve it as its judge, and the queue starts the first attempt by itself. If the project has no judge yet, name one on the People page first.