The record. Its context. The proof.

Pack ID

recourse-copy-pack-v1

Tenant

demo-tenant

Issued at

2026-09-09T23:59:46.347Z

Query

Explicit record ID selection; no semantic search The exact selection that produced this population. A pack without its query is a claim, not evidence.

Filters

none None. The population was selected by explicit record ID, not by a filter.

Population

Exactly the three records submitted in source-inputs.json using request key recourse-copy-pack-v1; not the whole tenant. 3 matched, 3 included, 0 not included Matched is what the query returned. Included is what this pack ships.

Collection cutoff

2026-09-09T23:59:46.347Z The instant the population was fixed. Nothing recorded after it can be in this pack.

Ingestion watermark

sequence 7 How current the underlying data was when this pack was collected. It is not a claim that the tenant is complete.

Index version

none No search index produced this population, so there is no index version to state.

Missing evidence

Every record in the stated population is included. 3 matched the query, 3 are in this pack, 0 were left out. 5 further categories are recorded as not supplied for the included records: Policy text and policy validity dates are not supplied; only policy reference strings are recorded; Approvals, approver identity, review dates, corrections and supporting attachments are not supplied; No original external export, upstream authenticity evidence or historical custody trail is supplied; these are synthetic API inputs; Private inputs are empty objects; no hidden rationale or private attachment can be recovered from this sample; No independent time evidence, search index or complete-tenant collection is claimed.

Pack hash

e98b9e2aa30e4d3d1d76a2e706a324c93bb93e847a88a83153d639799cb93e2f SHA-256 over the canonical scope statement and the SHA-256 of every evidence file. Recompute it from the extracted bytes.

Recipients

none No recipient was recorded. This pack was not issued to a named party.

Verification

3 of 3 receipts verified. Verified · dev signer Development signer means integrity under a published dev key and no independently trusted time.

Searchable-through

Not available in this preview There is no search index here, so nothing states how far search coverage reaches. It is separate from receipt state and is never a durability state.

Semantic search cannot establish completeness. Exact selection defines this pack's scope; it cannot reveal records the source never submitted. The same rows are written into pack.json and VERIFY.txt inside the download.

How the pack hash is made. pack_hash is the SHA-256 of canonical JSON (keys sorted, no whitespace) over {format:"recourse-pack-hash-v2", pack_id, tenant_id, issued_at, scope, collection_cutoff, ingestion_watermark, index_version, missing_evidence, recipients, included_adr_ids, chain_of_custody, evidence}, where every field except evidence is copied verbatim from pack.json and evidence maps each receipt file name, trust.json, SYSTEM-DESCRIPTION.txt and CERTIFICATION-TEMPLATES.txt to the SHA-256 of its extracted bytes. Issued at and Collection cutoff are inside the bytes this hash covers, so the stated scope cannot be changed without changing the hash. It does not cover VERIFY.txt, pack.json or MANIFEST.json, which are unsigned wrapper.

Received means acknowledged. Durable means committed to the configured persistence layer. Sealed means included in a signed root with a receipt. Acknowledged is not durable.

Download the exact submitted JSON · Download the actual acknowledgement

{
  "schema_version": "1.0",
  "occurred_at": "2026-08-01T12:00:00.000Z",
  "subject_id": "copy-pack-synthetic-1",
  "actor": {
    "type": "agent",
    "id": "copy-pack-risk-agent"
  },
  "decision": {
    "action": "security.exception.evaluate",
    "outcome": "allow"
  },
  "model": {
    "provider": "synthetic",
    "name": "fixture-risk-model",
    "version": "v1"
  },
  "policy_refs": [
    "policy_synthetic_v1"
  ],
  "private_fields": {}
}

{
  "schema_version": "1.0",
  "occurred_at": "2026-08-02T12:00:00.000Z",
  "subject_id": "copy-pack-synthetic-2",
  "actor": {
    "type": "agent",
    "id": "copy-pack-risk-agent"
  },
  "decision": {
    "action": "security.exception.evaluate",
    "outcome": "deny"
  },
  "model": {
    "provider": "synthetic",
    "name": "fixture-risk-model",
    "version": "v1"
  },
  "policy_refs": [
    "policy_synthetic_v1"
  ],
  "private_fields": {}
}

{
  "schema_version": "1.0",
  "occurred_at": "2026-08-03T12:00:00.000Z",
  "subject_id": "copy-pack-synthetic-3",
  "actor": {
    "type": "agent",
    "id": "copy-pack-risk-agent"
  },
  "decision": {
    "action": "security.exception.evaluate",
    "outcome": "defer"
  },
  "model": {
    "provider": "synthetic",
    "name": "fixture-risk-model",
    "version": "v1"
  },
  "policy_refs": [
    "policy_synthetic_v2"
  ],
  "private_fields": {}
}

Development signer means integrity under a published dev key and no independently trusted time. Sealing binds what was recorded; it does not establish that the claimed event happened.

Every record in the stated population is included. 3 matched the query, 3 are in this pack, 0 were left out. 5 further categories are recorded as not supplied for the included records: Policy text and policy validity dates are not supplied; only policy reference strings are recorded; Approvals, approver identity, review dates, corrections and supporting attachments are not supplied; No original external export, upstream authenticity evidence or historical custody trail is supplied; these are synthetic API inputs; Private inputs are empty objects; no hidden rationale or private attachment can be recovered from this sample; No independent time evidence, search index or complete-tenant collection is claimed.

• Policy text and policy validity dates are not supplied; only policy reference strings are recorded.
• Approvals, approver identity, review dates, corrections and supporting attachments are not supplied.
• No original external export, upstream authenticity evidence or historical custody trail is supplied; these are synthetic API inputs.
• Private inputs are empty objects; no hidden rationale or private attachment can be recovered from this sample.
• No independent time evidence, search index or complete-tenant collection is claimed.

Approvals: not supplied. Corrections: not supplied. Review dates and decision rationale: not supplied. They have not been inferred from an allow, deny or defer outcome.

1. Obtain the expected public development fingerprint separately from the producer. This fixture's pin was fetched from authenticated local status before the receipts, not trusted because it appeared inside them.
2. Run the verifier with that expected pin. It checks the envelope, chain link, inclusion proof, timestamp signature and trust match.
3. Compare the source public fields and dates, then review the cutoff and missing-evidence list. Individual receipts do not prove collection completeness or the full tenant chain.

Same-service pin distribution demonstrates consistency under the development key. It is not an independent trust authority. Development signer means integrity under a published dev key and no independently trusted time.

./recourse-verify receipt-1.json --dev-pin 1243d4dabe0c7218105918b3fd94be21d6a25973c4f1b4d4eb777a7543a4c9a1

The pack statement · File manifest and SHA-256 hashes · System description · Certification templates for counsel · Capture record, outside the pack · Download verification instructions · Captured public trust metadata · Actual verification results · Get the offline verifier

Expected result for each sample receipt: verified: true, trust: dev-pinned, trusted_time: false. A different expected pin fails trust.