Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen Delete is called with an array-element path on input where the array is truncated (e.g., Delete([]byte(`{"a":[1,2`), "a", "[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 with an array-element path on input where the array is truncated (e.g., Delete([]byte(`{"a":[1,2`), "a", "[1]")), the parser shall return the original byte payload unchanged and shall not panic.
the parser shall always satisfy !delete_array_input_is_truncated | (delete_returns_original_input_on_truncated_array & delete_completes_without_panic_on_truncated_array)
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Array deletion on truncated input exercises the same tokenEnd sentinel pattern as object deletion but through a different code path in Delete (the array branch).
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
- Apr 14, 2026, 18:00 UTC · agent:claude
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
No obligations recorded for this requirement
Proof obligations are recorded once evidence is generated. None have been captured here yet — this is expected, not a gap in the requirement itself. A required class of evidence the requirement must witness — the bridge between the requirement existing and it being proven.
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_array_input_is_truncated | (delete_returns_original_input_on_truncated_array & delete_completes_without_panic_on_truncated_array)
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| delete_array_input_is_truncated | — | True when Delete is called with an array-element path on input where the array is truncated. | |
| delete_returns_original_input_on_truncated_array | — | True when Delete returns the original byte payload unchanged for truncated array input. | |
| delete_completes_without_panic_on_truncated_array | — | True when Delete completes without panicking on truncated array input. |
Witnesses· 5 scenarios total
- TestDeleteTruncatedArrayInputdeep_spec_test.go:258
- TestMCDC_SYS_REQ_050_Row1_TriggerFalsemcdc_spec_witnesses_test.go:1754exercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row2_InvariantViolationPanicmcdc_spec_witnesses_test.go:1769exercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row3_InvariantViolationOriginalmcdc_spec_witnesses_test.go:1779exercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row4_InvariantViolationNoPanicmcdc_spec_witnesses_test.go:1789exercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row5_TruncatedArraymcdc_spec_witnesses_test.go:1799exercises 1 condition scenario
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 (2)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_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.