Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen ArrayEach receives malformed or otherwise unusable addressed array input, the parser shall return an error.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ArrayEach receives malformed or otherwise unusable addressed array input, the parser shall return an error. When the addressed root value is not an array (object, number, string, boolean, null) and no key path is provided, the parser shall return MalformedArrayError WITHOUT invoking the callback — the previous implementation emitted one spurious callback with a misparsed token before erroring (DEFECT-260727-ARR1).
the parser shall always satisfy addressed_array_is_well_formed | malformed_array_input_returns_error
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Malformed-array failure is a distinct observable behavior class and should not be hidden inside the ordered-iteration or empty-array contracts.
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
- human:buger · lead_engineer
- Reviewed
- Jul 27, 2026, 06:53 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · agent:codex
- 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.
2 obligations · 2 discharged
Browse the catalogueBehavior when inputs are syntactically or structurally invalid.
ArrayEach on adversarial input like [1,{ drives nextToken past EOF; an unguarded i+1 increment in the iteration loop panics with index-out-of-range on network-reachable input.
- negativerequiredpresentCovered by 2 tests
- nominalrequiredpresentCovered by 1 test
ArrayEach on a non-array root value (object, number, bool, null) without a key path invoked the callback ONCE with the first content token misinterpreted as an array element (e.g. an object key parsed as a string element), then returned MalformedArrayError. A caller performing side effects in the callback observed a spurious invocation on input that is not an array at all. Fixed in DEFECT-260727-ARR1; regression test TestArrayEachNonArrayRootNoCallback_SYS029 locks all non-array root type partitions.
- negativerecommendedpresentCovered 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 | malformed_array_input_returns_error
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| addressed_array_is_well_formed | — | True when ArrayEach is operating on a well-formed addressed JSON array. | |
| malformed_array_input_returns_error | — | True when ArrayEach returns an error for malformed or unusable array input. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_029_Row1_InvariantViolationmcdc_spec_witnesses_test.go:1006exercises 1 condition scenario
- TestMCDC_SYS_REQ_029_Row2_WellFormedmcdc_spec_witnesses_test.go:1015exercises 1 condition scenario
- TestObligation_SYS_REQ_029obligation_evidence_test.go:304
- TestArrayEachWithWhiteSpaceparser_test.go:1663exercises 1 condition scenario
- TestArrayEachNonArrayRootNoCallback_SYS029parser_test.go:2523
Its place
This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.
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.
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
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.