Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen 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
- human:leonidbugaev
- Reviewed
- Apr 21, 2026, 00:00 UTC
History
- Created
- Apr 21, 2026, 00:00 UTC · agent:claude
- Modified
- Jul 26, 2026, 13:17 UTC · human:cli
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 !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_TriggerFalsemcdc_spec_witnesses_test.go:3490exercises 1 condition scenario
- TestMCDC_SYS_REQ_108_Row2_InvariantViolationmcdc_spec_witnesses_test.go:3498exercises 1 condition scenario
- TestParseStringEncodingSafetyRoundtripobligation_property_test.go:507exercises 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)
- 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.