Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ParseBoolean receives an invalid boolean token, the parser shall return the documented malformed-value error.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseBoolean receives an invalid boolean token, the parser shall return the documented malformed-value error.
the parser shall always satisfy raw_boolean_literal_is_valid | returns_parseboolean_error
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Invalid-token failure is externally visible and should be specified independently from valid ParseBoolean success behavior.
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 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.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-92
The FRETish invariant
raw_boolean_literal_is_valid | returns_parseboolean_errorrequires ParseBoolean to reject any token that is not exactlytrue/false, and the default arm at parser.go:2141 correctly returns MalformedValueError. However the two match arms usebytes.HasPrefix(b, trueLiteral)/bytes.HasPrefix(b, falseLiteral)(parser.go:2137,2139) instead ofbytes.Equal, so trailing-garbage tokens liketrueish/falsehoodare invalid literals yet return (value, nil) with no error, violating the invariant. This is the intentional prefix-match defect tracked by KI-11 (CWE-20), whose reproducer TestDemoKI11 and the MCDC row test both exercise it. Sound wrapper, real tracked defect — approvable.Cited code (3)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
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 catalogueBehavior when inputs are syntactically or structurally invalid.
ParseBoolean on adversarial input like truN over-reads past the literal check and returns true, misclassifying malformed input as a valid boolean and corrupting downstream control flow.
- 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 raw_boolean_literal_is_valid | returns_parseboolean_error
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_boolean_literal_is_valid | — | True when ParseBoolean receives a valid boolean literal token. | |
| returns_parseboolean_error | — | True when ParseBoolean returns the documented malformed-value error for an invalid boolean token. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_036_Row1_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_036_Row2_ValidLiteralexercises 1 condition scenario
- TestParseBooleanexercises 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| # | raw_boolean_literal_is_valid | returns_parseboolean_error | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | F | raw_boolean_literal_is_valid | |
| 2 | F | T | T | returns_parseboolean_error | |
| 3 | T | F | T | raw_boolean_literal_is_valid |
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.
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
Files to re-check (1)
- parser.goparser.go
Tests to re-run (3)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_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.