ENTITY Documentation Portal
Developer manual · ENTITY v3.4.3 · evidence

Evidence API

Current runtime: ENTITY v3.4.3. Evidence/attestation surfaces remain distinct from objective truth, legal title and payment. BTDU remains component version 3.4.2 unchanged and can attach exact-content evidence to governed objects.

ENTITY treats evidence as support for a claim, not as automatic truth. The current runtime preserves explicit evidence, attestation, trust-policy, external-anchor, contestability and causal-attribution boundaries.

Verification boundary

REALITY → OBSERVATION → CLAIM → EVIDENCE → ATTESTATION → VERIFICATION → GOVERNED ENTITY STATE

There are separate questions: is the record cryptographically intact, does it conform to ENTITY semantics, does the applicable trust policy accept it, and does the evidence adequately support the real-world claim? A positive answer to one does not force a positive answer to the others.

Evidence objects

Evidence should be immutable or content-addressed where practical, identify media/type and source/submitting Entity context, and retain enough information to evaluate what claim it supports. BTDU ingestion can bind exact content hashes/evidence to governed information objects without converting storage topology into ownership.

Attestation

An attestation is a signed statement by an identified attestor. In the Universal Transaction Fabric, attest() records an evidence SHA-256 and claim body and explicitly marks the attestation as evidence rather than truth.

Trust policies

Threshold trust policies can require minimum attestations and required/allowed attestors. evaluate_trust() checks signatures and policy satisfaction while explicitly returning truth_inferred: false. Policy satisfaction therefore means the configured evidence rule was met, not that objective truth was proven.

External anchors

External registries, timestamps, public ledgers or other anchors may strengthen evidence but do not become general sovereign authority over the Entity. Store the exact anchor reference and interpretation applied at the time.

Contestability

Evidence-backed systems must support contrary evidence, revocation, supersession and dispute without rewriting historical signed records. A later conclusion can supersede an earlier operational conclusion while retaining both records and the reason for change.

Economic causality

When evidence is used to justify contribution or value attribution, record the actual causal link and terms. ENTITY deliberately permits zero monetary value and zero contribution weight where evidence does not support a stronger claim; provenance readiness is not realized revenue.

Historical evidence

Earlier v3.3/v3.4.2 evidence remains under its original version/qualification labels. Current application documentation uses v3.4.3 as the runtime label while preserving BTDU's unchanged 3.4.2 component identity.