Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen the current path segment is a negative array index (e.g., "[-1]"), Get shall return the defined not-found result because negative indexing is not supported by the JSON path syntax.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the current path segment is a negative array index (e.g., "[-1]"), Get shall return the defined not-found result because negative indexing is not supported by the JSON path syntax.
the parser shall always satisfy !path_segment_is_negative_array_index | returns_not_found_for_negative_array_index
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Negative array indices are not part of the documented path syntax. The parser should deterministically handle them rather than producing undefined behavior.
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-29
For an array-index segment, searchKeysConfig parses the index with strconv.Atoi (parser.go:577); a negative literal like [-1] parses to aIdx=-1 with no error. It then walks the array via arrayEachConfig comparing the running curIdx (which starts at 0 and only increments) against aIdx (parser.go:586), so a negative target is never matched and valueFound stays nil, causing the return of the not-found sentinel -1 (parser.go:597-598). Get therefore surfaces KeyPathNotFoundError, matching the FRETish obligation; the deep_spec and MCDC Row3 negative-index witnesses confirm this.
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 catalogueGet on path [-1] is parsed by strconv.Atoi as -1 and then used as data[i-1] or an array element index, wrapping to a large unsigned index and panicking 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 !path_segment_is_negative_array_index | returns_not_found_for_negative_array_index
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| path_segment_is_negative_array_index | — | True when the current path segment is a negative array index such as "[-1]". | |
| returns_not_found_for_negative_array_index | — | True when Get returns the defined not-found result for a negative array index because negative indexing is not supported. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_047_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_047_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_047_Row3_NegativeNotFoundexercises 1 condition scenario
MC/DC truth table· 3 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| # | path_segment_is_negative_array_index | returns_not_found_for_negative_array_index | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | path_segment_is_negative_array_index | |
| 2 | T | F | F | path_segment_is_negative_array_index | |
| 3 | T | T | T | returns_not_found_for_negative_array_index |
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)
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.