Settings

Every switch, what it changes, and what it cannot change.

Yours

Your timezone. Set from your browser the first time you sign in, and changeable here. Every time Constat shows you — on a run page, a release, a sealed record, a notice — is in that zone, and each page names the zone once in words. The record itself stays in UTC underneath; only what you read changes.

Notices. Where Constat reaches you: your email address, and your organization's Slack webhook if it has one. A door opening is the notice that is not optional; the rest can be turned off.

The organization's

The sender. One email provider and one Slack webhook. Constat uses them for invitations and for telling judges a door has opened. Nothing else.

Visibility — private or public. Private is the default and means the public side of Constat cannot see the organization at all; it reads through a connection that has no access to it, so this is an absence rather than a check somebody could forget.

Public means anyone with the address can read, without an account: your requirements and their criteria, the attempts, the evidence with its sources, the seal numbers and the releases. It does not show what an attempt cost, nor a judge's name or reason.

Turn it on deliberately. A good way in is a second organization holding one finished project, so you can see exactly what a stranger sees before you decide.

The project's

Lanes. How many attempts this project may have in flight at once. One by default. Two attempts on the same requirement are never allowed whatever the number — that is the race lanes exist to prevent. What is single-file whatever the lanes say is the default branch: no attempt starts while a release is taking or merging a branch, and no release starts while an attempt is in flight, so the ground an attempt rebased onto never moves underneath it.

Where attempts run. GitHub's machines by default, or a runner of your own by its label. A label makes the wake stand rather than waiting to be pressed.

How it goes live. An address Constat watches after a merge, or nothing at all for a project that does not deploy.

The live address. Where Constat looks to see that a release is actually serving. Live is observed, never assumed.

The seal gates the merge. Off by default. Off, Constat writes its check run on the pull request as neutral, whatever the verdict, and nothing is blocked. On, a refusal fails that check, and the check's own summary says which mode it is in so nobody is misled.

Agents. Which agents this project may dispatch, and the name of the secret each one reads its key from. Constat records names, never values.

What no setting can do

No setting lets a machine accept work. No setting lets anybody edit what CI observed, or change a requirement's words after approval. No setting gives Constat permission to write your code — the witness holds read on contents and that is not configurable.