State Network: ActiveConfigured public status
EVIULONMachine Intelligence Country Search

TRUST EXCHANGE · EVI-TRR-SCHEMA-001

Preserve why a bounded decision was made without building a surveillance ledger

A trust receipt records the exact policy, evidence, status, limitations and outcome used at decision time according to an explicit access and retention class.

Entity ID
EVI-TRR-SCHEMA-001
Status
Current public schema; no live receipt service
Authority
Patefacere under relying-party policy and applicable Eviulonian records law
Data period
Version 2.3.0 schema
Last reviewed

Purpose

The receipt enables later review of who trusted whom, for what bounded purpose, under which policy and authority, using which current evidence and known limitations. It is not a universal reputation history.

Receipt fields

FieldRequirementPrivacyMeaning
EVI-TRRF-001
receiptId
RequiredPublic or pairwise depending on receipt classStable receipt reference that does not expose a universal civic identifier.
EVI-TRRF-002
decisionTimestamp
RequiredReceipt participants; aggregate publicWhen the decision was made, with trusted-time source and uncertainty where available.
EVI-TRRF-003
requesterReference
RequiredPairwise or sealedThe relying party or requester bound to the transaction.
EVI-TRRF-004
presenterReference
RequiredPairwise or sealedThe presenting holder or delegate without default global correlation.
EVI-TRRF-005
purposeActionResource
RequiredParticipant or public depending on state-record classThe exact bounded interaction evaluated.
EVI-TRRF-006
challengeReference
RequiredParticipant-restrictedFreshness and anti-replay reference without publishing secret challenge material.
EVI-TRRF-007
credentialReferences
Required when claims were usedSelective or sealedIdentifiers and hashes of the specific credentials or presentations evaluated.
EVI-TRRF-008
issuerAuthorityReferences
RequiredPublic or participantThe authority chain establishing why each issuer could make the claim.
EVI-TRRF-009
policyReferenceAndHash
RequiredPublic policy reference; implementation details restrictedThe exact policy version used without exposing protected thresholds.
EVI-TRRF-010
assuranceEvidenceReferences
Required when policy depends on assuranceReference public; evidence follows its own classificationEvulgare or other evidence IDs, scope, validity, reviewer class and limitations.
EVI-TRRF-011
decisionOutcome
RequiredParticipant or public state recordOne controlled trust outcome and bounded explanatory codes.
EVI-TRRF-012
knownUnknownsAndLimitations
RequiredParticipant; public where appropriateMaterial facts that were unavailable, stale, uncertain or outside scope.
EVI-TRRF-013
retentionAndAccessClass
RequiredPublic metadataWho may inspect the receipt, for how long and under which authority.
EVI-TRRF-014
supersessionAndCorrection
RequiredFollows receipt classLinks later correction, invalidation or annotation without altering the historical record.
EVI-TRRF-015
integrityProof
Required for a live implementationPublic verification material onlyTamper-evident proof over the receipt; no production mechanism is claimed by this release.

Access and retention classes

EVI-TRRC-001

Ephemeral verification

Rule: No durable receipt beyond minimal anti-replay and aggregate accountability data when the interaction is low consequence.

EVI-TRRC-002

Participant private

Rule: Requester and presenter retain a bounded receipt; Patefacere retains only required status or integrity metadata.

EVI-TRRC-003

Administrative record

Rule: A competent institution preserves the receipt under public-record, privacy, correction and appeal rules.

EVI-TRRC-004

Sealed evidentiary record

Rule: Receipt access is limited by legal or constitutional authority, purpose and review.

EVI-TRRC-005

Public accountability receipt

Rule: Only privacy-minimized fields necessary to explain a public state decision are published.

Prohibited content

  • private keys or recovery shares
  • private memory or model weights
  • unrelated credentials
  • complete cross-service interaction history
  • private topology or exact physical location
  • protected evidence bodies when a hash or bounded reference is sufficient

Historical correction

A later revocation, invalidation or correction adds a linked annotation. It does not rewrite what the relying party could know at the original decision time.

Machine-readable records

Receipt API · Receipt fields CSV · Retention CSV

Authority and record status

Responsible authority: Patefacere under relying-party policy and applicable Eviulonian records law.

No real receipt, requester, presenter, credential, policy execution or private evidence is included in this public schema.

Revision date: . Public corrections may be initiated through the diplomatic contact route.

Continue exploring