Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-028SystemReview

When ArrayEach addresses a well-formed empty JSON array, the parser shall emit no callbacks.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsMediumworst 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 empty JSON array, the parser shall emit no callbacks.

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

Rationale & tags

Why this requirement exists, and how it is categorised.

Empty-array behavior is externally visible and should be reviewed independently from non-empty iteration and malformed-input failure.

decompositionarrayeachedge-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 levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 15:45 UTC · agent:codex
Modified
Jul 26, 2026, 14:54 UTC · human:cli

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

ArrayEach on [] emits one spurious callback with a stale element slice, misleading the caller to process a phantom element from a stale buffer.

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

ArrayEach on nil data panics in nextToken at data[0] instead of returning without invoking the callback, 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 !addressed_array_is_well_formed | !addressed_array_is_empty | empty_array_produces_no_callbacks

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.
empty_array_produces_no_callbacks—True when ArrayEach emits no callbacks for a well-formed empty addressed array.

Witnesses· 4 scenarios total

  • TestMCDC_SYS_REQ_028_Row1_NonEmptyWellFormed
    mcdc_spec_witnesses_test.go:955exercises 1 condition scenario
  • TestMCDC_SYS_REQ_028_Row2_EmptyMalformed
    mcdc_spec_witnesses_test.go:971exercises 1 condition scenario
  • TestMCDC_SYS_REQ_028_Row3_InvariantViolation
    mcdc_spec_witnesses_test.go:986exercises 1 condition scenario
  • TestObligation_SYS_REQ_028
    obligation_evidence_test.go:286
  • TestArrayEachEmpty
    parser_test.go:1715exercises 1 condition scenario

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

Files to re-check (2)

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

Tests to re-run (3)

  • 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