Documentation

DoneMark documentation

Proof of done, for software built by agents.

Start here

1What DoneMark is forThe one idea, and the boundary it sits on.2Concepts and terminologyEvery word DoneMark uses, in the order you meet them.3Who it is forA solo builder, a startup, a company — what changes and what does not.

Using it

4What waits for you, and your hatsThe list behind the count at the top, and how your hats order it.5The loop, step by stepOne requirement from a sentence to a sealed record, with what you see at each step.6Reading a verdictWhat the run page tells you, and how to tell whose fault a red run is.7Seeing it runningThe copy your host builds, the database warning, and journeys.8Releases, from plan to liveAsks built together, tested once, judged one by one and put live in one merge.9When things go wrongThe failures you will actually meet, and what each one means.

Reference

10Every state, listedRequirements, attempts, releases, evidence and claims — the exact words and what they mean.11What your CI must publishThe archive contract, in short.

Setting up

12Your first hourFrom signing in to a room with a project in it.13People, seats and invitationsWho may write asks, who may judge, who may only read.14The brief and the decisionsWhat the project is for, and the rules every attempt is told.15Bring a project you already haveOne line, one pull request, one secret.16Start a new appFrom a template DoneMark can witness from its first commit.17SettingsEvery switch, what it changes, and what it cannot change.