Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ArrayEach addresses a well-formed empty JSON array, the parser shall emit no callbacks.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ArrayEach addresses a well-formed empty JSON array, the parser shall emit no callbacks.
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.
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.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- approved
- Reviewer
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · Codex · AI agent
- Modified
- Aug 20, 2026, 13:11 UTC · Buger
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-91
The formula says a well-formed empty array must produce zero callbacks. The empty-array fast path in arrayEachConfig (parser.go:1763) compares the first significant byte against '}' instead of ']', so a valid
[]fails the sentinel, falls into the element loop against the closing bracket, and returns MalformedArrayError rather than iterating zero times. This is the intentional demo defect tracked by KI-10 (proof/known-issues/KI-10.yaml, status:open, remediation = restore ']'), with a passing reproducer manifest (proof/evidence/KI-10-reproducer.yaml) and TestDemoKI10_EmptyArrayEach. The requirement's own witnesses (TestArrayEachEmpty, TestMCDC_SYS_REQ_028_Row3, TestObligation_SYS_REQ_028) assert zero callbacks on[], so verification honestly fails against the mutated sentinel; the contract and design are sound, the defect is tracked, so it stays approvable.Cited code (4)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
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 catalogueBehavior when inputs are absent, nil, zero-length, or blank.
ArrayEach on [] emits one spurious callback with a stale element slice, misleading the caller to process a phantom element from a stale buffer.
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
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.
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered 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).
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
| Name | Type | Direction | Description |
|---|---|---|---|
| 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_NonEmptyWellFormedexercises 1 condition scenario
- TestMCDC_SYS_REQ_028_Row2_EmptyMalformedexercises 1 condition scenario
- TestMCDC_SYS_REQ_028_Row3_InvariantViolationexercises 1 condition scenario
- TestArrayEachEmptyexercises 1 condition scenario
MC/DC truth table· 4 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | addressed_array_is_empty | addressed_array_is_well_formed | empty_array_produces_no_callbacks | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | T | F | T | addressed_array_is_empty | |
| 2 | T | F | F | T | addressed_array_is_well_formed | |
| 3 | T | T | F | F | addressed_array_is_empty | |
| 4 | T | T | T | T | empty_array_produces_no_callbacks |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
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 — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
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.