Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen GetInt is called on empty input, the parser shall return the same not-found or error behavior as Get on empty input.
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 empty input, the parser shall return the same not-found or error behavior as Get on empty input.
the parser shall always satisfy !getint_input_is_empty | returns_getint_error_for_empty_input
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Empty input to GetInt delegates to Get. The empty-input behavior must be explicitly covered.
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
- 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.
2 obligations · 2 discharged
Browse the catalogueBehavior when inputs are absent, nil, zero-length, or blank.
GetInt on an empty []byte returns 0 (silent success) instead of KeyPathNotFoundError, masking missing data as a valid zero and corrupting accumulator invariants.
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
GetInt on nil data panics in nextToken at data[0] instead of returning the not-found result, crashing the caller on a nil trust-boundary input.
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered 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).
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_is_empty | returns_getint_error_for_empty_input
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getint_input_is_empty | — | True when GetInt is called on empty input. | |
| returns_getint_error_for_empty_input | — | True when GetInt returns not-found or error for empty input. |
Witnesses· 3 scenarios total
- TestGetIntEmptyInputdeep_spec_test.go:768
- TestMCDC_SYS_REQ_078_Row1_TriggerFalsemcdc_spec_witnesses_test.go:2559exercises 1 condition scenario
- TestMCDC_SYS_REQ_078_Row2_InvariantViolationmcdc_spec_witnesses_test.go:2567exercises 1 condition scenario
- TestMCDC_SYS_REQ_078_Row3_EmptyInputErrormcdc_spec_witnesses_test.go:2575exercises 1 condition scenario
- TestObligation_SYS_REQ_078obligation_evidence_test.go:575
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.
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
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.