Proof Portal
jsonparser
ProbeLabsviewing a historical runWhen EachKey encounters a tokenEnd sentinel value (len(data)) during multi-path scanning, the parser shall treat it as an end-of-input condition and return -1 or error rather than using it as an unchecked array index.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When EachKey encounters a tokenEnd sentinel value (len(data)) during multi-path scanning, the parser shall treat it as an end-of-input condition and return -1 or error rather than using it as an unchecked array index.
the parser shall always satisfy !eachkey_tokenEnd_sentinel_reached | eachkey_handles_sentinel_safely
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
EachKey uses searchKeys and Get internally. The same tokenEnd sentinel patterns that caused PR
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-65
EachKey (parser.go:642) guards every end-of-input/sentinel condition before using an offset as an index: a truncated key makes stringEnd return -1 -> return -1 (parser.go:674), a missing value token makes nextToken return -1 -> return -1 (parser.go:682), a level<1 underflow calls back with MalformedJsonError and returns -1 (parser.go:709), and an unterminated array makes blockEnd return -1 -> return -1 (parser.go:840). Because the loop is bounded by
for i < lnand each nextToken/stringEnd result is checked against -1, the tokenEnd/len(data) sentinel is treated as end-of-input rather than an unchecked index. TestEachKeySentinelHandling exercises{"a,{"a:,[1,2, and{"a":1under a recover() and observes no panic.Cited code (4)
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 catalogueEachKeys uses the tokenEnd sentinel len(data) as an array index into data[] during multi-path scan (e.g. data[tokenEnd(offset)]), panicking with index-out-of-range instead of returning -1.
- 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 !eachkey_tokenEnd_sentinel_reached | eachkey_handles_sentinel_safely
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| eachkey_tokenEnd_sentinel_reached | — | True when EachKey encounters a tokenEnd sentinel value during multi-path scanning. | |
| eachkey_handles_sentinel_safely | — | True when EachKey treats the tokenEnd sentinel as an end-of-input condition and returns safely. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_085_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_085_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_085_Row3_SentinelHandledexercises 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| # | eachkey_handles_sentinel_safely | eachkey_tokenEnd_sentinel_reached | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | eachkey_tokenEnd_sentinel_reached | |
| 2 | F | T | F | eachkey_handles_sentinel_safely | |
| 3 | T | T | T | eachkey_handles_sentinel_safely |
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 (1)
- parser.goparser.go
Tests to re-run (3)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_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.