Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen ParseString encounters a UTF-16 high surrogate escape (e.g., '\uD800') that is not followed by a valid low surrogate escape, the parser shall substitute U+FFFD (replacement character) for the lone surrogate and continue parsing, matching encoding/json behavior, rather than producing corrupted output or synthesizing a bogus code point.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseString encounters a UTF-16 high surrogate escape (e.g., '\uD800') that is not followed by a valid low surrogate escape, the parser shall substitute U+FFFD (replacement character) for the lone surrogate and continue parsing, matching encoding/json behavior, rather than producing corrupted output or synthesizing a bogus code point.
the parser shall always satisfy !raw_string_has_missing_low_surrogate | substitutes_replacement_for_missing_low_surrogate
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Surrogate pair handling in decodeUnicodeEscape requires both high and low surrogates. A missing or invalid low surrogate exercises a distinct failure 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
- human:buger · lead_engineer
- Reviewed
- Jul 27, 2026, 12:22 UTC
History
- Created
- Apr 14, 2026, 18:00 UTC · agent:claude
- Modified
- Jul 27, 2026, 12:22 UTC · human:buger
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
No obligations recorded for this requirement
Proof obligations are recorded once evidence is generated. None have been captured here yet — this is expected, not a gap in the requirement itself. A required class of evidence the requirement must witness — the bridge between the requirement existing and it being proven.
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_string_has_missing_low_surrogate | substitutes_replacement_for_missing_low_surrogate
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_string_has_missing_low_surrogate | — | True when ParseString encounters a UTF-16 high surrogate escape not followed by a valid low surrogate escape. | |
| substitutes_replacement_for_missing_low_surrogate | — | True when ParseString substitutes U+FFFD for a lone high surrogate, matching encoding/json behavior. |
Witnesses· 2 scenarios total
- TestMissingSurrogateLowdeep_spec_test.go:617
- TestMCDC_SYS_REQ_061_Row1_TriggerFalsemcdc_spec_witnesses_test.go:2802exercises 1 condition scenario
- TestMCDC_SYS_REQ_061_Row3_MissingLowSurrogateErrormcdc_spec_witnesses_test.go:2815exercises 1 condition scenario
Its place
This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
No implementation linked
No source files are traced to this requirement yet.
Impact
Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.
Impact
Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.
If you change this
Tests to re-run (2)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_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.