Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-049SystemReview

When Delete calls internalGet and internalGet returns an error, Delete shall use that error to short-circuit to the safe fallback path (return original input unchanged) rather than discarding the error and proceeding with potentially invalid offsets.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When Delete calls internalGet and internalGet returns an error, Delete shall use that error to short-circuit to the safe fallback path (return original input unchanged) rather than discarding the error and proceeding with potentially invalid offsets.

FRETish formula
the parser shall always satisfy !delete_discards_internalGet_error | delete_propagates_internalGet_error

Rationale & tags

Why this requirement exists, and how it is categorised.

Error propagation from internalGet is the defense-in-depth mechanism against sentinel-value panics. If Delete discards the error (assigns to _), it loses the signal that offsets are invalid. This was a contributing factor in the PR #280 class.

error-propagationdeletepr280

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 18:00 UTC · agent:claude
Modified
Jul 26, 2026, 14:54 UTC · human:cli

Obligations

What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.

1 obligation · 1 discharged

Browse the catalogue
Discharged
Worst case if violatedCritical

Delete discards the internalGet error and proceeds with stale offsets into data[prevTok]/data[end:] (parser.go:907), panicking with index-out-of-range on adversarial input — the OSS-Fuzz witness shape.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test

Formula evidence

The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).

FRETish formula

the parser shall always satisfy !delete_discards_internalGet_error | delete_propagates_internalGet_error

Variables

NameTypeDirectionDescription
delete_discards_internalGet_error—True when Delete discards an error returned by internalGet (assigns to underscore) instead of using it to short-circuit.
delete_propagates_internalGet_error—True when Delete uses an error returned by internalGet to short-circuit to the safe fallback path.

Witnesses· 3 scenarios total

  • TestDeleteErrorPropagation
    deep_spec_test.go:228
  • TestMCDC_SYS_REQ_049_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:1717exercises 1 condition scenario
  • TestMCDC_SYS_REQ_049_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:1727exercises 1 condition scenario
  • TestMCDC_SYS_REQ_049_Row3_PropagatedError
    mcdc_spec_witnesses_test.go:1740exercises 1 condition scenario
  • TestObligation_SYS_REQ_049
    obligation_evidence_test.go:418

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Open in graph

Loading graph…

Trace evidence

The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.

Impact

Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.

If you change this

Requirements
0
Files
1
Tests
3
At-risk contracts
0

Files to re-check (1)

  • parser.goparser.go

Tests to re-run (3)

  • deep_spec_test.godeep_spec_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_evidence_test.goobligation_evidence_test.go

What this rests on

Parent requirements (1)

Discussions

Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.

Sign in to discuss this with the proof team.Sign in