Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen Delete is called on input that is truncated at a value boundary (the exact PR
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 at a value boundary (the exact PR
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.
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.
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-30
deleteFoundConfig resolves the value via internalGetConfig and returns the original input unchanged on any parse error (parser.go:1284-1286). For input truncated at a value boundary (e.g.
{"test":1), the trailing-comma cleanup computes tokEnd=tokenEnd(data[endOffset:]) and short-circuits withif endOffset+tokEnd >= len(data) { return data, false }(parser.go:1291), so no out-of-range index or slice is taken and the caller's bytes are returned as-is. The deep_spec truncation cases and MCDC Row5 witness confirm no panic and original-input return.Cited code (3)
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":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.
- 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_at_value_boundary | (delete_returns_original_input_on_truncated_value & delete_completes_without_panic_on_truncated_value)
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| 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
- TestMCDC_SYS_REQ_048_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_048_Row2_InvariantViolationPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_048_Row3_InvariantViolationOriginalexercises 1 condition scenario
- TestMCDC_SYS_REQ_048_Row4_InvariantViolationNoPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_048_Row5_TruncatedValueexercises 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_completes_without_panic_on_truncated_value | delete_input_is_truncated_at_value_boundary | delete_returns_original_input_on_truncated_value | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | delete_input_is_truncated_at_value_boundary | |
| 2 | F | T | F | F | delete_input_is_truncated_at_value_boundary | |
| 3 | F | T | T | F | delete_completes_without_panic_on_truncated_value | |
| 4 | T | T | F | F | delete_returns_original_input_on_truncated_value | |
| 5 | T | T | T | T | delete_completes_without_panic_on_truncated_value |
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 (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)
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.