Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen GetString is called on a JSON string containing escaped Unicode sequences (e.g., \u00e9, \uD83D\uDE00), the parser shall decode them to the correct Go string runes, preserving round-trip semantic equivalence with the original Unicode codepoints.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetString is called on a JSON string containing escaped Unicode sequences (e.g., \u00e9, \uD83D\uDE00), the parser shall decode them to the correct Go string runes, preserving round-trip semantic equivalence with the original Unicode codepoints.
the parser shall always satisfy !getstring_input_has_escaped_unicode | getstring_decodes_and_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 ensures that escaped Unicode in JSON is faithfully decoded to Go strings. This is critical for internationalized payloads.
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-72
The escaped-Unicode decode core is correct: decodeUnicodeEscape handles BMP escapes and combines valid high+low surrogate pairs (\uD83D\uDE00 -> U+1F600), so the surrogate-pair and \u00e9 cases round-trip. However the requirement's own verification test TestGetStringEncodingSafety FAILS on the solidus case: with KI-14 the '/' entry was dropped from the basic-escape switch in unescapeToUTF8Config, so GetString on {"s":"a\/b"} returns MalformedStringEscapeError instead of "a/b" (I ran the test and reproduced the failure at obligation_property_test.go:498). Additionally KI-9 (h2I upper bound widened to accept 'G') lets \uGxxx decode to a bogus codepoint, violating the semantic-preservation clause. Both are real, tracked defects — verification honestly fails, but they are known-issue-linked and still approvable.
Cited code (5)
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 need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. 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 !getstring_input_has_escaped_unicode | getstring_decodes_and_preserves_semantics
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getstring_input_has_escaped_unicode | — | True when GetString addresses a JSON string containing escaped Unicode sequences. | |
| getstring_decodes_and_preserves_semantics | — | True when GetString decodes escaped Unicode to correct Go string runes preserving semantic equivalence. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_092_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_092_Row2_InvariantViolationexercises 1 condition scenario
- TestGetStringEncodingSafetyexercises 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| # | getstring_decodes_and_preserves_semantics | getstring_input_has_escaped_unicode | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | getstring_input_has_escaped_unicode | |
| 2 | F | T | F | getstring_decodes_and_preserves_semantics | |
| 3 | T | T | T | getstring_decodes_and_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 implementation linked
No source files are traced to this requirement yet.
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.