Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen the addressed token cannot be classified as string, object, array, number, boolean, or null, Get shall return a value-type error instead of a successful classification.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the addressed token cannot be classified as string, object, array, number, boolean, or null, Get shall return a value-type error instead of a successful classification.
the parser shall always satisfy !addressed_token_shape_is_invalid | returns_value_type_error
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Unknown token classification is an externally visible error path in Get and should not be hidden inside a generic parse-failure bucket.
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:buger · lead_engineer
- Reviewed
- Jul 26, 2026, 15:21 UTC
History
- Created
- Apr 14, 2026, 00:00 UTC · human:cli
- Modified
- Jul 26, 2026, 15:21 UTC · human:buger
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 catalogueGet on a leading-byte token that matches no classifier (e.g. ; at value position) returns a Number or String classification anyway, mis-routing the caller into the wrong typed accessor and producing wrong downstream values.
- 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 !addressed_token_shape_is_invalid | returns_value_type_error
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| addressed_token_shape_is_invalid | — | True when the addressed token cannot be classified as string, object, array, number, boolean, or null. | |
| returns_value_type_error | — | True when Get returns a value-type classification error for an invalid addressed token shape. |
Witnesses· 3 scenarios total
- TestGetUnknownValueTypedeep_spec_test.go:1110
- TestMCDC_SYS_REQ_027_Row1_TriggerFalsemcdc_spec_witnesses_test.go:922exercises 1 condition scenario
- TestMCDC_SYS_REQ_027_Row2_InvariantViolationmcdc_spec_witnesses_test.go:934exercises 1 condition scenario
- TestMCDC_SYS_REQ_027_Row3_ValueTypeErrormcdc_spec_witnesses_test.go:943exercises 1 condition scenario
- TestObligation_SYS_REQ_027obligation_evidence_test.go:278
- TestGetRequirementSlicesparser_test.go:1390
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 (4)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_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.