Proof Portal
jsonparser
ProbeLabs23 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
- 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-38
Delete resolves the target via internalGetConfig, and when the addressed value is truncated mid-structure (e.g. '{"a":{"b":1') that call returns an error and deleteFoundConfig returns the original data slice unchanged with found=false (parser.go:1283-1286); the tokenEnd sentinel path also returns data unchanged when no trailing delimiter is found (parser.go:1291-1294). Delete() discards the found flag and returns that unchanged payload, and all subsequent index math is bounds-checked, so no panic occurs. The five MCDC rows and TestDeleteTruncatedMidStructure confirm unchanged output and no panic.
Cited code (4)
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
- TestMCDC_SYS_REQ_056_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row2_InvariantViolationPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row3_InvariantViolationOriginalexercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row4_InvariantViolationNoPanicexercises 1 condition scenario
- TestMCDC_SYS_REQ_056_Row5_TruncatedStructureexercises 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_structure | delete_input_is_truncated_mid_structure | delete_returns_original_input_on_truncated_structure | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | delete_input_is_truncated_mid_structure | |
| 2 | F | T | F | F | delete_input_is_truncated_mid_structure | |
| 3 | F | T | T | F | delete_completes_without_panic_on_truncated_structure | |
| 4 | T | T | F | F | delete_returns_original_input_on_truncated_structure | |
| 5 | T | T | T | T | delete_completes_without_panic_on_truncated_structure |
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.