Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ObjectEach encounters an object entry that is truncated (e.g., '{"a":1, "b":' where the second value is incomplete), the parser shall return a parse-related error and shall not panic.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ObjectEach encounters an object entry that is truncated (e.g., '{"a":1, "b":' where the second value is incomplete), the parser shall return a parse-related error and shall not panic.
the parser shall always satisfy !object_is_truncated_mid_entry | returns_error_for_truncated_object_entry
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Truncated mid-entry iteration in ObjectEach exercises Get on incomplete value tokens, which may trigger sentinel-value boundary conditions.
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, 18:00 UTC · Claude · 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-36
objectEachConfig fails loud on a truncated entry: after skipping the colon, config.Get on the incomplete value (e.g. '{"a":1,"b":') returns a parse error that is returned directly at parser.go:1998-1999, and truncation before the colon/next-token makes nextTokenConfig return -1 -> MalformedJsonError (parser.go:1937/1989). Every data[offset] index is guarded by a preceding nextTokenConfig/-1 check, so a truncated nested object like '{"a":{"b":1' returns an error without panicking. TestObjectEachTruncatedMidEntry confirms no panic across the truncated-value cases.
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 need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. 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 !object_is_truncated_mid_entry | returns_error_for_truncated_object_entry
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| object_is_truncated_mid_entry | — | True when ObjectEach encounters an object entry whose value is truncated or incomplete. | |
| returns_error_for_truncated_object_entry | — | True when ObjectEach returns a parse-related error for a truncated object entry, without panicking. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_054_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_054_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_054_Row3_TruncatedErrorexercises 1 condition scenario
MC/DC truth table· 3 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| # | object_is_truncated_mid_entry | returns_error_for_truncated_object_entry | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | object_is_truncated_mid_entry | |
| 2 | T | F | F | object_is_truncated_mid_entry | |
| 3 | T | T | T | returns_error_for_truncated_object_entry |
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 (2)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_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.