proofline
TR

How it works

Each diagram below is drawn from the workflow files, and every node names the stage or rule it comes from. More features follow the diagrams.

How a task moves

How a task movesDiagram facts from the Proofline workflow.1. Intake1. Intake2. Classification2. Classification3. DISCOVER3. DISCOVER4. Design and plan4. Design and plan5. Approvals and freeze5. Approvals and freeze6. Implement6. Implement7. Knowledge7. Knowledge8. Report, DONE, cleanup8. Report, DONE, cleanup
How a task moves

Source Lifecycle stages

Diagram facts from the Proofline workflow.
  1. 1. Intake

    Source 1. Intake

  2. 2. Classification

    Source 2. Classification

  3. 3. DISCOVER

    Source 3. DISCOVER

  4. 4. Design and plan

    Source 4. Design and plan

  5. 5. Approvals and freeze

    Source 5. Approvals and freeze

  6. 6. Implement

    Source 6. Implement

  7. 7. Knowledge

    Source 7. Knowledge

  8. 8. Report, DONE, cleanup

    Source 8. Report, DONE, cleanup

Roles and gates

Roles and gatesDiagram facts from the Proofline workflow.gate SECRETSGate setscript agent.sh secret-scan <ID>Gate setgate REVIEW_SMALLGate setrole reviewerGate setgate REVIEW_PLANGate setrole reviewerGate setgate REVIEW_RULESGate setrole reviewerGate setgate REVIEW_TESTSGate setrole reviewerGate setgate REVIEW_DATAGate setrole reviewerGate setgate SECURITYGate setrole security-reviewerGate setgate QAGate setrole qaGate setgate VERIFYGate setrole verifierGate setgate VERIFYGate setscript the verifier reads reviews/visual-proof/report.json, which the QA visual focus producesGate set
Roles and gates

Source Gate set

Diagram facts from the Proofline workflow.
  • SECRETS → agent.sh secret-scan <ID>

    Source Gate set

  • REVIEW_SMALL → reviewer

    Source Gate set

  • REVIEW_PLAN → reviewer

    Source Gate set

  • REVIEW_RULES → reviewer

    Source Gate set

  • REVIEW_TESTS → reviewer

    Source Gate set

  • REVIEW_DATA → reviewer

    Source Gate set

  • SECURITY → security-reviewer

    Source Gate set

  • QA → qa

    Source Gate set

  • VERIFY → verifier

    Source Gate set

  • VERIFY → the verifier reads reviews/visual-proof/report.json, which the QA visual focus produces

    Source Gate set

Four classes, four flows

TRIVIAL

All of: ≤ 2 scope paths (script-enforced), text or configuration only (no executable code or tests in scope, script-enforced, A115), no behaviour change, no design choice, no contract, persistence, security or concurrency involvement

Source Classification

TRIVIALClassificationautonomousAutonomy policyevidence: nopipelines.TRIVIALqa: nopipelines.TRIVIAL
TRIVIAL

Source Classification

  1. TRIVIAL

    Source Classification

  2. autonomous

    Source Autonomy policy

  3. evidence: no

    Source pipelines.TRIVIAL

  4. qa: no

    Source pipelines.TRIVIAL

  5. review: no

    Source pipelines.TRIVIAL

  6. architect: no

    Source pipelines.TRIVIAL

  7. max_explorers: 0

    Source pipelines.TRIVIAL

  8. max_scope_paths: 2

    Source pipelines.TRIVIAL

STANDARD

Bounded behaviour change in one component; no new integration, persistence or security boundary

Source Classification

STANDARDClassificationautonomousAutonomy policyevidence: yespipelines.STANDARDqa: yespipelines.STANDARD
STANDARD

Source Classification

  1. STANDARD

    Source Classification

  2. autonomous

    Source Autonomy policy

  3. evidence: yes

    Source pipelines.STANDARD

  4. qa: yes

    Source pipelines.STANDARD

  5. review: optional

    Source pipelines.STANDARD

  6. architect: no

    Source pipelines.STANDARD

  7. max_explorers: 1

    Source pipelines.STANDARD

COMPLEX

≥ 2 modules; new integration or dependency; public contract change; persistence or schema change; meaningful concurrency; a design choice with real tradeoffs

Source Classification

COMPLEXClassificationsupervisedAutonomy policyevidence: yespipelines.COMPLEXqa: yespipelines.COMPLEX
COMPLEX

Source Classification

  1. COMPLEX

    Source Classification

  2. supervised

    Source Autonomy policy

  3. evidence: yes

    Source pipelines.COMPLEX

  4. qa: yes

    Source pipelines.COMPLEX

  5. review: yes

    Source pipelines.COMPLEX

  6. architect: yes

    Source pipelines.COMPLEX

  7. max_explorers: 2

    Source pipelines.COMPLEX

CRITICAL

Auth, authorization, cryptography, secrets, any security boundary; destructive or irreversible migration; financial or data-integrity-critical behaviour; high-impact CI, deploy or infrastructure

Source Classification

CRITICALClassificationsupervisedAutonomy policyevidence: yespipelines.CRITICALqa: yespipelines.CRITICAL
CRITICAL

Source Classification

  1. CRITICAL

    Source Classification

  2. supervised

    Source Autonomy policy

  3. evidence: yes

    Source pipelines.CRITICAL

  4. qa: yes

    Source pipelines.CRITICAL

  5. review: yes

    Source pipelines.CRITICAL

  6. architect: yes

    Source pipelines.CRITICAL

  7. max_explorers: 3

    Source pipelines.CRITICAL

More along the lifecycle

  • A product is discovered and assessed with you in the main session, before any task run.

    Source Lead commands

  • A product PRD is written with you and checked before you approve it.

    Source Lead commands

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

    Source Command routing

  • 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

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

    Source 7. Knowledge

  • 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

  • Outcomes are recorded and checked, and a trace shows the chain behind a requirement or task.

    Source Lead commands

Works with Claude Code and Codex

Proofline works with Claude Code and Codex. Codex is supported in the implementer role.

Source Runtime role override

Seen in real use: Claude took over when the Codex limit was reached.