Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen the current path segment is an object key and it is evaluated at the current JSON structural scope, Get shall resolve that segment only against object members in that current scope.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the current path segment is an object key and it is evaluated at the current JSON structural scope, Get shall resolve that segment only against object members in that current scope.
the parser shall always satisfy !path_segment_is_object_key | !segment_is_evaluated_at_current_scope | returns_value_from_current_scope_object_key
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Correct lookup depends on respecting JSON structural scope rather than matching a similarly named key in a sibling or deeper subtree.
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
- Jul 26, 2026, 12:44 UTC
History
- Created
- Apr 14, 2026, 00:00 UTC · Created via CLI
- Modified
- Jul 26, 2026, 12:44 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.
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. Nothing here means unknown — not that the requirement has no obligations.
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 !path_segment_is_object_key | !segment_is_evaluated_at_current_scope | returns_value_from_current_scope_object_key
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| path_segment_is_object_key | — | True when the current lookup path segment is interpreted as an object-member key rather than as an array index. | |
| segment_is_evaluated_at_current_scope | — | True when the current lookup segment is being matched against the current JSON structural scope rather than against a sibling or deeper subtree. | |
| returns_value_from_current_scope_object_key | — | True when Get resolves the requested object-member path segment only against the current structural scope and returns that value. |
Witnesses· 4 scenarios total
- TestMCDC_SYS_REQ_020_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_020_Row2_NotEvaluatedexercises 1 condition scenario
- TestMCDC_SYS_REQ_020_Row3_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_020_Row4_ObjectKeyMatchedexercises 1 condition scenario
MC/DC truth table· 4 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| # | path_segment_is_object_key | returns_value_from_current_scope_object_key | segment_is_evaluated_at_current_scope | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | T | T | path_segment_is_object_key | |
| 2 | T | F | F | T | segment_is_evaluated_at_current_scope | |
| 3 | T | F | T | F | path_segment_is_object_key | |
| 4 | T | T | T | T | returns_value_from_current_scope_object_key |
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
- 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.