Proof Portal

Sign in
Projects

jsonparser

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

When ArrayEach addresses a well-formed non-empty JSON array, the parser shall invoke the callback for each addressed array element in encounter order.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

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

Description

When ArrayEach addresses a well-formed non-empty JSON array, the parser shall invoke the callback for each addressed array element in encounter order.

FRETish formula
the parser shall always satisfy !addressed_array_is_well_formed | addressed_array_is_empty | array_callback_receives_elements_in_order

Rationale & tags

Why this requirement exists, and how it is categorised.

Ordered iteration over addressed array contents is a distinct externally visible behavior from empty-array handling and malformed-input handling.

decompositionarrayeachtraversal

Verification & provenance

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

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:buger · lead_engineer
Reviewed
Jul 27, 2026, 06:53 UTC
“Re-approved after ArrayEach non-array-root fix (DEFECT-260727-ARR1): root-type guard prevents spurious callback on non-array input.”

History

Created
Apr 13, 2026, 17:10 UTC · human:cli
Modified
Jul 27, 2026, 06:53 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

ArrayEach invokes callbacks in non-deterministic encounter order on identical input, breaking caller-side slice-append or sum accumulation 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 !addressed_array_is_well_formed | addressed_array_is_empty | array_callback_receives_elements_in_order

Variables

NameTypeDirectionDescription
addressed_array_is_well_formed—True when ArrayEach is operating on a well-formed addressed JSON array.
addressed_array_is_empty—True when ArrayEach is operating on an addressed array that contains no elements.
array_callback_receives_elements_in_order—True when ArrayEach invokes the callback for each addressed array element in encounter order.

Witnesses· 4 scenarios total

  • TestArrayEach_OOB_MalformedElements
    dead_code_audit_oob_test.go:86
  • TestRemoval1_ArrayEach_LoopExitsOnEmptyArray
    dead_code_audit_test.go:14
  • TestRemoval1_ArrayEach_LoopExitsOnSingleElement
    dead_code_audit_test.go:24
  • TestRemoval6_ArrayEach_GetReturnsZeroOffset
    dead_code_audit_test.go:444
  • TestRemoval6_ArrayEach_EmptyStringElement
    dead_code_audit_test.go:491
  • TestRemoval6_ArrayEach_WhitespaceOnlyInput
    dead_code_audit_test.go:515
  • TestStress_ArrayEach_NestedEmpty
    dead_code_audit_test.go:609
  • TestMCDC_SYS_REQ_006_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:135exercises 1 condition scenario
  • TestMCDC_SYS_REQ_006_Row4_EmptyArray
    mcdc_spec_witnesses_test.go:152exercises 1 condition scenario
  • TestArrayEachSupplementalErrors
    mcdc_supplement_test.go:239
  • TestCodeMCDC_ArrayEachNormalIteration
    mcdc_supplement_test.go:625
  • TestCodeMCDC_ArrayEachNoError
    mcdc_supplement_test.go:645
  • TestObligation_SYS_REQ_006
    obligation_evidence_test.go:142
  • TestArrayEach
    parser_test.go:1629exercises 2 condition scenarios
  • TestPropertyArrayEachCompleteness
    property_test.go:341

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
2
Tests
8
At-risk contracts
0

Files to re-check (2)

  • aliases.goaliases.go
  • parser.goparser.go

Tests to re-run (8)

  • aliases_test.goaliases_test.go
  • dead_code_audit_oob_test.godead_code_audit_oob_test.go
  • dead_code_audit_test.godead_code_audit_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_test.goparser_test.go
  • property_test.goproperty_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