Proof Portal

Sign in
Projects

jsonparser

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

When the JSON input is incomplete or truncated before addressed lookup or no-key-path extraction can complete, including incomplete addressed strings, arrays, objects, or missing value tokens, the parser shall return a parse-related error and shall not report a successful lookup 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 JSON input is incomplete or truncated before addressed lookup or no-key-path extraction can complete, including incomplete addressed strings, arrays, objects, or missing value tokens, the parser shall return a parse-related error and shall not report a successful lookup result.

FRETish formula
the parser shall always satisfy !input_is_incomplete_during_lookup | returns_parse_error_for_incomplete_lookup

Rationale & tags

Why this requirement exists, and how it is categorised.

Incomplete or truncated input is a distinct externally visible failure mode in Get and should be modeled independently from successful lookup, empty-input, tolerated malformed-input, or not-found behavior.

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.

1 obligation · 1 discharged

Browse the catalogue
Discharged

Behavior when inputs are syntactically or structurally invalid.

Worst case if violatedCritical

Get on adversarial input like {"a": (no value token) drives nextToken to return -1; an unguarded data[i] dereference in the value classification step panics with index-out-of-range on network-reachable 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 !input_is_incomplete_during_lookup | returns_parse_error_for_incomplete_lookup

Variables

NameTypeDirectionDescription
input_is_incomplete_during_lookup—True when the input is truncated or incomplete before Get can complete the addressed lookup.
returns_parse_error_for_incomplete_lookup—True when Get reports a parse-related error for an incomplete or truncated lookup input.

Witnesses· 3 scenarios total

  • TestGetTruncatedReturnsError
    deep_spec_test.go:973
  • TestMCDC_SYS_REQ_017_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:403exercises 1 condition scenario
  • TestMCDC_SYS_REQ_017_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:415exercises 1 condition scenario
  • TestMCDC_SYS_REQ_017_Row3_ParseErrorReturned
    mcdc_spec_witnesses_test.go:426exercises 1 condition scenario
  • TestObligation_SYS_REQ_017
    obligation_evidence_test.go:230
  • 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