Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen Set is called with a multi-level path where intermediate levels exist but the leaf does not, the parser shall correctly create the missing nested structure and insert the value at the correct location.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Set is called with a multi-level path where intermediate levels exist but the leaf does not, the parser shall correctly create the missing nested structure and insert the value at the correct location.
the parser shall always satisfy !set_target_is_nested_in_existing_structure | set_performs_nested_mutation_correctly
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Nested mutation through createInsertComponent exercises depth-tracking logic that determines whether to append inside an existing structure or overwrite. This is a distinct behavior from flat key insertion.
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 14, 2026, 18: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-49
The requirement is that Set with a multi-level path whose intermediate levels exist but leaf does not correctly creates the missing nested structure and inserts at the right location. setConfig (parser.go:1402) handles the KeyPathNotFoundError case by walking existing subpaths via internalGetConfig to find the deepest existing prefix, then builds and splices the new component at that offset. I ran TestSetNestedMutation, TestObligation_SYS_REQ_069, and TestMCDC_SYS_REQ_069_Row2/Row3:
Set({"a":{"b":1}}, "a","c")creates c inside a and a round-trip Get returns the inserted value, and setting an existing leafa/boverwrites it correctly. All pass with correct output. No known issue is attached to this requirement.Cited code (4)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
1 obligation · 1 discharged
Browse the catalogueSet on path [a][b] where a exists but b does not overwrites the sibling [a][c] value or builds malformed JSON like {"a":{"b":1}} missing a comma, silently corrupting the document.
- nominalrequiredpresentCovered by 1 test
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 !set_target_is_nested_in_existing_structure | set_performs_nested_mutation_correctly
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| set_target_is_nested_in_existing_structure | — | True when Set is called with a multi-level path where intermediate levels exist but the leaf does not. | |
| set_performs_nested_mutation_correctly | — | True when Set correctly creates missing nested structure and inserts the value at the correct location. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_069_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_069_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_069_Row3_NestedMutationexercises 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| # | set_performs_nested_mutation_correctly | set_target_is_nested_in_existing_structure | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | set_target_is_nested_in_existing_structure | |
| 2 | F | T | F | set_performs_nested_mutation_correctly | |
| 3 | T | T | T | set_performs_nested_mutation_correctly |
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.
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
Files to re-check (1)
- parser.goparser.go
Tests to re-run (3)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_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.