Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ParseBoolean receives a partial boolean literal (e.g., "tru", "fals", "t", "f"), the parser shall return MalformedValueError because the token does not match either "true" or "false" exactly.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseBoolean receives a partial boolean literal (e.g., "tru", "fals", "t", "f"), the parser shall return MalformedValueError because the token does not match either "true" or "false" exactly.
the parser shall always satisfy !raw_boolean_literal_is_partial | returns_error_for_partial_boolean_literal
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Partial boolean literals are a distinct malformed-input subclass that exercises the bytes.Equal comparison boundary. Truncated network payloads commonly produce these.
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, 18: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-39
The narrow formula clause holds for genuinely partial literals: 'tru'/'fals'/'t'/'f' are shorter than the target literals so bytes.HasPrefix(b, trueLiteral)/HasPrefix(b, falseLiteral) are both false and ParseBoolean falls to the default returning MalformedValueError (parser.go:2132-2141), which TestParseBooleanPartialLiterals verifies. However the same function uses HasPrefix rather than bytes.Equal, so trailing-garbage tokens like 'trueish'/'falsehood' are wrongly accepted as booleans — an open CWE-20 defect tracked by KI-11 and explicitly linked to SYS-REQ-057. Sound intent and implemented, but the exact-match contract for this validation function is honestly not met.
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 catalogueParseBoolean on a 3-byte tru over-reads 4 bytes past EOF checking for the true/false literal, panicking with index-out-of-range on a buffer that is exactly 3 bytes long.
- 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_partial | returns_error_for_partial_boolean_literal
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_boolean_literal_is_partial | — | True when ParseBoolean receives a partial boolean literal such as "tru" or "fals". | |
| returns_error_for_partial_boolean_literal | — | True when ParseBoolean returns MalformedValueError for a partial boolean literal. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_057_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_057_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_057_Row3_PartialErrorexercises 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_partial | returns_error_for_partial_boolean_literal | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | raw_boolean_literal_is_partial | |
| 2 | T | F | F | raw_boolean_literal_is_partial | |
| 3 | T | T | T | returns_error_for_partial_boolean_literal |
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)
- 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.