Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen GetInt is called on JSON containing numeric edge cases such as numbers with many leading zeros, maximum-length digit strings, or values at float64 precision boundaries, the parser shall return a correct int64 result or a well-defined error without panicking.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetInt is called on JSON containing numeric edge cases such as numbers with many leading zeros, maximum-length digit strings, or values at float64 precision boundaries, the parser shall return a correct int64 result or a well-defined error without panicking.
the parser shall always satisfy !getint_input_has_large_number_edge_case | getint_handles_large_numbers_safely
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Large and edge-case numbers in JSON are common in financial and scientific APIs. The parser must not silently truncate or corrupt these values.
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 21, 2026, 00: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-76
GetInt routes through ParseInt -> parseInt (bytes.go:9), whose fast path is gated on
l-i < 20(bytes.go:27) — the KI-7 intentional defect that widens the threshold so any 19-digit integer skips the overflow-checked slow path. I ran TestGetIntLargeNumberEdgeCases: max/min int64 pass, but{"n":9223372036854775808}(MaxInt64+1) wraps silently to -9223372036854775808 with a nil error instead of the required well-defined error, so the subtest FAILS. This directly contradicts the requirement's 'correct int64 result or well-defined error' clause; verification is honestly failing on a defect tracked by KI-7.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 !getint_input_has_large_number_edge_case | getint_handles_large_numbers_safely
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getint_input_has_large_number_edge_case | — | True when GetInt addresses a JSON number with edge-case formatting like leading zeros or max-length digit strings. | |
| getint_handles_large_numbers_safely | — | True when GetInt returns correct int64 or well-defined error for large-number edge cases. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_096_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_096_Row2_InvariantViolationexercises 1 condition scenario
- TestGetIntLargeNumberEdgeCasesexercises 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| # | getint_handles_large_numbers_safely | getint_input_has_large_number_edge_case | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | getint_input_has_large_number_edge_case | |
| 2 | F | T | F | getint_handles_large_numbers_safely | |
| 3 | T | T | T | getint_handles_large_numbers_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 implementation linked
No source files are traced to this requirement yet.
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
Tests to re-run (2)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_property_test.goobligation_property_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.