Topic · software checklist

Software checklist

Gist

A software checklist is a named campaign with ordered stamps, not a Word list. Proof runs proof audit --check process_checklist on every normal audit. FAIR still owns the quality PDF. Jotform still owns the form. Jama still authors.

proof audit --check process_checklist

Keep FAIR if you already print a quality list. Keep Jotform if you already collect ticks. Proof will not count a PDF in Drive as a campaign stamp.

Request demo Last Word list vs this stamp

01 · The missed spine

The repo is green. Nobody stamped traces-light.

Pipeline routing names the biggest gap. It does not remember which campaign step you already did.

FAIR, GeeksforGeeks, and StrongQA will give you a software checklist: document the source, run tests, inspect the module. That is not this URL. Proof's check is a default-on warning on the active campaign. The builtin name is onboard_v1. Humans and agents do the work. Proof stores the order and the stamps. There is no model inside proof checklist.

The motivating miss is mechanical. A new repo has proof.yaml and a few shalls. Every other gate is green. The next eligible step is still traces-light. Nobody confirmed it. The next agent starts at whatever the pipeline role shouts today. The spine was never the router.

On an already-onboarded repo the when: new_project steps (init, research, skeleton) auto-skip. A mature tree is never told to start at step 1. Confirm what you have already done. Skip with a reason what you have not. Or set project.checklists.active: none if you are not running a campaign.

proof checklist show onboard_v1
proof checklist confirm --id traces-light --package security --note "Implements on security entrypoints"
proof audit --check process_checklist

The first command is the next eligible step. The confirm is the stamp. The audit is that stamp missing on every later run. A green quality PDF next to an unstamped traces-light is how the campaign stayed oral.

02 · The exhibit

Same repo. A Word list, or this stamp.

The quality PDF is ticked. The campaign is not. Click the tabs.

The run

Ask FAIR / Jotform / inspection PDF
Exit 0 if the boxes are ticked
Why the list does not live in the repo

List green

This hop

No stamp on traces-light. The next agent still has no campaign spine.

No stamp

The run

Keep the PDF. It still owns the quality list you print. That is not this hop.

Keep the list

Proof

Ask active checklist complete, or next eligible step
Out WARN plus proof checklist show / confirm

A green PDF is not a stamp

Same repo. A Word list, or this stamp. Click the tabs.

Surface	What they do	What Proof does	What we lose
FAIR quality list	A printed software quality checklist. Document, test, inspect.	Named DAG. Stamps in `proof/checklists/onboard_v1.state.yaml`.	Not FAIR's attributes. Keep the PDF if you already print it.
Jotform / Nintex	A form that collects ticks. Process software for offices.	`proof checklist confirm --id traces-light`. DAG must be satisfied.	Not a form builder. No assignees, due dates, or Power Automate.
Inspection / StrongQA	A module inspection list, or a list of tests to run.	Campaign grain. Not per-STK ac-sweep. Not the test runner.	Not the inspection. Not the suite. Acceptance criteria.
Jama	The authoring programme. A checklist lives on the item if you put it there.	Fail the missing stamp on the files. The next eligible step in the log.	Not Jama's field. Jama still authors.

The teaching graph is still a ticked PDF next to an unstamped traces-light. Confirm the step you actually ran. Three honest exits, in order: confirm with a note; skip with a reason; or set project.checklists.active: none if you are not running a campaign. Do not confirm a step you have not done.

proof checklist show onboard_v1
proof checklist confirm --id traces-light --package security --note "Implements on security entrypoints"
proof checklist check onboard_v1
proof audit --check process_checklist

The check is a warning, default-on. It skips itself when proof checklist check evaluates required named checks, so the spine does not recurse. upstream_refresh_v1 is the other builtin, for an upgrade, not a new repo. See acceptance criteria if the list is per-STK, not the campaign. See requirement lifecycle if the missing object is status on a shall, not a stamp on a step. See Proof vs Jama if the missing object is the authoring programme.

03 · The honest loss

Proof names the stamp. It does not do the work.

A confirmed step is not a proof of the Go. Jama still authors.

Proof does not implement FAIR's quality checklist, Jotform, Nintex Promapp, StrongQA test lists, or the PROCESS 2025 surgical case-series guideline. It does not assign owners or due dates. A stamp is an "I did this" record. It is not a proof that the Go matches the shall. We have not scored onboard_v1 against a frozen FAIR or ISO 9001 corpus. The loss is named, not scored. The pipeline role still routes the biggest remaining gap after the spine is green enough. Per-STK progress stays on ac-sweep.

Acceptance criteria stay on acceptance criteria. Status on a shall stays on requirement lifecycle. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a software checklist? Same question. Same URL.

What is a process checklist? Same cluster in Proof. The Google result is often the PROCESS 2025 surgical reporting guideline. That is not this hop.

What is an onboarding checklist? HR and IT onboarding. Proof's onboard_v1 is a repo campaign, not a laptop image.

What is an audit checklist? ISO 9001 and internal-audit PDFs. Keep them. They do not stamp traces-light.

What is a verification checklist? Often identity documents for SNAP or E-Verify. Not this hop.

Is Proof a Jama alternative for checklists? No. Jama still authors. Proof vs Jama.