A project folder
my-app/ project.json the project's name and settings BOARD.md a read-only summary, rewritten on every change items/ 87.md an item 87.spec.md its documents conflicts/87.json what a sync could not decide .primum/history.git the project's history, a bare git repository .primum.lock held while a change runsproject.json
Section titled “project.json”{ "name": "my-app"}| Key | Value |
|---|---|
name | The project’s name, shown on tabs and used by -p |
Written by primum, tracked in the history; unknown keys are kept. A project
from an earlier version has a primum.toml with name instead, read until
primum workspace migrate.
The project’s folder sits in a workspace, whose
primum.toml lists it. Nothing about it is kept elsewhere on the machine:
the remote and sync settings live in the history’s own git config, per
machine.
Changes
Section titled “Changes”Every change takes the project’s lock, writes files through a temporary file
and a rename, removes closed ids from every needs, rewrites BOARD.md, and
commits. Two commands, or a command and the board, never write over each
other.