Proof Portal
jsonparser
ProbeLabs36 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
- 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 !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_TriggerFalsemcdc_spec_witnesses_test.go:3347exercises 1 condition scenario
- TestMCDC_SYS_REQ_102_Row2_InvariantViolationmcdc_spec_witnesses_test.go:3355exercises 1 condition scenario
- TestMutationUnicodeKeysobligation_property_test.go:758exercises 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.