Skip to content
Procurement kit

# Procurement‑ready — without the bloat.

Big tech procurement buys deliverables, acceptance tests, and fail‑closed semantics.

Contact security Run offline proof Pilot‑in‑a‑Box Download sample pack

### Pilot‑in‑a‑Box (Self‑serve, ~30 minutes)

A buyer‑run evaluation kit that produces deterministic PASS/FAIL/HOLD receipts and a DSSE signing request for a signed evaluation report.

- No meeting. No uploads. Public‑safe.
- Fail‑closed: missing/stale/unverifiable prerequisites → HOLD and block.
- Portable: JSONL receipts + summary bundle for internal ticketing.

Download Pilot‑in‑a‑Box HALTSEAL overview Offline verifier

Non‑binding. No SLA. No license grant.

Copy‑paste clause pack
Send to Security Kingdom RFC PDF

    Supplier SHALL deliver procurement‑grade accountability artifacts for the declared scope, including:
    (1) deterministic validator outputs (PASS / FAIL / HOLD) with stable reason codes;
    (2) replay‑verifiable receipts and portable conformance packs sufficient for independent verification;
    (3) fail‑closed gates at declared control points that block side effects unless a valid, in‑scope Permit is verified;
    (4) permits that are scope‑ and time‑bounded and minted only after PASS;
    (5) audit sampling evidence demonstrating no in‑scope side effects occur without valid permits; and
    (6) retention + replay support for the agreed audit window.

    If evidence is missing, stale, inconsistent, or unverifiable under the pinned policy/validator versions,
    the system SHALL return HOLD and fail closed for sensitive side effects.

## Evidence anchors for Security & Counsel

Procurement‑grade, offline‑verifiable artifacts for Security and Counsel.

Non‑binding unless signed. No license by publication.
Evidence Pack index Attachment bundle export
Air‑gapped verifier kit Offline‑first
Offline‑only Self‑verify
Signed releases • commitments • keyring governance

### Air‑gapped reviewer kit

Run MVG verifiers in fully disconnected environments — designed for skeptical security review and audit attachment workflows.

Download kit →
Licensing diligence
Offline‑verifiable Two‑layer commitment
Tier B under NDA

### Verifiable diligence pack

Replace email threads with immutable, versioned diligence artifacts — privately receipted, publicly committed (blinded).

Open →
Assurance Pack
Offline‑verifiable DSSE + SHA‑256
Public‑safe

### Assurance artifacts

Procurement‑grade assurance bundle with integrity proofs and a local verifier workflow — built for skeptical review.

Open →
Approval receipts
Ticket‑bound Org threshold
Hardware‑attested (optional)

### Signed internal approvals

Turn verification results into attachable approval receipts for JIRA/ServiceNow — countersigned, policy‑evaluated, and offline‑verifiable.

Create receipt →

### What auditors attach

- Audit summary (PDF) — one‑page printout from the verifier (PASS/FAIL/HOLD + Approval ID + boundary language).
- Countersigned approval receipt (JSON) — ticket‑bound receipt with org threshold evaluation for internal review workflows.
- Kit supply‑chain verification receipt (JSON) — kit SHA‑256 + keyring snapshot hash + commitments/headchain verdicts for audit replay.

#### Attachment naming convention

- `MVG_AuditSummary_<ApprovalShort>.pdf`
- `MVG_CountersignedApproval_<ApprovalShort>.json`
- `MVG_KitSupplyChainReceipt_<ApprovalShort>.json`

Use the same Approval short code printed in the PDF and embedded in JSON receipts to keep attachments matchable.

Attachment bundle export (offline) Naming spec

Print diligence summary Print assurance summary Print kit supply‑chain summary

Reviewer‑generated, offline‑verifiable artifacts. Non‑binding unless signed.

## Reviewer kit supply‑chain governance

Signed keyring snapshots, head‑of‑heads, and rotation policy — audit‑replayable offline.

Non‑binding unless signed. Public materials do not grant any patent license.
Governance → Verify kit supply‑chain →
Signed keyring
Rotation policy Grace window Fail‑closed

### Keyring snapshots + rotation

A signed keyring snapshot (DSSE) with roles, deprecation, and grace windows — designed for reproducible audit and safe key rollover.

Open policy →
Head‑of‑heads
Append‑only Signed heads Update trail

### Commitment log update chain

A log‑of‑heads binds commitment log heads over time, so release commitments remain auditable even as the log updates.

Open headchain →
Offline verification
ZIP + DSSE Key lifecycle PASS / FAIL / HOLD

### Verify supply‑chain offline

One‑screen verdict for signature validity, key status, inclusion proofs, and headchain continuity — built for skeptical review.

Verify →

## Minimum requirements + acceptances

What buyers can score. What sellers must prove.

Requirements SHALL

- P1 Deliver artifacts: policy IDs, validator outputs, receipts, permits, conformance packs.
- P2 Deterministic PASS/FAIL/HOLD with stable reason codes + declared scope.
- P3 Receipts replayable under pinned versions + canonicalization.
- P4 Fail‑closed gates at declared control points (block on HOLD/FAIL).
- P5 Permits minted only after PASS; scope + TTL bounded.
- P6 Retention + auditor replay support for the agreed window.

Acceptance Buyer‑run

- P1 Validate signatures + required fields.
- P2 Run test vectors; reproduce expected outcomes incl. negatives.
- P3 Replay a sample using only conformance pack + allowed evidence handles.
- P4 Demonstrate deterministic blocking at each control point in scope.
- P5 Audit sampling shows no in‑scope side effects without a valid permit.
- P6 Replay succeeds within retention; degraded mode remains fail‑closed.

Deep dive 30 min

### What we show

- Pick one action surface: egress or dispatch.
- Show fail‑closed behavior: missing/stale/unverifiable → HOLD + block.
- Export receipts designed for Security review.

Under NDA Clean

### What you get

- Evidence schema + reason code registry + test vectors.
- Integration details for your enforcement chokepoint.
- Pilot plan + acceptance criteria for production hardening.

Contact security Products

## SOC 2 / ISO 27001 mapping (illustrative)

Which artifacts can be submitted as audit evidence. (Not legal advice.)

Run verifier

Artifact | Evidence | SOC 2 | ISO 27001 | How to verify
--- | --- | --- | --- | ---
Evidence Pack (manifest + SHA256SUMS) | Completeness + tamper‑evidence of the audit bundle | `Security + Change Mgmt` | `Change Mgmt • Evidence integrity` | /verify offline replay
Pinned registry snapshots | Policy/version pinning; drift‑resistant semantics | `Change Mgmt` | `Configuration • Change Mgmt` | /verify pins + snapshot IDs
Deterministic PASS/FAIL/HOLD | Control operation with fail‑closed behavior | `System Ops` | `Monitoring • Operational controls` | /verify verdict reproduction
Reason codes (stable) | Explainable enforcement decisions under pinned semantics | `Monitoring + Incident response` | `Monitoring • Event analysis` | /verify reason registry
IAL receipts (hash‑chained) | Append‑only accountability trail (who/what/why) | `Logging + Monitoring` | `Logging • Monitoring` | /verify receipts integrity
Permits (scope + TTL + audience) | Pre‑action authorization bounds | `Logical access` | `Access control` | Permit validation
Signed Conformance Report export | Machine‑ingestable evidence for GRC & auditors | `Reporting` | `Audit evidence` | Download JSON / signed DSSE

This mapping is illustrative. Your auditor defines scope and applicable control statements.