Proof Portal

Sign in
Projects

jsonparser

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

When the JSON input is well formed and no key path is provided, the parser shall return the closest complete root JSON value according to the API contract, including complete object, array, string, number, boolean, or null values.

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 well formed and no key path is provided, the parser shall return the closest complete root JSON value according to the API contract, including complete object, array, string, number, boolean, or null values.

FRETish formula
the parser shall always satisfy !json_input_is_well_formed | key_path_is_provided | returns_root_value_without_key_path

Rationale & tags

Why this requirement exists, and how it is categorised.

Get has special root-extraction behavior when no key path is provided, so that contract should be modeled independently from addressed lookup.

decompositionget

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

Applying the operation twice produces the same result as applying once.

Worst case if violatedMedium

Get with no path returns different root slices across calls on identical input (e.g. trims surrounding whitespace inconsistently), corrupting downstream equality or hash invariants.

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 !json_input_is_well_formed | key_path_is_provided | returns_root_value_without_key_path

Variables

NameTypeDirectionDescription
json_input_is_well_formed—True when the provided JSON byte slice is well formed for the lookup case under evaluation.
key_path_is_provided—True when the caller supplies at least one key-path segment for the lookup case under evaluation.
returns_root_value_without_key_path—True when Get returns the closest complete root JSON value for a well-formed input when no key path is provided.

Witnesses· 4 scenarios total

  • TestGetNoKeyPathReturnsRoot
    deep_spec_test.go:994
  • TestMCDC_SYS_REQ_018_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:439exercises 1 condition scenario
  • TestMCDC_SYS_REQ_018_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:451exercises 1 condition scenario
  • TestMCDC_SYS_REQ_018_Row3_RootValueReturned
    mcdc_spec_witnesses_test.go:465exercises 1 condition scenario
  • TestMCDC_SYS_REQ_018_Row4_KeyPathProvided
    mcdc_spec_witnesses_test.go:477exercises 1 condition scenario
  • TestObligation_SYS_REQ_018
    obligation_evidence_test.go:243
  • 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