Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-077SystemReview

When GetInt addresses a value that is not a JSON number (e.g., a string, boolean, object, array, or null), the parser shall return a type-mismatch error.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

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

Description

When GetInt addresses a value that is not a JSON number (e.g., a string, boolean, object, array, or null), the parser shall return a type-mismatch error.

FRETish formula
the parser shall always satisfy !getint_addressed_value_is_not_number | returns_getint_type_mismatch_error

Rationale & tags

Why this requirement exists, and how it is categorised.

GetInt has explicit type-checking logic that rejects non-number values. This is behaviorally distinct from successful integer parsing and from malformed-input errors.

getinttype-mismatch

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
Jul 26, 2026, 14:54 UTC · human:cli

Obligations

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

1 obligation · 1 discharged

Browse the catalogue
Discharged
Worst case if violatedMedium

GetInt on a string value like "42" silently returns 42 by accepting the wrapped token, masking the type error and corrupting the caller's numeric schema.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test

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_addressed_value_is_not_number | returns_getint_type_mismatch_error

Variables

NameTypeDirectionDescription
getint_addressed_value_is_not_number—True when GetInt addresses a value that is not a JSON number.
returns_getint_type_mismatch_error—True when GetInt returns a type-mismatch error for a non-number addressed value.

Witnesses· 3 scenarios total

  • TestGetIntTypeMismatch
    deep_spec_test.go:744
  • TestMCDC_SYS_REQ_077_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2531exercises 1 condition scenario
  • TestMCDC_SYS_REQ_077_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2539exercises 1 condition scenario
  • TestMCDC_SYS_REQ_077_Row3_TypeMismatchError
    mcdc_spec_witnesses_test.go:2547exercises 1 condition scenario
  • TestObligation_SYS_REQ_077
    obligation_evidence_test.go:568

Its place

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

Open in graph

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
3
At-risk contracts
0

Files to re-check (1)

  • parser.goparser.go

Tests to re-run (3)

  • deep_spec_test.godeep_spec_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_evidence_test.goobligation_evidence_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.

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