Topic · deployment tvl verified

Deployment tvl verified

Gist

Deployment tvl verified is whether a high or critical KnownIssue is anchored by verified production TVL or an outside grade. A headline that restates itself is not an anchor. Proof runs proof audit --check deployment_tvl_verified. Jama still authors.

proof audit --check deployment_tvl_verified

Keep the Jira ticket if the board already owns it. Keep Jama if it already authors the shall. Neither one grades the claim.

Request demo Last unanchored high vs this hop

01 · The unanchored high

A high grade can still rest on the author's own assertion.

Presence of the YAML is not this hop. This hop is whether somebody other than the author made the grade checkable.

The check is default-on for Web3 and DeFi projects, warning, document stage. It reads every active KnownIssue (open / reviewed). A low internal finding is skipped. An honest bounty_severity of low or informational is skipped. Withdrawn and fixed KIs are out of scope. Non-Web3 repos skip unless you set enabled: true.

If any of severity, code_severity, or bounty_severity is high or critical, the hop resolves an anchor kind. tvl is verified production TVL. adjudicated is an outside party that upheld the grade against a cited ruleset. pending is a findable report whose grade question is still open. none is a finding. Filing a URL is not enough. The author's own claim restated in another venue is the shape this hop exists to prevent.

id: KI-T1
status: open
severity: high
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 on_chain_status.production_tvl and no verdict. That is the unanchored-high case. Submission validated is the error floor before a finding leaves. A claim still awaiting judging does not fail that hop. Here the same claim is reported as in flight: not anchored, and not a finding.

proof known-issue list
proof known-issue edit KI-T1
proof audit --check deployment_tvl_verified

Cite verified production TVL when the finding is against a deployed surface that really does custody value. Record the outside adjudication when the grade is defined by a contest's published rules or a vendor's rating. Honestly downgrade bounty_severity only when you concede the headline is not bounty-calibrated. Doing all three is not extra rigour. At least two of them are then not true.

02 · The exhibit

Same KI-T1. Unanchored high, or this hop.

Open finding, high grade, no TVL, no verdict. Click the tabs.

The row

Ask does the KI exist and say high
Stamp KI-T1.yaml is present, severity high, no production_tvl, no adjudication
Why a filing URL restates the author's claim; the hop needs who graded it, not that you asserted it somewhere else

Status green

This hop

Nobody asked whether the grade was anchored. High is already in the ledger. The warning is this hop.

No stamp

The row

Keep the Jira ticket. Keep the Jama field. That is not this hop.

Keep the record

Proof

Ask is KI-T1 high or critical, and is the claim anchored
Out deployment_tvl_verified KI-T1 high claim is unanchored (no verified TVL, no outside grade)

Unanchored claim

Same KI-T1. Unanchored high, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Submission validated	Error. A submitting KI must carry the four documentation gates plus a poc_quality block. Gate 9 does not fail an in-flight claim.	Warning. Whether a high or critical claim is anchored, including KIs nobody is filing yet.	Not the error floor. See submission validated.
Poc quality checked	Warning. Missing block, then the eleven-rule review when the union includes the KI.	Warning. Whether the grade itself is grounded outside the author.	Not the eleven-rule review. See poc quality checked.
High severity reproducer grade	Error. A high-stakes KI needs an executed witness, not a CVSS headline.	Warning. A high-stakes KI needs an anchor for the grade, not a PoC run.	Not the witness hop. See high severity reproducer grade.
DefiLlama TVL page	A hosted figure. Ads production tvl is that page if it ranks.	A YAML flag the audit can warn next to the KI. It does not fetch the URL.	Not a TVL oracle. We have not verified on-chain value.
Jira ticket	A linked-issue field the board already owns.	A YAML object whose on_chain_status and adjudication the hop grades.	Not a ticket workflow. We have not frozen a Jira pack.
Jama field	The authoring programme. Attributes if you put them there.	A YAML object the audit can warn next to the shall.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one active high KI next to no anchor. Read the finding. Then cite TVL, record the verdict, or concede the bounty grade.

on_chain_status:
  production_tvl: true
  tvl: https://defillama.com/protocol/example
  deployed_version: v1.2.0

The other honest exit is an outside grade. File first. Wait. Then record what came back:

proof known-issue edit KI-T1 \
  --set-submission-adjudication-status accepted \
  --set-submission-adjudicated-severity high

A vendor that affirms the finding without grading it leaves the claim in flight. That is the correct reading. Silence about severity is not a downgrade. Completeness stays on known issue complete. The error floor stays on submission validated. Do not treat a DefiLlama page as this cell. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names an unanchored claim. It does not fetch TVL, and it does not prove the Go.

A green deployment_tvl_verified can still mean there were no high KnownIssues. The hop is a warning. Jama still authors.

Warning severity. A counted finding does not block the audit. production_tvl: true is operator judgment today; the hop does not independently verify on-chain value. It does not fetch the submission URL, read the cited ruleset, or check the recorded verdict against the tracker. A claim in flight is not a finding. Zero high or critical KnownIssues is a pass that inspected nothing. Non-Web3 projects skip unless you opt in. Load failure is a fail. Opt-out is enabled: false. Downgrading bounty_severity to silence a finding you still intend to file at high is severity dishonesty, not a fix. The hop does not prove the Go. We have not scored this floor against a frozen Jama pack, a DefiLlama export, or a Jira export. The loss is named, not scored.

The error floor stays on submission validated. The missing-block review stays on poc quality checked. The witness hop stays on high severity reproducer grade. 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 deployment tvl verified? Same question. Same URL.

Is this submission validated? No. That hop is an error: a submitting KI must carry the four documentation gates plus a poc_quality block. A claim still awaiting judging does not fail Gate 9 there. This hop is a warning on the grade itself. See submission validated.

Is this poc quality checked? No. That hop grades the missing block and the eleven rules. This hop grades whether the severity claim is anchored. See poc quality checked.

Is this high severity reproducer grade? No. That hop is an executed witness for a high-stakes KI. This hop is an outside anchor for the grade. See high severity reproducer grade.

Does a missing known-issues directory fail? No. Zero high KnownIssues is a silent pass. Put a YAML there when the behavior is confirmed, then cite TVL or the verdict before you leave the headline at high.

Does filing a tracker URL clear the hop? No. A report must come back with an upheld high or critical grade against a cited ruleset. Until then the claim is in flight.

Does production_tvl true prove the TVL? No. The hop confirms the flag exists. It does not fetch DefiLlama. It does not read the chain.

Does a green hop prove the Go? No. The hop does not run the PoC. It does not prove the function.

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