Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen Get is called with a nil byte slice as input, the parser shall return a not-found or error result without panicking.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Get is called with a nil byte slice as input, the parser shall return a not-found or error result without panicking.
the parser shall always satisfy !get_input_is_nil | get_returns_safe_result_for_nil
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Nil input is distinct from empty input and must not cause a nil-pointer dereference panic. Callers may pass nil when an upstream read fails.
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
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 21, 2026, 00:00 UTC · Claude · 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.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-68
For nil input Get must return a safe not-found/error result without panicking. With keys, searchKeysConfig(nil,...) returns -1 so internalGetConfig returns (nil, NotExist, -1, KeyPathNotFoundError); with no keys, nextTokenConfig(nil) returns -1 and it returns MalformedJsonError — neither path dereferences the nil slice. TestMCDC_SYS_REQ_088_Row2 asserts exactly value==nil, dataType==NotExist, offset==-1, err!=nil, and TestGetNilSafety wraps the call in a recover() guard that never fires. Sound.
Cited code (5)
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 need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. 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).
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 !get_input_is_nil | get_returns_safe_result_for_nil
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| get_input_is_nil | — | True when Get is called with a nil byte slice as input. | |
| get_returns_safe_result_for_nil | — | True when Get returns a not-found or error result without panicking for nil input. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_088_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_088_Row2_InvariantViolationexercises 1 condition scenario
- TestGetNilSafetyexercises 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.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | get_input_is_nil | get_returns_safe_result_for_nil | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | get_input_is_nil | |
| 2 | T | F | F | get_input_is_nil | |
| 3 | T | T | T | get_returns_safe_result_for_nil |
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 implementation linked
No source files are traced to this requirement yet.
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Tests to re-run (2)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_property_test.goobligation_property_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.