Proof Portal
jsonparser
ProbeLabsviewing a historical runWhen ParseString is called on a byte slice containing standard JSON escape sequences (backslash-n, backslash-t, double backslash, backslash-solidus, backslash-doublequote, backslash-uXXXX), the decoded Go string shall contain the correct Unicode codepoints such that re-encoding to JSON would produce semantically equivalent escape sequences.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseString is called on a byte slice containing standard JSON escape sequences (backslash-n, backslash-t, double backslash, backslash-solidus, backslash-doublequote, backslash-uXXXX), the decoded Go string shall contain the correct Unicode codepoints such that re-encoding to JSON would produce semantically equivalent escape sequences.
the parser shall always satisfy !parsestring_input_has_standard_escapes | parsestring_roundtrip_preserves_semantics
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Encoding safety for ParseString ensures that the decode path does not lose information. The decoded string must represent the same semantic content as the original JSON encoding.
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-88
ParseString (parser.go:2148) unescapes via unescapeToUTF8Config, which correctly decodes \n \t \\ \" \b \f \r and \uXXXX (those subtests pass in TestParseStringEncodingSafetyRoundtrip, obligation_property_test.go:507). But the requirement explicitly enumerates the escaped solidus (\/) as a standard escape, and unescapeToUTF8Config has dropped '/' from its accepted case list (escape.go:203), so ParseString([]byte(
a\/b)) returns MalformedValueError and the 'solidus' subtest fails — I confirmed this by running the test (obligation_property_test.go:529). This is a real RFC-8259 violation tracked by KI-14 and thus still approvable, but note KI-14 lists only SYS-REQ-014/038 in affected_requirements and should also cite SYS-REQ-108.Cited code (4)
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 aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. 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 !parsestring_input_has_standard_escapes | parsestring_roundtrip_preserves_semantics
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| parsestring_input_has_standard_escapes | — | True when ParseString input contains standard JSON escape sequences. | |
| parsestring_roundtrip_preserves_semantics | — | True when ParseString decoded string preserves semantic equivalence with original JSON encoding. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_108_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_108_Row2_InvariantViolationexercises 1 condition scenario
- TestParseStringEncodingSafetyRoundtripexercises 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| # | parsestring_input_has_standard_escapes | parsestring_roundtrip_preserves_semantics | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | parsestring_input_has_standard_escapes | |
| 2 | T | F | F | parsestring_input_has_standard_escapes | |
| 3 | T | T | T | parsestring_roundtrip_preserves_semantics |
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
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.