Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen Set or Delete is called with key paths containing Unicode characters, the parser shall correctly resolve the path and perform the mutation or return a well-defined error without panicking.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Set or Delete is called with key paths containing Unicode characters, the parser shall correctly resolve the path and perform the mutation or return a well-defined error without panicking.
the parser shall always satisfy !mutation_input_has_unicode_keys | mutation_handles_unicode_keys_safely
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
JSON object keys can be arbitrary Unicode strings. Mutation helpers must handle non-ASCII key paths without corrupting the document.
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-82
The formula requires Unicode key paths to either resolve and mutate correctly or fail cleanly without panicking. Set (parser.go:1397) and Delete (parser.go:1238) delegate to setConfig/deleteFoundConfig, which match keys byte-wise through internalGet with no decode step that could panic on multi-byte input. TestMutationUnicodeKeys (obligation_property_test.go:758) exercises Set/Delete on a document carrying a raw UTF-8 key and confirms the mutation applies and the document stays parseable, and the MCDC Row2 witness confirms a non-nil result for a Unicode-key Set. The Set/Delete demo defects KI-3/KI-4/KI-16 are confined to array-index and root-delete paths, none of which this requirement's Unicode-string-key cases touch; all witness tests pass.
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 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 !mutation_input_has_unicode_keys | mutation_handles_unicode_keys_safely
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| mutation_input_has_unicode_keys | — | True when Set or Delete is called with key paths containing Unicode characters. | |
| mutation_handles_unicode_keys_safely | — | True when Set or Delete correctly resolves Unicode key paths or returns well-defined error. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_102_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_102_Row2_InvariantViolationexercises 1 condition scenario
- TestMutationUnicodeKeysexercises 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| # | mutation_handles_unicode_keys_safely | mutation_input_has_unicode_keys | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | mutation_input_has_unicode_keys | |
| 2 | F | T | F | mutation_handles_unicode_keys_safely | |
| 3 | T | T | T | mutation_handles_unicode_keys_safely |
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.