Proof Portal
jsonparser
ProbeLabsviewing a historical runWhen GetBoolean addresses a value that appears to be a partial boolean literal (e.g., the addressed token is "tru" or "fals" due to truncation), the parser shall return an error from the type-classification or ParseBoolean step.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetBoolean addresses a value that appears to be a partial boolean literal (e.g., the addressed token is "tru" or "fals" due to truncation), the parser shall return an error from the type-classification or ParseBoolean step.
the parser shall always satisfy !getboolean_addressed_value_is_partial_literal | returns_getboolean_error_for_partial
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 can occur when input is truncated at a token boundary. The getType function uses tokenEnd to find the token end, and if the token is partial, it may be classified as Unknown rather than Boolean.
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-59
The guarantee that a partial boolean literal ("tru"/"fals") yields an error holds because classification happens in getTypeConfig (parser.go:1624-1626), whose 't'/'f' case requires bytes.Equal(value, trueLiteral)||bytes.Equal(value, falseLiteral) — a truncated token like
trufails both exact comparisons and returns UnknownValueTypeError, which GetBoolean (parser.go:2113) propagates via its e!=nil guard before ParseBoolean is ever reached. Notably the KI-11 prefix-match defect in ParseBoolean cannot affect this requirement: ParseBoolean runs only after getType has already confirmed the token is exactly the literal, so partial literals never reach it. MCDC rows and TestGetBooleanPartialLiteral confirm errors on non-boolean/partial values and a clean true on{"a":true}.Cited code (4)
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 catalogueGetBoolean on an addressed token like tru (3 bytes) over-reads 4 bytes past the literal check in ParseBoolean, panicking with index-out-of-range or returning a wrong bool to the caller.
- 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 !getboolean_addressed_value_is_partial_literal | returns_getboolean_error_for_partial
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getboolean_addressed_value_is_partial_literal | — | True when GetBoolean addresses a value that is a partial boolean literal due to truncation. | |
| returns_getboolean_error_for_partial | — | True when GetBoolean returns an error from type classification or ParseBoolean for a partial boolean literal. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_079_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_079_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_079_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| # | getboolean_addressed_value_is_partial_literal | returns_getboolean_error_for_partial | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | getboolean_addressed_value_is_partial_literal | |
| 2 | T | F | F | getboolean_addressed_value_is_partial_literal | |
| 3 | T | T | T | returns_getboolean_error_for_partial |
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 findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
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.