Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen Delete is called on input that is truncated mid-structure (e.g., an object with an unclosed nested object like '{"a":{"b":1'), the parser shall return the original byte payload unchanged and shall not panic.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Delete is called on input that is truncated mid-structure (e.g., an object with an unclosed nested object like '{"a":{"b":1'), the parser shall return the original byte payload unchanged and shall not panic.
the parser shall always satisfy !delete_input_is_truncated_mid_structure | (delete_returns_original_input_on_truncated_structure & delete_completes_without_panic_on_truncated_structure)
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Mid-structure truncation in Delete exercises both internalGet and findKeyStart with incomplete structural input, which is a distinct truncation pattern from at-value-boundary.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
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 catalogueDelete on {"a":{"b":1 (unclosed nested object) drives findKeyStart into recursion that over-reads; the cleanup data[prevTok] dereference at parser.go:907 panics with index-out-of-range.
- nominalrequiredpresentCovered 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).
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_mid_structure | (delete_returns_original_input_on_truncated_structure & delete_completes_without_panic_on_truncated_structure)
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| delete_input_is_truncated_mid_structure | — | True when Delete is called on input truncated mid-structure with unclosed nested objects or arrays. | |
| delete_returns_original_input_on_truncated_structure | — | True when Delete returns the original byte payload unchanged for mid-structure truncated input. | |
| delete_completes_without_panic_on_truncated_structure | — | True when Delete completes without panicking on mid-structure truncated input. |
Witnesses· 5 scenarios total
- TestDeleteTruncatedMidStructuredeep_spec_test.go:287
- TestMCDC_SYS_REQ_056_Row1_TriggerFalsemcdc_spec_witnesses_test.go:1962exercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row2_InvariantViolationPanicmcdc_spec_witnesses_test.go:1972exercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row3_InvariantViolationOriginalmcdc_spec_witnesses_test.go:1982exercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row4_InvariantViolationNoPanicmcdc_spec_witnesses_test.go:1992exercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row5_TruncatedStructuremcdc_spec_witnesses_test.go:2002exercises 1 condition scenario
- TestObligation_SYS_REQ_056obligation_evidence_test.go:454
Its place
This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.
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.
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
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.