Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-023SystemApproved

When the current path segment is a valid array index but the index is out of bounds for the addressed array, Get shall return the defined not-found result.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceBFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When the current path segment is a valid array index but the index is out of bounds for the addressed array, Get shall return the defined not-found result.

FRETish formula
the parser shall always satisfy !path_segment_is_array_index | !array_index_segment_is_valid | !array_index_is_out_of_bounds | returns_oob_array_index_not_found

Rationale & tags

Why this requirement exists, and how it is categorised.

Out-of-bounds array access is behaviorally distinct from malformed index syntax and from successful element resolution.

decompositiongetarray-indexedge-case

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelB
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:buger · lead_engineer
Reviewed
Jul 26, 2026, 15:21 UTC
“Final re-approval after L3 strict posture sweep (hazard+obligation+coverage work)”

History

Created
Apr 14, 2026, 00:00 UTC · human:cli
Modified
Jul 26, 2026, 15:21 UTC · human:buger

Obligations

What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.

2 obligations · 2 discharged

Browse the catalogue
Discharged

Behavior at limits, thresholds, and edge-of-range values.

Worst case if violatedMedium

Get with path [5] on [1,2,3] returns the last element instead of not-found due to an off-by-one in the array bounds check, masking an out-of-range access as a valid value.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test
Discharged

Behavior for unusual but valid input combinations.

Worst case if violatedMedium

Get on a single-element array with index [0] returns wrong element due to off-by-one in i+1 increment, or panics on [1] due to unchecked post-increment dereference.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered 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).

FRETish formula

the parser shall always satisfy !path_segment_is_array_index | !array_index_segment_is_valid | !array_index_is_out_of_bounds | returns_oob_array_index_not_found

Variables

NameTypeDirectionDescription
path_segment_is_array_index—True when the current lookup path segment is interpreted as an array index.
array_index_segment_is_valid—True when the current array-index path segment has valid index syntax.
array_index_is_out_of_bounds—True when the addressed array index exceeds the bounds of the addressed array.
returns_oob_array_index_not_found—True when Get reports the defined not-found outcome for a valid but out-of-bounds array index.

Witnesses· 5 scenarios total

  • TestGetArrayIndexOutOfBounds
    deep_spec_test.go:1057
  • TestMCDC_SYS_REQ_023_Row1_InBounds
    mcdc_spec_witnesses_test.go:714exercises 1 condition scenario
  • TestMCDC_SYS_REQ_023_Row2_InvalidOutOfBounds
    mcdc_spec_witnesses_test.go:726exercises 1 condition scenario
  • TestMCDC_SYS_REQ_023_Row3_NotArraySegment
    mcdc_spec_witnesses_test.go:735exercises 1 condition scenario
  • TestMCDC_SYS_REQ_023_Row4_InvariantViolation
    mcdc_spec_witnesses_test.go:750exercises 1 condition scenario
  • TestMCDC_SYS_REQ_023_Row5_OobNotFound
    mcdc_spec_witnesses_test.go:761exercises 1 condition scenario
  • TestObligation_SYS_REQ_023
    obligation_evidence_test.go:269
  • TestGetRequirementSlices
    parser_test.go:1390

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Open in graph

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.

If you change this

Requirements
0
Files
1
Tests
4
At-risk contracts
0

Files to re-check (1)

  • parser.goparser.go

Tests to re-run (4)

  • deep_spec_test.godeep_spec_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_evidence_test.goobligation_evidence_test.go
  • parser_test.goparser_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.

Sign in to discuss this with the proof team.Sign in