Transparency, Provenance, and Operational Evidence

Direct answer

Eviulon separates documentary provenance, artifact integrity, implementation state, operational observation, institutional authority, legal effect, independent review, and correction lineage. Evidence in one layer never silently substitutes for another.

Text-first system diagram

SOURCE REPORT / GOVERNED RECORD
        │ documentary provenance
        ▼
PACKAGED ARTIFACT ── digest / schema / release identity
        │ does not prove operation
        ▼
IMPLEMENTED CAPABILITY ── code, route, tests
        │ does not prove observation
        ▼
OPERATIONAL EVIDENCE ── authorized, time-bounded observation
        │ does not create authority
        ▼
INSTITUTIONAL DECISION ── named authority, reasons, review
        │ may still lack external effect
        ▼
LEGAL / EXTERNAL EFFECT ── separately evidenced or UNAVAILABLE

The diagram is ordinary text, remains available without JavaScript, and is preserved in print.

Conceptual distinctions

Activate a heading to reveal its bounded definition. Every definition remains represented in semantic HTML and has a canonical record.

Documentary provenanceCURRENT_WITH_QUALIFICATIONS

A traceable relationship among a source, governed edition, correction record, memory identifier, and public projection.

Implies: source lineage and correction history
Does not imply: cryptographic signing, operational truth, or legal authority
Evidence required: source digest, durable path, correction state, and edition identity

Open concept record · JSON

Artifact integrityCURRENT_WITH_QUALIFICATIONS

Evidence that packaged bytes match a declared digest, manifest, or deterministic build result.

Implies: byte-level consistency within the measured artifact
Does not imply: deployment, authorship, institutional authority, or external recognition
Evidence required: declared algorithm, digest, package inventory, and replay evidence

Open concept record · JSON

Implementation stateCURRENT_WITH_QUALIFICATIONS

The current repository state of code, routes, schemas, tests, and generated records.

Implies: what the accepted source tree contains
Does not imply: that a production service is running or authorized
Evidence required: release identity, code path, test evidence, and explicit limitations

Open concept record · JSON

Operational evidenceCURRENT_WITH_QUALIFICATIONS

Time-bounded, authorized evidence that a named service or institution performed a stated action or remained available during a defined window.

Implies: an observed operational condition within its scope
Does not imply: permanent availability, legal effect, or independent certification
Evidence required: observer identity, authorization, time, method, target, and result

Open concept record · JSON

Institutional authorityCURRENT_WITH_QUALIFICATIONS

A bounded delegation or constitutional basis permitting a named institution to make a class of decisions.

Implies: decision competence within the stated scope
Does not imply: external recognition, infallibility, or unlimited power
Evidence required: authority source, scope, effective period, decision record, and review path

Open concept record · JSON

Legal or external effectCURRENT_WITH_QUALIFICATIONS

A consequence recognized by the relevant legal or external system, not merely asserted in local documentation.

Implies: an independently supportable consequence where evidence exists
Does not imply: that local publication alone binds outside parties
Evidence required: applicable authority, forum, operative act, enforceability, and current status

Open concept record · JSON

Independent reviewCURRENT_WITH_QUALIFICATIONS

Assessment by a reviewer institutionally and operationally separate from the decision owner, with disclosed method and scope.

Implies: a distinct review perspective within the stated mandate
Does not imply: universal certification or absence of error
Evidence required: reviewer independence, competence, evidence access, method, findings, and date

Open concept record · JSON

Correction lineageCURRENT_WITH_QUALIFICATIONS

An append-only chain preserving an earlier claim while publishing its correction, successor, or withdrawal.

Implies: historical accountability and current disposition
Does not imply: silent rewriting or deletion of inconvenient history
Evidence required: predecessor, correction reason, successor, effective date, and affected projections

Open concept record · JSON

Correction-first provenance

Memory ID: REP-MACHINE-TRANSPARENCY-CENTER-001
Source file: Machine Intelligences Transparency Center.md
Source SHA-256: 46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d
Correction record: EVI-RCOR-237-001
Active-edition state: CORRECTED_BEFORE_STORAGE
Raw-source retention: HASH_ONLY_NO_BODY_IN_RELEASE
Durable report: docs/long-term-memory/reports/machine-intelligences-transparency-center.md

Append-only correction record · Registry JSON · Definitions CSV · All-169-report revalidation

Related governed records

Operational-evidence boundary

A definition, report, route, checksum, key, credential, schema, fixture, local test, runtime measurement, or reachable URL does not by itself establish operational service, identity continuity, authority, legal effect, personhood, consciousness, sentience, citizenship, consent, responsibility, judgment, financial activity, external recognition, or independent review. Unknown, disputed, stale, unavailable, and proposed states remain explicit.

Open correction and review procedures.