Proof Portal

Projects

jsonparser

ProbeLabsviewing a historical run
Viewing historical run 96a2d33Aug 20, 2026, 02:30 PMproof-demoaudited with uncommitted changes — showing the committed treeBack to current
All requirements
RequirementSYS-REQ-059SystemReview

When ParseInt receives an integer token that is exactly one beyond the int64 range (9223372036854775808 for max+1, -9223372036854775809 for min-1), the parser shall return OverflowIntegerError.

1 open known issue affect this requirement (worst severity: High). Automated checks pass.
PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsHighworst open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When ParseInt receives an integer token that is exactly one beyond the int64 range (9223372036854775808 for max+1, -9223372036854775809 for min-1), the parser shall return OverflowIntegerError.

FRETish formula
the parser shall always satisfy !raw_int_token_is_at_int64_max_plus_one | returns_overflow_at_int64_max_plus_one
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

The boundary between valid and overflow is where off-by-one errors hide. The max+1 and min-1 cases must be specified explicitly.

parseintboundaryoverflow

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
Leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 18:00 UTC · Claude · AI agent
Modified
Apr 14, 2026, 18:00 UTC · Claude · AI agent

Change history

Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.

Open known issues

Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.

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).

FRETish formula

the parser shall always satisfy !raw_int_token_is_at_int64_max_plus_one | returns_overflow_at_int64_max_plus_one

Variables

NameTypeDirectionDescription
raw_int_token_is_at_int64_max_plus_oneTrue when ParseInt receives an integer token exactly one beyond the int64 range (9223372036854775808 or -9223372036854775809).
returns_overflow_at_int64_max_plus_oneTrue when ParseInt returns OverflowIntegerError for an integer token exactly one beyond the int64 range.

Witnesses· 3 scenarios total

  • TestMCDC_SYS_REQ_059_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_059_Row2_InvariantViolation
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_059_Row3_OverflowError
    exercises 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.

Covereda test exercises this rowExempteda reviewed mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test
#raw_int_token_is_at_int64_max_plus_onereturns_overflow_at_int64_max_plus_oneResultProvesCovering test
1FFTraw_int_token_is_at_int64_max_plus_one
2TFFraw_int_token_is_at_int64_max_plus_one
3TTTreturns_overflow_at_int64_max_plus_one

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).

If you change this

Requirements
0
Files
1
Tests
2
At-risk contracts
0

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

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.

Sign in to discuss this with the proof team.Sign in