Proof Portal
jsonparser
ProbeLabsviewing a historical runWhen ObjectEach addresses a well-formed non-empty JSON object, the parser shall invoke the callback with the correct key, value, and value type tuple for each addressed object entry.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ObjectEach addresses a well-formed non-empty JSON object, the parser shall invoke the callback with the correct key, value, and value type tuple for each addressed object entry.
the parser shall always satisfy !addressed_object_is_well_formed | addressed_object_is_empty | object_callback_receives_entries
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Correct object entry reporting is a distinct externally visible contract from empty-object handling, malformed-input failure, and callback error propagation.
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 13, 2026, 17:10 UTC · Created via CLI
- 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-12
ObjectEach delegates to objectEachConfig, which satisfies !addressed_object_is_well_formed | addressed_object_is_empty | object_callback_receives_entries: malformed input returns MalformedObjectError/MalformedJsonError before any callback (the !well_formed disjunct), an empty object '{}' returns nil at the post-brace '}' check without invoking the callback (addressed_object_is_empty), and for each well-formed non-empty entry it extracts the key (unescaping when needed), skips the colon, resolves the value via config.Get, and invokes callback(key, value, valueType, offset+off). TestObjectEach plus the OOB-truncation boundary tests confirm correct per-entry tuples and no callback on malformed/empty objects.
Cited code (4)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
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_object_is_well_formed | addressed_object_is_empty | object_callback_receives_entries
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| addressed_object_is_well_formed | — | True when ObjectEach is operating on a well-formed addressed JSON object. | |
| addressed_object_is_empty | — | True when ObjectEach is operating on an addressed object that contains no entries. | |
| object_callback_receives_entries | — | True when ObjectEach invokes the callback with the correct key, value, and value-type tuple for each addressed object entry. |
Witnesses· 4 scenarios total
- TestMCDC_SYS_REQ_007_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_007_Row4_EmptyObjectexercises 1 condition scenario
- TestObjectEachexercises 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_object_is_empty | addressed_object_is_well_formed | object_callback_receives_entries | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | addressed_object_is_well_formed | |
| 2 | F | T | F | F | addressed_object_is_empty | |
| 3 | F | T | T | T | object_callback_receives_entries | |
| 4 | T | T | F | T | addressed_object_is_empty |
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.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
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 (3)
- aliases.goaliases.go
- fuzz.gofuzz.go
- parser.goparser.go
Tests to re-run (10)
- aliases_test.goaliases_test.go
- coverage_closure_test.gocoverage_closure_test.go
- dead_code_audit_oob_test.godead_code_audit_oob_test.go
- dead_code_audit_test.godead_code_audit_test.go
- fuzz_native_test.gofuzz_native_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- mcdc_supplement_test.gomcdc_supplement_test.go
- parser_test.goparser_test.go
- path_fuzz_test.gopath_fuzz_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.