Start a new app

Nothing exists yet. DoneMark gives you a repository that can be witnessed from its first commit, and a first ask already written.

What you are choosing

On the project door, a new app offers the stacks DoneMark can witness today — Web app · Next.js with Postgres, Phone app · Expo, Service · Elixir. Each template carries the same four things:

• CI with a Run button
• the check report and the pictures, wired in
• the runner files, at the current version
• the first requirement, Lay the foundation, already written

Under the templates, the door prints the stacks it cannot witness yet, in plain words: DoneMark has no reporter for them, so it could not witness a single criterion. It says so there rather than after your first attempt.

What DoneMark will not do

It does not advise on a stack. It prints the floor of what it can witness and nothing more. Within that floor, the choice is yours — and if an agent makes it, the choice is shown as the agent's claim, not as DoneMark's recommendation.

It does not scaffold, host or configure anything. The template is a GitHub template repository. You create your repository from it, under your own account, with your own login.

Step 1 — the project asks, once it can see

Make the project and point it at a repository, then install DoneMark's GitHub App (named Constat on GitHub) on that repository. The moment it can see, DoneMark reads — and if the repository has no commits it says so and puts the choice in front of you on the project's own page: start from a template, or bring code you already have. It never picks one. These are the templates it can witness end to end, and which one you build in is yours; the moment DoneMark chose, its readings about what you built would stop being independent of that choice. A template DoneMark cannot reach is not offered.

Choosing one shows you the steps before you leave, and says who does each. Two of the three happen on GitHub, because the App DoneMark holds cannot write to a repository — not a file, not a branch, not a commit. That is not a gap; it is the reason what comes out of your repository later is evidence rather than a claim.

One press, or by hand. Create owner/name from the template, in my name → signs you in to GitHub for that one act and makes the repository under your account; DoneMark keeps nothing from it. Or make it yourself on GitHub ↗ if you would rather.

Either way, the copy is yours, and DoneMark waits. The page names the repository you are about to create, fills the name in on GitHub's own page, and keeps looking while you are gone. Come back to it: when the repository exists and the App can read it, the page turns into the project's face. If the App is not on the new repository yet, the page says that is the missing step. If you made it under a different name, you can say so there without leaving.

Step 2 — the first requirement is already there

Lay the foundation is on the record, approved, before you have written anything. Its criteria name checks the template already carries: a fresh checkout installs and runs its tests, the app starts and shows its name on its first screen with a picture, and the reporter reads the repository as ready.

Its point is not the code. It is to run the whole path once — an ask, an agent, CI, evidence, a door, your verdict — so that the first thing on your record is a witnessed change rather than scaffolding.

Step 3 — the key, then dispatch

Add the key as the page names it — or paste it and let the page seal it in your browser and store it on GitHub in your name — then Test the key, and press Dispatch once it has passed.

The Next.js template, on Vercel, gives every attempt a running copy you can open from the run page; the Expo template gives a preview to open on your phone. See Seeing it running.

What the agent chooses within the stack — which framework, which database — is written as its own claim and shown beside the evidence, never inside it.

Step 4 — your acceptance is DoneMark № 1

When you accept it, the project's first sealed record exists, and it is a real one.