Proof Portal

Projects

jsonparser

ProbeLabsviewing a historical run
Viewing historical run d79405eAug 20, 2026, 03:41 PMproof-demoaudited with uncommitted changes — showing the committed treeBack to current
All requirements
RequirementSYS-REQ-040SystemApproved

When ParseInt receives a non-integer or otherwise malformed token that is not an overflow case, the parser shall return the documented malformed-value error.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass.
PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone 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 a non-integer or otherwise malformed token that is not an overflow case, the parser shall return the documented malformed-value error.

FRETish formula
the parser shall always satisfy raw_int_token_is_well_formed | raw_int_token_overflows_int64 | returns_parseint_malformed_error
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

Malformed-token rejection is an externally visible ParseInt outcome and should be specified independently from valid integer parsing and overflow detection.

decompositionparseintedge-case

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
Buger · lead_engineer
Reviewed
Aug 20, 2026, 13:11 UTC
Spec-conformance reviewed (agent:claude:spec-conformance); approved on owner authorization.

History

Created
Apr 14, 2026, 15:45 UTC · Codex · 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.

  1. Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-95

    The invariant raw_int_token_is_well_formed | raw_int_token_overflows_int64 | returns_parseint_malformed_error requires a non-overflow malformed token to yield MalformedValueError, and ParseInt (parser.go:2168) returns MalformedValueError exactly when parseInt reports !ok && !overflow. parseInt rejects any non-digit byte via if d > 9 { return 0, false, false } (bytes.go:29-31), and the former sign-only false-success (ParseInt("-")=0,nil) is now closed by the guard if i == l { return 0, false, false } at bytes.go:20-22, so - and notanint both error. The KI-7 fast-path overflow defect only affects the overflow disjunct (SYS-REQ-039), which this formula explicitly permits, so it does not break this requirement; KI-2 is marked fixed with regression test TestParseIntSignOnly_KI2. No open KI is attached here.

    Cited code (3)

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_well_formed | raw_int_token_overflows_int64 | returns_parseint_malformed_error

Variables

NameTypeDirectionDescription
raw_int_token_is_well_formedTrue when ParseInt receives a syntactically well-formed integer token that does not overflow int64.
raw_int_token_overflows_int64True when ParseInt receives an integer token whose magnitude exceeds the supported int64 range.
returns_parseint_malformed_errorTrue when ParseInt returns the documented malformed-value error for a non-integer or otherwise malformed token.

Witnesses· 4 scenarios total

  • TestMCDC_SYS_REQ_040_Row1_InvariantViolation
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_040_Row2_MalformedOrOverflow
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_040_Row3_WellFormed
    exercises 1 condition scenario
  • TestParseInt
    exercises 1 condition scenario

MC/DC truth table· 4 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_well_formedraw_int_token_overflows_int64returns_parseint_malformed_errorResultProvesCovering test
1FFFFraw_int_token_is_well_formed
2FFTTreturns_parseint_malformed_error
3FTFTraw_int_token_overflows_int64
4TFFTraw_int_token_is_well_formed

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

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)

  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • parser_test.goparser_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