Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
SYS-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.

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

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
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

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

Obligations

What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.

No obligations recorded for this requirement

Proof obligations are recorded once evidence is generated. None have been captured here yet — this is expected, not a gap in the requirement itself. A required class of evidence the requirement must witness — the bridge between the requirement existing and it being proven.

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

  • TestParseIntOverflowBoundary
    deep_spec_test.go:529
  • TestMCDC_SYS_REQ_059_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2089exercises 1 condition scenario
  • TestMCDC_SYS_REQ_059_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2101exercises 1 condition scenario
  • TestMCDC_SYS_REQ_059_Row3_OverflowError
    mcdc_spec_witnesses_test.go:2109exercises 1 condition scenario

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

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 — if you change this requirement, what else may need re-checking, and what it in turn depends on.

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