A public, reproducible evidence bundle for relation-isomorphic protected computation. The fixtures are synthetic; no customer records, private crosswalk, credentials, native identifiers, local keys, or provider calls are included.

Verified results

Verification surfacePublished result
Relabeling-invariance blocks20/20
Eligible native edit relations preserved exactly23/23
Records verified per relation-isomorphism run53/53
Field values verified per run529/529
Batch-restoration adversarial cases14/14
Transformation adversarial cases10/10
Provider calls during preparation0

The pipeline being tested

Native synthetic records
→ Semantic Switch protected representation
→ qBlock / Qdrant Edge candidate partitions
→ Fracture adjudication
→ Forge canonical selections
→ local exact restoration through the private crosswalk
→ Shield forward-only baseline defense

The two input files describe the same relational object under different native relabelings. A correct generator must preserve the relational structure, not the native token identities. The relation audit separately requires every eligible native edit type to remain visible in the fictional representation.

Reproduce the evidence

  1. Obtain or build a Semantic Switch executable with the relation-isomorphism-v1 feature.
  2. Download verify.py and this pack's fixtures and harnesses.
  3. Run python verify.py --binary /path/to/semantic-switch.
  4. Compare the fresh JSON summary with the retained invariance result and exact-relation result.

The driver creates a temporary random local key, prepares both inputs, verifies every record and field, computes fresh reports, and deletes the temporary workspace. It exits successfully only when all 20 blocks and all 23 eligible relations pass.

Artifact inventory

Claim ceiling

These results establish deterministic transport fidelity, exact relation preservation, complete local verification, and adversarial restoration behavior on the declared synthetic fixtures. They do not establish anonymity, inference resistance, universal privacy, matching accuracy, production merge correctness, or independent validation of a customer population. Native rows, keys, and the private crosswalk remain under client control.