Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-070SystemReview

When Set is called without any key path, the parser shall return KeyPathNotFoundError because Set requires at least one path segment to identify the mutation target.

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 without any key path, the parser shall return KeyPathNotFoundError because Set requires at least one path segment to identify the mutation target.

FRETish formula
the parser shall always satisfy !set_called_without_path | set_returns_error_without_path

Rationale & tags

Why this requirement exists, and how it is categorised.

Set without a path is a distinct edge case from Delete without a path (which returns empty). Set returns an error, Delete returns empty document. Both no-path behaviors must be explicitly specified.

setedge-caseno-path

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 violatedLow

Set with no path returns a byte slice or panics in findKeyStart at data[0] instead of returning KeyPathNotFoundError, mutating the wrong memory or crashing on empty input.

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_called_without_path | set_returns_error_without_path

Variables

NameTypeDirectionDescription
set_called_without_path—True when Set is called without any key path segments.
set_returns_error_without_path—True when Set returns KeyPathNotFoundError because no path segment was provided.

Witnesses· 3 scenarios total

  • TestSetNoPath
    deep_spec_test.go:379
  • TestMCDC_SYS_REQ_070_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2331exercises 1 condition scenario
  • TestMCDC_SYS_REQ_070_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2339exercises 1 condition scenario
  • TestMCDC_SYS_REQ_070_Row3_NoPathError
    mcdc_spec_witnesses_test.go:2347exercises 1 condition scenario
  • TestObligation_SYS_REQ_070
    obligation_evidence_test.go:502

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Open in graph

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

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.

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