Proof Portal

Projects

jsonparser

ProbeLabsviewing a historical run
Viewing historical run d79405eAug 20, 2026, 03:41 PMproof-demoaudited with uncommitted changes — showing the committed treeBack to current
All requirements
RequirementSYS-REQ-011SystemApproved

When GetUnsafeString addresses a JSON string value, the parser shall return the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass and 1/1 obligations are satisfied.
PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When GetUnsafeString addresses a JSON string value, the parser shall return the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

FRETish formula
the parser shall always satisfy !addressed_value_is_string | returns_unsafe_string_view
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

GetUnsafeString is explicitly documented as the low-allocation alternative to GetString and needs its own contract coverage.

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
Buger · lead_engineer
Reviewed
Aug 20, 2026, 13:11 UTC
Spec-conformance reviewed (agent:claude:spec-conformance); approved on owner authorization.

History

Created
Apr 13, 2026, 17:21 UTC · Created via CLI
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.

  1. Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-14

    GetUnsafeString satisfies !addressed_value_is_string | returns_unsafe_string_view: on a successful Get it returns bytesToString(&v), a zero-copy mapping of the addressed raw value bytes directly to a Go string with no Unescape/ParseString call, so JSON escapes are deliberately NOT processed — exactly the unsafe raw view the requirement demands. The property test TestPropertyTypedAccessorsRoundTrip only compares GetUnsafeString against expected values on the no-escape case (strings.ContainsAny gate), matching the no-unescaping semantics, and TestGetUnsafeString provides the example witness.

    Cited code (3)

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

Output identical regardless of collection ordering or runtime conditions.

If it were violatedMedium

GetUnsafeString returns different raw bytes for identical input across calls, corrupting downstream byte-equality or hash invariants.

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 !addressed_value_is_string | returns_unsafe_string_view

Variables

NameTypeDirectionDescription
addressed_value_is_stringTrue when the addressed successful lookup value is a JSON string token.
returns_unsafe_string_viewTrue when GetUnsafeString returns the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

Witnesses· 3 scenarios total

  • TestMCDC_SYS_REQ_011_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestGetUnsafeString
    exercises 2 condition scenarios

MC/DC truth table· 3 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.

Covereda test exercises this rowExempteda reviewed mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test
#addressed_value_is_stringreturns_unsafe_string_viewResultProvesCovering test
1FFTaddressed_value_is_string
2TFFaddressed_value_is_string
3TTTreturns_unsafe_string_view

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.

No findings affect this requirement

Nothing was flagged against this requirement in the pinned run.

Impact

Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).

If you change this

Requirements
0
Files
2
Tests
5
At-risk contracts
0

Files to re-check (2)

  • fuzz.gofuzz.go
  • parser.goparser.go

Tests to re-run (5)

  • fuzz_native_test.gofuzz_native_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • mcdc_supplement_test.gomcdc_supplement_test.go
  • obligation_evidence_test.goobligation_evidence_test.go
  • parser_test.goparser_test.go

What this rests on

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