Proof Portal
jsonparser
ProbeLabsviewing a historical runWhen ParseBoolean receives a valid raw boolean token, the parser shall return the corresponding Go bool value.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseBoolean receives a valid raw boolean token, the parser shall return the corresponding Go bool value.
the parser shall always satisfy !raw_boolean_literal_is_valid | returns_parseboolean_value
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
ParseBoolean success on valid tokens should be specified independently from the invalid-token error path.
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
- Leonidbugaev
- Reviewed
- Apr 23, 2026, 00:00 UTC
History
- Created
- Apr 13, 2026, 17:21 UTC · Created via CLI
- Modified
- Jul 26, 2026, 14:54 UTC · Created via CLI
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
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 catalogueOutput identical regardless of collection ordering or runtime conditions.
ParseBoolean returns different bools across calls on the same true/false token, inverting downstream branching logic.
- 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_value
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_boolean_literal_is_valid | — | True when ParseBoolean receives a valid boolean literal token. | |
| returns_parseboolean_value | — | True when ParseBoolean returns the corresponding Go bool value. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_012_Row1_TriggerFalseexercises 1 condition scenario
- TestParseBooleanexercises 2 condition scenarios
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_value | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | raw_boolean_literal_is_valid | |
| 2 | T | F | F | raw_boolean_literal_is_valid | |
| 3 | T | T | T | returns_parseboolean_value |
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 (2)
- fuzz.gofuzz.go
- parser.goparser.go
Tests to re-run (6)
- fuzz_native_test.gofuzz_native_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- mcdc_supplement_test.gomcdc_supplement_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_test.go
- reference_oracle_test.goreference_oracle_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.