Proof Portal
jsonparser
ProbeLabs23 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
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 18:00 UTC · Claude · AI agent
- Modified
- Aug 20, 2026, 13:11 UTC · Buger
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-32
For an array-element path (last key
[N]) the array branch calls internalGetConfig with the full key list and returns the original input on error (parser.go:1320-1323); a truncated array such as{"a":[1,2yields MalformedArrayError from blockEnd, so the untouched payload is returned. Even when a truncated element resolves at end-of-input, the trailing-comma cleanup guards withendOffset+tokEnd >= len(data)before any deref (parser.go:1328), again returning data unchanged. No unchecked index is taken, so no panic. MCDC Row5 truncated-array witness passes.Cited code (3)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. Nothing here means unknown — not that the requirement has no obligations.
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
- TestMCDC_SYS_REQ_050_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row2_InvariantViolationPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row3_InvariantViolationOriginalexercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row4_InvariantViolationNoPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_050_Row5_TruncatedArrayexercises 1 condition scenario
MC/DC truth table· 5 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | delete_array_input_is_truncated | delete_completes_without_panic_on_truncated_array | delete_returns_original_input_on_truncated_array | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | delete_array_input_is_truncated | |
| 2 | T | F | F | F | delete_array_input_is_truncated | |
| 3 | T | F | T | F | delete_completes_without_panic_on_truncated_array | |
| 4 | T | T | F | F | delete_returns_original_input_on_truncated_array | |
| 5 | T | T | T | T | delete_completes_without_panic_on_truncated_array |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
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 — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
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)
Changes
Semantic changes that move or scope this requirement — the intended work touching it. Each links to the full change.
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.