Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ParseInt receives integer tokens at the exact int64 boundary values (9223372036854775807 for max, -9223372036854775808 for min), the parser shall return the correct int64 value without overflow error.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseInt receives integer tokens at the exact int64 boundary values (9223372036854775807 for max, -9223372036854775808 for min), the parser shall return the correct int64 value without overflow error.
the parser shall always satisfy !raw_int_token_is_at_int64_max_boundary | returns_correct_value_at_int64_boundary
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The int64 boundary is a critical boundary value where off-by-one errors in overflow detection would produce incorrect results. Both max positive and min negative must be tested.
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-40
Both exact int64 boundaries decode correctly. Max '9223372036854775807' (19 digits) takes the fast path (bytes.go:40) and accumulates to exactly maxInt64 with no intermediate overflow; min '-9223372036854775808' (l-i=19) also takes the fast path where v=10*v+d wraps to math.MinInt64 and the neg branch's '-v' wraps back to MinInt64 (bytes.go:46,49-51), and ParseInt returns v with nil error (parser.go:2168-2176). TestParseIntBoundaryValues asserts both equal math.MaxInt64/MinInt64. KI-2 (sign-only '-') is linked here but is status=fixed via the 'if i == l' guard (bytes.go:34-36) and concerns a different partition, so no open defect affects the boundary formula.
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 !raw_int_token_is_at_int64_max_boundary | returns_correct_value_at_int64_boundary
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_int_token_is_at_int64_max_boundary | — | True when ParseInt receives an integer token at the exact int64 boundary values (max 9223372036854775807 or min -9223372036854775808). | |
| returns_correct_value_at_int64_boundary | — | True when ParseInt returns the correct int64 value at the exact boundary without overflow error. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_058_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_058_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_058_Row3_BoundaryValueexercises 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| # | raw_int_token_is_at_int64_max_boundary | returns_correct_value_at_int64_boundary | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | raw_int_token_is_at_int64_max_boundary | |
| 2 | T | F | F | raw_int_token_is_at_int64_max_boundary | |
| 3 | T | T | T | returns_correct_value_at_int64_boundary |
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 (1)
- 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)
Changes
Semantic changes that move or scope this requirement — the intended work touching it. Each links to the full change.
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.