Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen Delete is called with a provided path, the addressed target is absent, and the input is otherwise usable for deletion, the parser shall return the original byte payload unchanged.
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, the addressed target is absent, and the input is otherwise usable for deletion, the parser shall return the original byte payload unchanged.
the parser shall always satisfy !delete_path_is_provided | delete_target_exists | delete_input_is_unusable_for_requested_path | delete_preserves_input_when_target_missing
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Missing-target preservation is a distinct API outcome from successful deletion and from malformed-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
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · Codex · 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-20
The formula requires that Delete with a provided path, an absent target, and otherwise-usable input returns the original payload unchanged. In deleteFoundConfig the findKeyStartConfig KeyPathNotFoundError branch (parser.go:1277) returns
data, false— the untouched input slice — so a missing key yields the original bytes. TestMCDC_SYS_REQ_034_Row2/Row3 and TestObligation_SYS_REQ_034 confirmDelete({"a":1},"missing")equals the input, TestPropertyDeleteIdempotent proves idempotence, and TestOracleDeleteCorrectness asserts the input is unchanged across 10000 random deletes. KI-1 (empty-key panic) is status:fixed and the len(keys[lk-1])>0 guard at parser.go:1260 plus TestDeleteEmptyKeyPathComponent lock in panic-free degradation.Cited code (4)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
2 obligations · 2 discharged
Browse the catalogueBehavior for unusual but valid input combinations.
Delete on an object whose only key is the absent target rewrites the payload (e.g. drops a sibling key in cleanup), silently corrupting the document.
- nominalrequiredpresentCovered by 1 test
Delete on a missing nested path descends into the intermediate structure and corrupts a sibling by deleting the wrong key, producing a wrong 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 !delete_path_is_provided | delete_target_exists | delete_input_is_unusable_for_requested_path | delete_preserves_input_when_target_missing
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_input_is_unusable_for_requested_path | — | True when Delete cannot safely resolve the requested path because the input is malformed, truncated, or otherwise unusable for that deletion request. | |
| delete_preserves_input_when_target_missing | — | True when Delete leaves the input unchanged because the addressed target is missing in otherwise usable input. |
Witnesses· 5 scenarios total
- TestMCDC_SYS_REQ_034_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_034_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_034_Row3_TargetExistsUsableexercises 1 condition scenario
- TestMCDC_SYS_REQ_034_Row4_UnusableInputexercises 1 condition scenario
- TestDeleteexercises 1 condition scenario
MC/DC truth table· 5 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| # | delete_input_is_unusable_for_requested_path | delete_path_is_provided | delete_preserves_input_when_target_missing | delete_target_exists | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | F | F | T | delete_path_is_provided | |
| 2 | F | T | F | F | F | delete_input_is_unusable_for_requested_path | |
| 3 | F | T | F | T | T | delete_target_exists | |
| 4 | F | T | T | F | T | delete_preserves_input_when_target_missing | |
| 5 | T | T | F | F | T | delete_input_is_unusable_for_requested_path |
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 (6)
- empty_key_path_test.goempty_key_path_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_test.go
- property_test.goproperty_test.go
- reference_oracle_test.goreference_oracle_test.go
What this rests on
Parent requirements (1)
Changes
Semantic changes that move or scope this requirement — the intended work touching it. Each links to the full change.
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.