Topic · residual kill hygiene

Residual kill hygiene

Gist

Residual kill hygiene is whether a closed quantitative hunt kill still has samples. Proof runs proof audit --check residual_kill_hygiene. A spreadsheet row that says killed is not that hop. Jama still authors.

proof audit --check residual_kill_hygiene

Keep Metricstream if it already owns residual risk. Keep Jira if it already owns won't-fix. Neither one refuses a closed kill_number with an empty sample_table in this repo.

Request demo Last silent close vs this hop

01 · The closed-without-samples pattern

A kill_number without a sample_table is a story. The hop names it.

You can write status: closed and a ppm figure, leave sample_table empty, and keep the hunt green if the hop never ran.

A residual is a hunt disposition under proof/residuals/. It is a quantitative claim that an angle sits below the severity bar inside a declared sample domain. It is not a product defect tracker. A live unfixed failure is a KnownIssue. A named human shipping that failure is AcceptedRisk. See known issues reviewed and risk acceptance.

The check is default-on VERIFY, warning. Closed plus a quantitative kill_number (digits, ppm, bps, %, $) needs a non-empty sample_table. provisional_kill with empty samples is valid. Keep the status provisional until you measured. Same-domain strengthens is rejected: copying the prior pair set is a double-count, not a stronger kill. A reopen_if row marked falsified cannot stay closed. related_known_issues and source_vector, when set, must resolve. Reopened without a linked KnownIssue is promotion debt.

Missing proof/residuals/ is a no-op pass. Projects that never author residuals are not failed for that. Opt-out reports skip, never pass. A check that ran nothing must not count toward the audit's pass total.

proof residual list
proof residual audit --strict
proof audit --check residual_kill_hygiene --verbose
proof residual new --id L-181 --title "same-tier floor" \
    --kill-number "1 ppm" --sample pair=ETH/BTC,mid_f=2.9e6
proof residual close L-181

Do not hide a confirmed Med or High as a residual. File the KnownIssue. Do not close a quantitative kill without samples. Do not strengthen L-181 with the same pairs.

02 · The exhibit

Same L-181. A silent close, or this hop.

The kill_number is written. The sample_table is empty. Click the tabs.

The row

Ask does status still say closed
Stamp kill_number 1 ppm, sample_table empty
Why the spreadsheet never asked for pairs

Status green

This hop

No residual_kill_hygiene JSON. The ppm is written. The samples are not.

No stamp

The row

Keep the hunt notes. Keep the ppm. That is not this hop.

Keep the record

Proof

Ask does a closed kill_number still have samples
Out L-181 sample_table gap: closed quantitative kill with empty samples

Sample table gap

Same L-181. A silent close, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Spreadsheet kill list	A row that says killed, with a number.	Warn when closed plus kill_number has no sample_table.	We do not author the hunt. Empty samples on provisional_kill still pass.
Jira won't-fix	A ticket status on an issue.	Refuse same-domain strengthens. Refuse a falsified reopen_if that stays closed.	We do not own the ticket thread. A residual is not a defect tracker.
GRC residual risk	Enterprise remaining-risk after treatment.	The hop on YAML under proof/residuals/.	Not Metricstream. Not residual risk. See risk acceptance.
Jama	The authoring programme. Reviews if you put them there.	Warn a dishonest kill in this repo.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one residual next to its sample pairs. Run the check. Read the id. Add samples, or keep the status provisional. Do not copy L-181's domain onto a second residual and call it stronger.

proof residual list
proof residual show L-181
proof residual audit --strict
proof audit --check residual_kill_hygiene --verbose
proof residual close L-181
proof vector link V-H1 --residual L-181

Campaign open-work stays on unresearched_p0_vectors. Vector forward links stay on vector_campaign_hygiene. Prefer proof vector link so the vector owns the forward link. The write of a confirmed failure stays on known issues reviewed. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names a dishonest kill. It does not hunt the angle for you.

A green residual_kill_hygiene is honest YAML on residuals you already wrote. It is not a proof of the Go. Jama still authors.

Default is warning, not fail. A green VERIFY can still carry a sample_table gap unless you raise the fail level or run proof residual audit --strict. Missing proof/residuals/ is a no-op pass that reviewed nothing. Opt-out reports skip, never pass. The hop does not open a campaign. It does not file a KnownIssue. It does not compute residual risk. It does not prove the Go. We have not scored this graph against a frozen Jama pack, Metricstream, or Jira. The loss is named, not scored.

The signed ship of a known failure stays on risk acceptance. The engagement stays on software correctness audit. Jama still authors.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is residual kill hygiene? Same question. Same URL.

Is this residual risk? No. Residual risk on the Ads SERP is enterprise risk management. See risk acceptance.

Is this a KnownIssue? No. A residual parks a measured angle below the bar. A live unfixed failure is a KnownIssue. See known issues reviewed.

Does a missing residuals directory fail? No. Zero files is a pass. Put a YAML there when you park a kill.

Does a sample_table gap fail the merge? No. The hop warns. proof residual audit --strict exits non-zero on the same corpus.

Can I strengthen a prior kill on the same pairs? No. Expand the sample domain, or keep the first residual.

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