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.2Who it is forA solo builder, a startup, a company — what changes and what does not.3Concepts and terminologyEvery word DoneMark uses, in the order you meet them.

Setting up

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

Reference

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

Using it

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