Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsThe fastest JSON parser for Go — formally verified with ReqProof (real library, master).
When ArrayEach addresses a well-formed non-empty JSON array, the parser shall invoke the callback for each addressed array element in encounter order.
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 non-empty JSON array, the parser shall invoke the callback for each addressed array element in encounter order.
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.
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.
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
- Jul 27, 2026, 06:53 UTC
History
- Created
- Apr 13, 2026, 17:10 UTC · Created via CLI
- Modified
- Jul 27, 2026, 06:53 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.
Every recorded revision of this object's source — newest first, each with the commit message and its file-level diff.
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 catalogueOutput identical regardless of collection ordering or runtime conditions.
ArrayEach invokes callbacks in non-deterministic encounter order on identical input, breaking caller-side slice-append or sum accumulation invariants.
- 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 | array_callback_receives_elements_in_order
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. | |
| array_callback_receives_elements_in_order | — | True when ArrayEach invokes the callback for each addressed array element in encounter order. |
Witnesses· 4 scenarios total
- TestMCDC_SYS_REQ_006_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_006_Row4_EmptyArrayexercises 1 condition scenario
- TestArrayEachexercises 2 condition scenarios
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 | array_callback_receives_elements_in_order | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | addressed_array_is_well_formed | |
| 2 | F | T | F | F | addressed_array_is_empty | |
| 3 | F | T | T | T | array_callback_receives_elements_in_order | |
| 4 | T | T | F | T | addressed_array_is_empty |
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 (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.