Submission validated

The check is default-on at error, document stage. It reads every active KnownIssue (open / reviewed). Scope is a union. Either limb is enough: a submission or upstream_report block is present, or disposition contains the substring submit. A low internal finding nobody is filing is skipped. A low finding that is being submitted is not. Withdrawn and fixed KIs are out of scope.

If the KI is in scope, the hop errors when a named gate is missing. Gate 2 needs a non-empty submission_validation.natspec_review. Gate 3 needs a non-empty commit_origin. Gate 4 needs intended_path_verified: true. Gate 6 needs a master_status of identical, changed-unrelated, or removed-not-fixed. Gate 8 only asks whether a poc_quality block exists. Gate 9 only asks whether a high or critical claim has an anchor. It does not run the PoC. It does not read the NatSpec.

id: KI-S1
status: open
severity: high
disposition: submit
title: empty STS token is ACCEPTED

The suite can still be green. The ticket can still be open. The YAML can still sit in .proof/known-issues/ with no submission_validation key. That is the silent-submit case. poc_quality_checked is a warning that grades the missing block and the eleven rules. This hop is the error gate: fields exist, then the finding may leave. A prior-audit dedup match also blocks. Internal-current duplicates stay a warning on known issue complete.

proof known-issue list
proof known-issue edit KI-S1
proof audit --check submission_validated

Fill the four documentation fields from work you actually did. Add a poc_quality block, then grade the booleans on poc quality checked. Anchor a high or critical claim with verified production TVL or an outside verdict. That grade hop lives on deployment tvl verified. Do not clear this hop by deleting the word submit while a submission block still exists. External reality outranks disposition prose.

The teaching graph is still one active high KI next to no doctrine. Read the finding. Then fill the named gate, or establish the KI never went external.

disposition: submit
submission_validation:
  natspec_review: |
    @param amount The transfer amount (NatSpec on transfer() reviewed);
    no documented behavior covers the overflow shape.
  commit_origin: |
    abc1234 introduce transfer (Joe, 2025-03-14)
  intended_path_verified: true
  master_status: identical
poc_quality:
  real_infrastructure: true
  control_test: true
  current_deployment_relevance: true
  honest_severity: true
  reproducible: true
  no_inflation: true
  operational_path_verified: true
on_chain_status:
  production_tvl: true
  tvl: https://defillama.com/protocol/example
  deployed_version: v1.2.0

Gate 9 is only required when severity, code_severity, or bounty_severity is high or critical. A filing still awaiting a grade does not fail that gate. The warning hop that names an unanchored high, including KIs nobody is filing yet, stays on deployment tvl verified. The per-rule PoC review stays on poc quality checked. Completeness stays on known issue complete. Do not treat Salesforce's bulletin as this cell. Jama still authors. Proof vs Jama.

Error severity. A counted finding blocks the audit. The four documentation fields are shape, not substance: a non-empty string clears Gate 2 even if nobody read the comment. Gate 8 only asks whether a poc_quality block exists; the eleven rules stay on the warning hop. Gate 9 does not fetch TVL, open the tracker URL, or read the cited ruleset. A claim still awaiting judging does not fail Gate 9. Lowering bounty_severity does not clear it here. Closed and resolved findings are skipped, not flagged. Zero submitting KnownIssues is a pass that inspected nothing. Load failure is a fail. The hop does not prove the Go. We have not scored this floor against a frozen Jama pack, a Salesforce bulletin, or a Jira export. The loss is named, not scored.

The missing-block review stays on poc quality checked. The present-block truth hop stays on known issue poc quality effective. The completeness hop stays on known issue complete. The engagement stays on software correctness audit. Jama still authors.

What is submission validated? Same question. Same URL.

Is this poc quality checked? No. That hop is a warning: missing block, then the eleven-rule review. This hop is an error: a submitting KI must carry the block, plus four other gates. See poc quality checked.

Is this known issue poc quality effective? No. That hop is verify-stage truth of a present block on high or critical. This hop is document-stage existence on a submitting KI. See known issue poc quality effective.

Is this known issue complete? No. That hop is whether every active KI has some evidence kind. This hop is the doctrine floor before a finding leaves. See known issue complete.

Is this a Salesforce known issue? No. Ads known issue is that status page. A hosted vendor bulletin is not this cell.

Does a missing known-issues directory fail? No. Zero submitting KnownIssues is a silent pass. Put a YAML there when the behavior is confirmed, then fill the gates before you mark it submit.

Does an empty natspec_review fail? Yes, as an error, when the KI is in the union. Whitespace is empty. The hop does not read the cited comment.

Does deleting the word submit clear a filed finding? No. If a submission or upstream_report block exists, the gates keep applying. Withdraw the report at its venue first, then remove the block.

Does a green hop prove the PoC? No. Gate 8 checks that a block exists. It does not run the exploit. It does not run the control test.

Is this deployment tvl verified? No. That hop is a warning on whether a high or critical claim is anchored, including KIs nobody is filing yet. Gate 9 here is existence of an anchor on a submitting KI. See deployment tvl verified.

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