Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
SYS-REQ-069SystemReview

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.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

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.

FRETish formula
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.

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.

setnestedmutation

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 18:00 UTC · agent:claude
Modified
Jul 26, 2026, 14:54 UTC · human:cli

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 catalogue
Discharged
Worst case if violatedMedium

Set 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.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered 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).

FRETish formula

the parser shall always satisfy !set_target_is_nested_in_existing_structure | set_performs_nested_mutation_correctly

Variables

NameTypeDirectionDescription
set_target_is_nested_in_existing_structureTrue when Set is called with a multi-level path where intermediate levels exist but the leaf does not.
set_performs_nested_mutation_correctlyTrue when Set correctly creates missing nested structure and inserts the value at the correct location.

Witnesses· 3 scenarios total

  • TestSetNestedMutation
    deep_spec_test.go:361
  • TestMCDC_SYS_REQ_069_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2286exercises 1 condition scenario
  • TestMCDC_SYS_REQ_069_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2294exercises 1 condition scenario
  • TestMCDC_SYS_REQ_069_Row3_NestedMutation
    mcdc_spec_witnesses_test.go:2311exercises 1 condition scenario
  • TestObligation_SYS_REQ_069
    obligation_evidence_test.go:487

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.

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

Requirements
0
Files
1
Tests
3
At-risk contracts
0

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

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.

Sign in to discuss this with the proof team.Sign in