Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen Delete is called with a provided path and the addressed target exists in usable input, the parser shall return the JSON document with that target removed.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Delete is called with a provided path and the addressed target exists in usable input, the parser shall return the JSON document with that target removed.
the parser shall always satisfy !delete_path_is_provided | !delete_target_exists | delete_returns_document_without_target
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Successful deletion of an existing target is a distinct API behavior from no-path handling, missing-target preservation, and unusable-input robustness.
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 23, 2026, 00:00 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · agent:codex
- Modified
- Apr 14, 2026, 15:45 UTC · agent:codex
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 !delete_path_is_provided | !delete_target_exists | delete_returns_document_without_target
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| delete_path_is_provided | — | True when Delete is called with at least one path segment. | |
| delete_target_exists | — | True when the addressed Delete target exists and can be isolated in the input JSON. | |
| delete_returns_document_without_target | — | True when Delete returns the JSON document with the addressed value removed. |
Witnesses· 4 scenarios total
- TestMCDC_SYS_REQ_033_Row1_TriggerFalsemcdc_spec_witnesses_test.go:1159exercises 1 condition scenario
- TestMCDC_SYS_REQ_033_Row2_MissingTargetmcdc_spec_witnesses_test.go:1170exercises 1 condition scenario
- TestMCDC_SYS_REQ_033_Row3_InvariantViolationmcdc_spec_witnesses_test.go:1180exercises 1 condition scenario
- TestDeleteparser_test.go:1350exercises 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.
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
Files to re-check (1)
- parser.goparser.go
Tests to re-run (2)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- parser_test.goparser_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.