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-103SystemApproved

When GetUnsafeString is called twice with identical JSON input and identical key paths, the parser shall return identical raw string values and identical error values on both calls.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass.
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 is called twice with identical JSON input and identical key paths, the parser shall return identical raw string values and identical error values on both calls.

FRETish formula
the parser shall always satisfy !getunsafestring_called_twice_with_same_input | getunsafestring_returns_identical_results
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

GetUnsafeString must be deterministic even though it skips unescaping. The same input must always produce the same raw string view.

getunsafestringdeterminism

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 21, 2026, 00:00 UTC · Claude · 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.

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

    GetUnsafeString (parser.go:2034) is a thin wrapper over Get that returns bytesToString(&v) with no mutable state, caching, or randomness, so two calls on identical input and identical key paths are structurally deterministic. TestGetUnsafeStringDeterminism (obligation_property_test.go:181) confirms v1==v2 and matching error nilness, and the MCDC Row2 witness asserts v1==v2 with both errors nil. Get is a pure read over the input slice, so the returned raw string aliases the same underlying bytes on each call. All witness tests pass and no KI touches this determinism property.

    Cited code (4)

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 aren't available for a historical run

The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. 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).

FRETish formula

the parser shall always satisfy !getunsafestring_called_twice_with_same_input | getunsafestring_returns_identical_results

Variables

NameTypeDirectionDescription
getunsafestring_called_twice_with_same_inputTrue when GetUnsafeString is called twice with identical input.
getunsafestring_returns_identical_resultsTrue when GetUnsafeString returns identical raw string values on both calls.

Witnesses· 3 scenarios total

  • TestMCDC_SYS_REQ_103_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_103_Row2_InvariantViolation
    exercises 1 condition scenario
  • TestGetUnsafeStringDeterminism
    exercises 1 condition scenario

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
#getunsafestring_called_twice_with_same_inputgetunsafestring_returns_identical_resultsResultProvesCovering test
1FFTgetunsafestring_called_twice_with_same_input
2TFFgetunsafestring_called_twice_with_same_input
3TTTgetunsafestring_returns_identical_results

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
0
Tests
2
At-risk contracts
0

Tests to re-run (2)

  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_property_test.goobligation_property_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