Topic · software accomplishment summary

What is a software accomplishment summary, and how do I keep it true in CI?

Gist

A software accomplishment summary is the SAR pack: one HTML file from the same gate-criteria CI already ran. Proof writes it with proof gate sar --output sas.html. Jama still authors. The DER still signs. SAS is not in proof doc list-templates.

proof gate sar --output sas.html

Keep the board if they sign. Keep Jama if they author. Proof is not a certificate, and a green SAR is not DO-330.

Request demo Last Word SAS vs this graph

01 · The pack that is not minutes

A Word SAS is last week's paste.

The board asked for one document. Someone copied last SAR into this one. The graph moved. The paste did not.

The gate H1 lives on preliminary design review. SRR, PDR, CDR, and TRR assess readiness. They do not write the pack. Only SAR does, and only when you pass --output.

The generic document path cannot supply gate-criteria. That is why sas is missing from proof doc list-templates. The NASA software-assurance sheet is a different template, on NASA-STD-8739.8, as proof doc generate verification-report.

proof gate srr
proof gate pdr
proof gate cdr
proof gate trr
proof gate sar --output sas.html
proof gate sar --format json

Table is the default. JSON is for CI. Markdown is for a comment. Exit 0 is ready. Exit 1 is not ready. Exit 2 is ready with observations. The HTML is the pack the board can open. It is not the signature.

02 · The exhibit

Same heading. A paste, or this graph.

The Word file still says last SAR. The YAML will fail the criterion that was never closed. Click the tabs.

Word / StrictDoc pack

Opened last SAR, copied forward
heading one table the board already saw

File attached

This push

The pack did not notice an open fail criterion.

No SAS from this graph

Word / StrictDoc pack

Still last SAR. Still a paste.

Keep the minutes

Proof

Ask does this graph still pass SAR
Gate proof gate sar --output sas.html

Fail criterion, no pack

Same heading. A paste, or this graph. Click the tabs.

Surface	What they do	What Proof does
Software accomplishment summary	The SAR pack a DER or NASA board reads: lifecycle, evidence, deviations, means of compliance	HTML from `proof gate sar --output sas.html`. Executive summary, requirements, design, verification, traceability, compliance matrix, open issues, Mermaid diagrams. Only SAR. Only with `--output`.
Jama / Polarion / DOORS	Author the programme and export a review pack	They still win at authoring. Proof does not replace Jama. IBM DOORS stays a mention on Proof vs Jama.
PDR / SRR / CDR / TRR	Earlier NASA lifecycle gates	Those H1s live on preliminary design review as `proof gate pdr` and the family. They do not write SAS.
NASA-STD-8739.8 verification report	Assurance completeness by level	That template is `proof doc generate verification-report`. Not this URL.
Rapita / LDRA / VectorCAST	Qualified object-code coverage on C	They still win at the qualified toolchain. Proof is not DO-330. Proof vs LDRA.
StrictDoc SAS template	A static RST skeleton for the same artefact	Keep it if you already fill RST. Proof writes HTML from this graph, not from a copied heading.

The pack names the open fail. A heading that still says last SAR is minutes, not this push.

proof gate sar
proof gate sar --format json
proof gate sar --output sas.html

A thin graph makes a thin SAS. Treat the HTML as a snapshot of this graph, not as a second source of completeness. We have not run this against a frozen Rapita / StrictDoc / DER pack, and we have not claimed the file is a certificate. The loss is named, not scored.

03 · The honest loss

A green Proof SAR is not a certificate.

Proof writes HTML from gate-criteria. It does not sit the board. Jama still authors. The DER still signs.

Proof is not NASA. Proof is not a DER. Proof is not DO-330. SAS is not advertised on proof doc list-templates because the generic generate path cannot supply gate-criteria. PDF fails until chromedp lands. The compliance matrix maps NPR 7150, DO-178C, and ISO 26262 onto evidence in this repo. That mapping is not a TÜV or FAA stamp. Object-code coverage on C still wants the qualified toolchain. That H1 lives on MC/DC for Go and on Proof vs LDRA.

The gate family stays on preliminary design review. The NASA assurance sheet stays on NASA-STD-8739.8. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a SAS in software? The same artefact. Same URL. Not a twin.

What is a software verification report? The NASA-STD-8739.8 completeness sheet. NASA-STD-8739.8 as proof doc generate verification-report.

What is a preliminary design review? An earlier gate. It does not write SAS. PDR.

What is a software baseline? A named freeze of the shalls. software baseline.

I need DO-178C style verification but I'm not in aerospace. What can I use? The four jobs, not this pack. DO-178C-style verification.

Is Proof DO-330 qualified? No. Named on DO-333 and here.

Is Proof a VectorCAST alternative? No. LDRA owns that cluster. Proof vs LDRA.