Proof Portal

Sign in
Projects

jsonparser

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

When Delete is called on input that is truncated at a value boundary (the exact PR

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 is called on input that is truncated at a value boundary (the exact PR

FRETish formula
the parser shall always satisfy !delete_input_is_truncated_at_value_boundary | (delete_returns_original_input_on_truncated_value & delete_completes_without_panic_on_truncated_value)

Rationale & tags

Why this requirement exists, and how it is categorised.

This is the exact bug class from PR #280. Delete calls tokenEnd on truncated input, gets len(data) back, then uses data[endOffset+tokEnd] which panics with index out of range. This specific truncation pattern for Delete must have its own requirement.

pr280deletetruncationsentinel

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 on {"a":1 (the PR-truncation witness) drives internalGet to return stale offsets; the cleanup path slices data[:start] + data[end:] with end > len(data) and panics with slice-out-of-range.

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_input_is_truncated_at_value_boundary | (delete_returns_original_input_on_truncated_value & delete_completes_without_panic_on_truncated_value)

Variables

NameTypeDirectionDescription
delete_input_is_truncated_at_value_boundary—True when Delete is called on input truncated at a value boundary where tokenEnd would return len(data) as a sentinel.
delete_returns_original_input_on_truncated_value—True when Delete returns the original byte payload unchanged for input truncated at a value boundary.
delete_completes_without_panic_on_truncated_value—True when Delete completes without panicking on input truncated at a value boundary.

Witnesses· 5 scenarios total

  • TestDeleteTruncatedAtValueBoundary
    deep_spec_test.go:197
  • TestMCDC_SYS_REQ_048_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:1660exercises 1 condition scenario
  • TestMCDC_SYS_REQ_048_Row2_InvariantViolationPanic
    mcdc_spec_witnesses_test.go:1670exercises 1 condition scenario
  • TestMCDC_SYS_REQ_048_Row3_InvariantViolationOriginal
    mcdc_spec_witnesses_test.go:1682exercises 1 condition scenario
  • TestMCDC_SYS_REQ_048_Row4_InvariantViolationNoPanic
    mcdc_spec_witnesses_test.go:1692exercises 1 condition scenario
  • TestMCDC_SYS_REQ_048_Row5_TruncatedValue
    mcdc_spec_witnesses_test.go:1702exercises 1 condition scenario
  • TestObligation_SYS_REQ_048
    obligation_evidence_test.go:408

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