🧾

Structural Receipt

Purpose-Resolved Transaction Evidence Reference Demo
Declare once. Resolve by purpose. Preserve through change. Verify independently.
Version v0.5.3 Operation Local Browser Core Deterministic Origin Native / Wrapped / Derived Evidence Purpose-Resolved Profiles Identified Data Context Declared Conformance Frozen + Hostile Verifier Python Companion Adoption Sidecar First
Demonstration Cases
Load a bounded case and inspect how the same evidence resolves differently by purpose.
CLEAN PURCHASE
Transaction Structure
Edit the declared structure. The visible receipt is a projection of the same underlying data.
Declared Items
Independent Payment Evidence
Declared Evaluation Context
Purpose Context
Human Receipt Projection
Presentation may change without changing the canonical purchase declaration.
Transaction Lineage
Adjustments are linked events. The original purchase is not silently rewritten.
RESOLVED
Linked Events
Structural Receipt v0.5.3 is a bounded local reference implementation with portable verifier-facing evidence bundles. Exported bundles are designed for separate local verification without requiring a shared account or network service. Purpose resolution carries no automatic execution authority. The reference does not execute payments, approve reimbursement, post accounting entries, certify tax treatment, authenticate issuers, prove physical delivery, or constitute legal or production assurance.
Compare Receipts
Compare another structural object against the current receipt.
Comparison Result
Load or paste a receipt to compare.
Add Linked Adjustment
The original purchase remains unchanged. A new lineage event records the change.
Adoption Paths
Structural Receipt can begin on one side of an exchange without requiring coordinated platform replacement.
Adopt on one side. Verify on the other. Integrate only when useful.
Producer-Side Adoption
Existing system → Structural Receipt sidecar → portable evidence bundle

The producing system can keep its current receipt or transaction record and add a Structural Receipt sidecar. A receiving party can reconstruct the exported bundle through a separate verifier without sharing the producer's application.

Verifier-Side Adoption
Existing structured source → declared bridge or adapter → WRAPPED / DERIVED Structural Receipt

A verifier can adopt the resolution model without requiring the source system to become a native Structural Receipt producer. Provenance and semantic-equivalence limits remain explicit.

Native End-to-End Adoption
Native producer → portable bundle → Structural Receipt-aware verifier

When both sides adopt the structure directly, the same identities, purpose profiles, evaluation context, lineage, and authority boundaries can move across the exchange.

Boundary
This reference demo directly creates, imports, resolves, exports, and reconstructs supported Structural Receipt objects and bundles. Generic conversion from arbitrary external formats belongs to the separate bridge and adapter artifacts in the release family.
Purpose Profile Manifest
Each bounded question declares its own dependencies, authority boundary, and limitations.
Purpose Resolution Detail
The result explains what was required, what was available, and what authority the result does not carry.
Verification Report
Producer-side deterministic reconstruction within the declared v0.5.3 reference profiles.
Evidence Bundle Reconstruction
Verifier-facing reconstruction checks the exported evidence without trusting producer PASS assertions.
Frozen Conformance and Tamper Corpus
Browser-side reconstruction of frozen positive vectors and declared negative or boundary vectors.
Hostile Input and Boundary Corpus
Adversarial checks for canonicalization, JSON parsing, money boundaries, context, provenance, and lineage replay.
Structural Receipt Full Audit
Primary producer-side regression gate for this standalone reference demo.
Audit not yet run.0/0
Audit not yet run.