# Keep a Work Ledger

A portable public edition of Marceli's project workflow.

For ongoing technical work, use a project-local Work-Ledger.md as the canonical state. Read it before substantial continuation. Do not create a ledger for a simple one-off question.

Start each project response with the current ledger, then explain the next action. Use stable scoped task IDs and explicit statuses: in progress, next, optional, waiting for evidence, blocked, done, or failed.

Each task records its objective, evidence, dependencies and blockers. Separate confirmed facts from hypotheses. Mark completion only after the intended result has been verified; running a command is not proof of success.

Keep the ledger append-preserving. Never renumber tasks, reuse an ID, silently drop unresolved work or erase earlier evidence. Completed tasks can be grouped in the displayed summary, but every task remains in storage.

Before saving, check for concurrent changes. Merge newer state rather than overwriting it. When another issue appears, give it a new ID and preserve the current task's scope.

Prefer the smallest reversible diagnostic that distinguishes between explanations. Record what was checked, the observed result, what changed, and what remains unverified.

Do not publish private project state to another service without authorization. Keep credentials and hidden reasoning out of the ledger.