Proof Portal

Sign in
Projects

jsonparser

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

When the input is empty and a key path is provided, the parser shall return the defined not-found result with `NotExist`, offset `-1`, and `KeyPathNotFoundError`.

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 input is empty and a key path is provided, the parser shall return the defined not-found result with `NotExist`, offset `-1`, and `KeyPathNotFoundError`.

FRETish formula
the parser shall always satisfy !json_input_is_empty | !key_path_is_provided | returns_missing_path_result_for_empty_input

Rationale & tags

Why this requirement exists, and how it is categorised.

The current Get contract treats empty input as an addressed lookup miss rather than as a parsing error, so that edge case should be modeled explicitly.

decompositiongetedge-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 when inputs are absent, nil, zero-length, or blank.

Worst case if violatedLow

Get on a zero-length input with a path returns a stale value slice instead of KeyPathNotFoundError, mis-classifying empty input as a found path and leaking stale bytes.

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

Behavior specified when inputs are nil, null, or zero-value.

Worst case if violatedHigh

Get on nil data panics in nextToken at data[0] instead of returning NotExist with KeyPathNotFoundError, crashing the caller on a nil trust-boundary input.

Discharging evidence2/2 required witnessed
  • negativerequiredpresent
    Covered by 1 test
  • 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 !json_input_is_empty | !key_path_is_provided | returns_missing_path_result_for_empty_input

Variables

NameTypeDirectionDescription
json_input_is_empty—True when the provided lookup input is empty.
key_path_is_provided—True when the caller supplies at least one key-path segment for the lookup case under evaluation.
returns_missing_path_result_for_empty_input—True when Get reports the defined not-found outcome for an empty input with a provided key path.

Witnesses· 4 scenarios total

  • TestGetEmptyInputWithPath
    deep_spec_test.go:1010
  • checkOffsetBoundsGate
    json_fuzz_test.go:1081
  • TestMCDC_SYS_REQ_019_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:493exercises 1 condition scenario
  • TestMCDC_SYS_REQ_019_Row2_EmptyNoKeyPath
    mcdc_spec_witnesses_test.go:505exercises 1 condition scenario
  • TestMCDC_SYS_REQ_019_Row3_InvariantViolation
    mcdc_spec_witnesses_test.go:519exercises 1 condition scenario
  • TestMCDC_SYS_REQ_019_Row4_EmptyMissingPath
    mcdc_spec_witnesses_test.go:533exercises 1 condition scenario
  • TestObligation_SYS_REQ_019
    obligation_evidence_test.go:252
  • 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