Technical reference · package mechanics

Check the package. Keep the market claim separate.

This public synthetic pack demonstrates the domain-neutral integrity mechanics behind PairTrace. Its scenario predates the clinical/GxP focus. It is not a clinical/GxP case, customer result, or demand signal.

Download sample pack Run the verifier

01 · local verification

Verify locally, without an account.

Load the built-in sample or select the extracted folder. Seven checks run in your browser; Web Crypto recomputes SHA-256 locally.

A passing result establishes package integrity and internal consistency. It does not establish GxP conformity, evidence sufficiency, correctness, approval, legal validity, or independent witnessing.

Ready to verify No files have been read.
  1. pending
    Manifest structureWaiting for a pack.
  2. pending
    Protected file setWaiting for a pack.
  3. pending
    File sizes and SHA-256Waiting for a pack.
  4. pending
    Canonical package rootWaiting for a pack.
  5. pending
    Anchor receipt consistencyWaiting for a pack.
  6. pending
    Review annex bindingWaiting for a pack.
  7. pending
    Recorded release decisionWaiting for a pack.
Case
—
Release record
—
Package root
—

02 · reference anatomy

What this technical sample contains.

The synthetic screening-era scenario records request, authorization, baseline, change, replay, review, remediation, sign-off, and release as an append-only chain.

Open the HTML annex Inspect manifest.json
  1. Case definitionSynthetic actors, fixed roles, and explicit data status.
  2. Append-only eventsRequest through release decision, including the blocking path and remediation.
  3. Evidence filesBaseline and replay observations bound to their event records.
  4. ManifestSorted protected paths, byte sizes, SHA-256 digests, and a canonical package root.
  5. Anchor receiptPackage-root, manifest, and report digests are bound together. External retention still depends on the customer copy; this v0 receipt is not independently signed, timestamped, or witnessed.
  6. Offline verifierThe download bundles verify.html. Its SHA-256 is 65d1f0cbd0c90fc4862e343878e1f9ef673e30604d795e3a28135ebc8067fd8c, so the delivered verifier can be compared with the published one.

Current direction · Clinical / GxP

How this proof relates to the current direction.

The verifier and package format are reusable technical foundations. The current clinical/GxP work centres on post-approval correction lineage and cross-system evidence reconstruction, which this sample does not claim to demonstrate.

Share one post-approval change