Proof Portal

Sign in
Projects

jsonparser

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

When the JSON input is well formed, a key path is provided, and the addressed path exists, the parser shall return the addressed value slice, the corresponding value type classification, the end offset of that value, and no error.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceBFindingsLowworst 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, a key path is provided, and the addressed path exists, the parser shall return the addressed value slice, the corresponding value type classification, the end offset of that value, and no error.

FRETish formula
the parser shall always satisfy !json_input_is_well_formed | !key_path_is_provided | !addressed_path_exists | returns_existing_path_lookup_result

Rationale & tags

Why this requirement exists, and how it is categorised.

The exported Get API is the fundamental primitive that all typed accessor helpers build on, so successful addressed lookup should be specified independently from not-found, empty-input, incomplete-input, no-key-path behavior, and lower-level path interpretation rules.

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 13, 2026, 16:22 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

Output identical regardless of collection ordering or runtime conditions.

Worst case if violatedMedium

Get on identical well-formed input returns a different (value,start,end) triple across calls; an offset-math layer downstream computes value[end-start:] past the buffer and slices out of range, panicking the caller.

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 | !addressed_path_exists | returns_existing_path_lookup_result

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.
addressed_path_exists—True when the requested key path resolves to a value in the JSON input under evaluation.
returns_existing_path_lookup_result—True when Get returns the addressed value, value type, end offset, and no error for a well-formed existing path lookup.

Witnesses· 6 scenarios total

  • TestEqual
    bytes_unsafe_test.go:32
  • BenchmarkEqualStr
    bytes_unsafe_test.go:56
  • BenchmarkBytesEqualStrSafe
    bytes_unsafe_test.go:64
  • BenchmarkBytesEqualStrUnsafeSlower
    bytes_unsafe_test.go:73
  • TestRemoval2_GetType_NumberAtEndOfInput
    dead_code_audit_test.go:130
  • TestRemoval2_GetType_BooleanAtEndOfInput
    dead_code_audit_test.go:152
  • TestRemoval2_GetType_NullAtEndOfInput
    dead_code_audit_test.go:166
  • TestRemoval2_Inconsistency_TruncatedNumber
    dead_code_audit_test.go:180
  • TestRemoval5_SearchKeys_ArrayIndex_Valid
    dead_code_audit_test.go:400
  • TestRemoval5_SearchKeys_ArrayIndex_MalformedNoClose
    dead_code_audit_test.go:410
  • TestRemoval5_SearchKeys_ArrayIndex_TooShort
    dead_code_audit_test.go:420
  • TestRemoval5_SearchKeys_ArrayIndex_NestedObject
    dead_code_audit_test.go:430
  • TestRemoval7_NextToken_EmptyInput
    dead_code_audit_test.go:536
  • TestRemoval7_NextToken_WhitespaceOnly
    dead_code_audit_test.go:544
  • TestRemoval7_FindKeyStart_NextTokenGuaranteesNonEmpty
    dead_code_audit_test.go:552
  • TestStress_Get_BareTruncatedValue
    dead_code_audit_test.go:655
  • FuzzTokenStartNative
    fuzz_native_test.go:176
  • TestCodeMCDC_TokenStartCarriageReturn
    mcdc_code_supplement_test.go:100
  • TestCodeMCDC_TokenStartTab
    mcdc_code_supplement_test.go:107
  • TestCodeMCDC_TokenEndTab
    mcdc_code_supplement_test.go:114
  • TestCodeMCDC_TokenStartDirect
    mcdc_code_supplement_test.go:23
  • TestCodeMCDC_TokenEndDirect
    mcdc_code_supplement_test.go:44
  • TestCodeMCDC_TokenStartNewline
    mcdc_code_supplement_test.go:91
  • TestMCDC_SYS_REQ_001_Row2_TriggerFalse
    mcdc_spec_witnesses_test.go:30exercises 1 condition scenario
  • TestMCDC_SYS_REQ_001_Row4_InvariantViolation
    mcdc_spec_witnesses_test.go:45exercises 1 condition scenario
  • TestCodeMCDC_SearchKeysArrayKeyValidation
    mcdc_supplement_test.go:517
  • TestCodeMCDC_SearchKeysKeyLevelMatch
    mcdc_supplement_test.go:548
  • TestCodeMCDC_GetTypeTokenEndNotNegative
    mcdc_supplement_test.go:594
  • TestCodeMCDC_FindKeyStartArrayRoot
    mcdc_supplement_test.go:663
  • TestCodeMCDC_SearchKeysKeyLevelMismatch
    mcdc_supplement_test.go:817
  • TestCodeMCDC_SearchKeysArrayKeyNotBracket
    mcdc_supplement_test.go:836
  • TestObligation_SYS_REQ_001
    obligation_evidence_test.go:104
  • TestPanickingErrors
    parser_error_test.go:26
  • TestGet
    parser_test.go:1370exercises 4 condition scenarios
  • TestGetSlice
    parser_test.go:1614
  • TestPropertyConcurrentReadsSafe
    property_test.go:1053
  • TestPropertyGetRoundTrip
    property_test.go:165
  • TestPropertySearchKeysDeterminism
    property_test.go:588
  • TestPropertyFindKeyStartDeterminism
    property_test.go:612
  • TestPropertyGetTypeClassification
    property_test.go:701
  • TestPropertyInternalGetConsistentWithGet
    property_test.go:816
  • TestPropertyValueTypeStringer
    property_test.go:897
  • TestOracleGetRoundTrip
    reference_oracle_test.go:452

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
3
Tests
12
At-risk contracts
0

Files to re-check (3)

  • fuzz.gofuzz.go
  • parser.goparser.go
  • path_compiler.gopath_compiler.go

Tests to re-run (12)

  • bytes_unsafe_test.gobytes_unsafe_test.go
  • dead_code_audit_test.godead_code_audit_test.go
  • fuzz_native_test.gofuzz_native_test.go
  • mcdc_code_supplement_test.gomcdc_code_supplement_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • mcdc_supplement_test.gomcdc_supplement_test.go
  • obligation_evidence_test.goobligation_evidence_test.go
  • parser_error_test.goparser_error_test.go
  • parser_test.goparser_test.go
  • path_compiler_test.gopath_compiler_test.go
  • property_test.goproperty_test.go
  • reference_oracle_test.goreference_oracle_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