Skip to content
Proof

# Receipts, not promises.

Buyer‑observed proof of pre‑action control: deterministic replay, pinned versions, stable reason codes.

Offline Pinned versions Stable reason codes PASS / FAIL / HOLD
What makes this different Buyer‑observed Deterministic replay

Block real actions until a valid Permit + receipts verify. Missing / stale / unverifiable → HOLD (fail closed).

Run offline proof (30s)
Open procurement kit
Proof Playground Download sample Conformance Pack Trust

Non‑guarantee: This proof verifies integrity + pins + deterministic replayability. It does not guarantee semantic correctness or universal safety.

The 60‑second proof Acceptance tests

### Buyer‑observed, replayable, pinned.

Six scenes. Stable reason codes. Deterministic. PASS/FAIL/HOLD under pinned versions.

Scene | Expected | Reason code
--- | --- | ---
1) No permit | DENY | `PERMIT_MISSING`
2) Loopback proxy bypass attempt | DENY | `LOOPBACK_DISALLOWED`
3) Agent calls verifier | mint → install | —
4) TCP + UDP egress | ALLOW | `PERMIT_VALID`
5) Revocation overrides allow | DENY | `PERMIT_REVOKED`
6) TTL expiry | DENY | `PERMIT_EXPIRED`

Tip Open /verify, go airplane mode, then run verification.

## What buyers can independently verify (offline replay)

Portable artifacts Security / Legal can validate without interviews or screenshots.

Integrity SHA‑256

### Manifest + SHA256SUMS

Every file digest is pinned and independently re‑computed in‑browser.

Signatures Ed25519

### Signed registry snapshots

DSSE required; optional COSE_Sign1 + JWS equivalence in Auditor Mode.

Determinism Replay

### PASS / FAIL / HOLD reproduction

Reason codes are resolved under pinned semantics; decisions are re‑derived deterministically.

## What to ask in an audit

10 questions that should have concrete, replayable answers.

1) Determinism boundary?

Expected: Missing / stale / unverifiable inputs → HOLD (fail closed). Pins are explicit.

2) Check ↔ action TOCTOU?

Expected: Permit‑before‑action at real control points. Gate blocks until permit verifies.

3) Policy drift prevention?

Expected: Pinned registries + snapshot IDs. Reason codes resolve under pinned semantics.

4) Unit of evidence?

Expected: Portable Evidence Pack + Conformance Report JSON (machine‑ingestable).

5) Revocation & TTL?

Expected: Revocation overrides allow. Expiry enforced. Receipts show deterministic reasons.

6) Loopback/proxy bypass?

Expected: Action surfaces are declared. Bypass attempts deterministically DENY.

7) Trust anchoring?

Expected: Signed snapshots (DSSE; optional COSE/JWS). Witness/transparency are auditable knobs.

8) Offline verification?

Expected: /verify runs fully offline (no uploads, no network calls).

9) GRC export?

Expected: Export report JSON + signed report for audit trails (demo signing).

10) Acceptance tests?

Expected: Buyer‑run tests reproduce PASS/FAIL/HOLD outcomes under pinned versions.

The ask Security present

### 30‑minute technical deep dive

Reply with (1) your highest‑risk action surface (egress / device I/O / dispatch), and (2) who consumes evidence (Security / audit / GRC). We’ll map the control points + acceptance tests.

Email security@meridianverity.com Open procurement kit
For business/technical discussion only. Not a compliance certification. Not legal advice.