proofline
TR

No evidence, no claim.

Proofline is a workflow of agents and skills where every claim comes with its source.

Source Evidence rules

See how it works

How a task moves

The command, not the model, decides the next step. Every task passes the same eight stages.

Source Lead hard rules

  1. 1. IntakeThe task is received
  2. 2. ClassificationA class is chosen
  3. 3. DISCOVEREvidence is gathered
  4. 4. Design and planThe plan is written
  5. 5. Approvals and freezeThe plan is frozen
  6. 6. ImplementOne Implementer writes the change
    Gates run after ImplementSECRETSREVIEWQAVERIFYCODE_DONE
  7. 7. KnowledgeWhat was learned is kept
  8. 8. Report, DONE, cleanupReport and cleanup

Why you can trust it

  • Every task is classed TRIVIAL, STANDARD, COMPLEX or CRITICAL. The highest class any indicator reaches wins.

    Source Classification

  • The freeze hashes the task, evidence, plan and QA plan. Any later change fails verify-freeze.

    Source Freezes

  • Exactly one Implementer per run. Reviewers run in parallel at the gate.

    Source Roles

  • A task reaches CODE_DONE only when every required gate passes, or is fully waived, for the exact current content.

    Source Gates, fix loop, completion

  • Commit and push need the user's approval and pass through the git hooks.

    Source Gates, fix loop, completion

What else it does

  • A product PRD is written with you, and a trace shows the chain behind a requirement or task.

    Source Lead commands

  • A batch of tasks runs in one session, one at a time, each in its own worktree.

    Source Gates, fix loop, completion

  • A failed or blocked run is reopened only with your approval; the frozen plan stays.

    Source Gates, fix loop, completion

  • One command does knowledge, commit, push, pull request, merge and cleanup with one question.

    Source One-command delivery

  • A red CI check is fixed in a round of its own, without asking you.

    Source CI-fix round

  • GitHub, GitLab and Azure DevOps work; with no CI, build and test run locally before merge.

    Source Lead commands, One-command delivery

  • Each surface of a product can have its own design document, plus a shared base.

    Source Command routing

  • Implementers mark each deliberate shortcut in code, so it can be listed as debt.

    Source 7. Knowledge

Two kinds of evidence

Source Evidence rules

reproduced

The check was run and the result was observed.

traced

A concrete input was followed along a concrete path.

Go deeper

11 roles and 28 skills