Settings

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

Yours

On Your settings, from the menu under your picture. Nobody else here can set any of it.

Your email. Where DoneMark writes to you. Leave it empty and it writes to you by no email at all.

Your timezone. Set from your browser the first time you sign in, and changeable here. Every time DoneMark 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.

Your hats. Which parts of the work come first for you — shown on Your settings, changed from Your hats in the same menu. A hat never changes what you may do. See What waits for you, and your hats.

When DoneMark calls you. For each moment — Ready to judge, Stuck, Went live — whether DoneMark emails you. At first it emails you when something is ready to judge or stuck, and not when a release goes live; tick or untick any of them, and the choice is saved at once. What waits for you is always in the app, in your waiting list and the count on every screen, whatever you choose. The team's Slack is one channel, set in Organisation settings, and nobody's choice changes what is posted there.

The organization's

On Organisation settings, under your organisation's name in the top bar: true for everyone here, in every project. Members, invitations and who judges which project stay on People; what it all costs is on Money.

Money, beside it under the organisation's name, is where Costs and the Ledger went. It has three sections. This month adds up every project: what the agents cost ("at least", since an attempt DoneMark could not price is never counted as free) against the monthly budget, and the CI minutes against the free minutes your plan gives, with one line per project. Where it went lists a project's attempts, each with what it built, who built it, how it ended, its tokens, its CI minutes and its cost. What the record says is the honesty numbers — claims contradicted, doors held shut, review minutes per accepted ask — and the week's progress. The last two read one project at a time; pick another beside their heading. The budget and the free minutes are changed here, in Organisation settings, and Money links to them.

Drafting "done when" lines. On or off for the whole organisation, and which model drafts them: Claude (Anthropic), OpenAI, Mistral, Kimi (Moonshot) or OpenRouter — any model OpenRouter carries, named as it names them (anthropic/claude-sonnet-5.5); for mockups drawn from your pictures, pick one that reads pictures — with the model's name, Test drafting to see it answer, and Save. Turned on, the words of a feature — its one line, the project's brief, the titles of its other features — leave for that model; never code, never a key. A draft approves nothing.

How the team is told. One Slack webhook for the organisation, shown masked. Each person's own email is on their own settings. The email sender is set on the server, never on a screen.

Money. A monthly budget for every project together, and the free CI minutes beside it. The budget counts what the attempts cost in AI, from the 1st of the month at midnight UTC; there is none until an administrator sets one. When it is reached, the queue starts nothing new until the next month, and work already running finishes. A person can still start an attempt by hand: the button says it is past the monthly budget, and the attempt goes only after Start anyway. The free CI minutes are what your GitHub plan gives each month (2,000 by default); Money warns at 80% of them. They are GitHub's bill — shown beside the budget, never counted in it.

Who can read this record — private or public. Private is the default and means the public side of DoneMark 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

What the project knows — the brief, the decisions and its words — is on About this project, with How it works here. The project's Settings are for configuration, in six sections listed at the top: The project, Who builds it, Limits, How it is tested, Going live and Judges. Every section saves on its own and says when a change to it takes effect — immediately, at the next dispatch, or at the next release — who last changed anything in it, and when. A setting that bites at another moment than its section says so on itself: the seal, under How it is tested, takes effect at the next release.

The name. Rename in The project. It changes the name everywhere DoneMark shows it, at once. Nothing in your repository carries the name, so a rename touches no code, and every sealed record keeps its address. Two projects of one organisation never share a name, archived ones included. What the project is for is its brief, not a second description here.

Limits. The most one attempt may spend, run and turn — money in dollars, time in minutes, and turns — each saved together with Save, taking effect at the next dispatch. An attempt that reaches one stops and says which. Beside them, the project's own day: see The queue's walls below.

Judges. The same list as on People: every member, with a tick for this project. Tick it here or there; it is one list. A reader can never judge, whatever seat they hold.

Builds. Every project works in releases — see Releases, from plan to live.

The daily ceiling. $50 by default: once the project's attempts have spent that much in a day (UTC), no new work starts until the next day; what is running finishes. A requirement that fails twice the same way leaves the queue until a person looks.

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.

Where it runs. Vercel (recommended for a Next.js app), Fly.io, Render, a server of your own, or Not yet. Until one is chosen, the release step fails on purpose rather than guess. On Vercel, DoneMark also reads each attempt's preview — see Seeing it running.

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

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

The seal gates the merge. Off by default. Off, DoneMark 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. DoneMark 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 DoneMark permission to write your code — the witness holds read on contents and that is not configurable.