See what remains recorded with EVIDE
Two illustrated paths: decisions made by people, and declarations from AI systems.
Invented examples. This page illustrates how the service works: it makes no deposits and generates no documents.
How to read the diagrams
Entered by the depositor. EVIDE records it as declared; it does not verify it.
Assigned or calculated by the platform when the deposit is received.
Stays outside EVIDE. Only a reference, and its fingerprint if declared, is recorded.
What the record does not prove.
A business decision is challenged months later. What will those assessing it have available?
When a dispute arises, the decision, its declared authorship, the documents and the timeline need to be reconstructed. EVIDE Human Intake helps prepare records that can be made available to lawyers, experts, authorities and judges for examining what was declared and submitted.
In this example you will see how to:
- Make attribution examinable - the depositing account is kept distinct from the person named as the decision-maker.
- Reconstruct the documentary sequence - the declared decision time is kept distinct from the receipt time assigned by EVIDE.
- Clarify what was received - documents only referenced, with the fingerprint declared by the depositor, are kept apart from files actually uploaded, whose fingerprint EVIDE calculates.
- Link decisions and reservations - the link between a deposit and a later written reservation remains available for examination.
- Prepare for later review - understand what remains available afterwards, with the EAR and the optional FEDIS explained separately.
The aim is to give those assessing a decision documented, examinable records, with explicit attribution, references, times and limits. The assessment of their content and evidentiary weight remains with those responsible for making it.
Tomorrow's reconstruction begins with today's records.
The supplier withdrawal
Alfa Components decides to withdraw from a supply contract with Beta Logistics because of repeated late deliveries. The purchasing manager then puts a written reservation on record. Months later, in this scenario, Beta disputes the withdrawal. What can a lawyer examine?
Companies and people in this example are invented.
Two different roles
Depositing account
The EVIDE account that makes every deposit in this example. Its identity is verified through DAPI and it signs in with an email one-time code.
Person named as decision-maker
Laura Neri, Chief Financial Officer. Named in the form by the depositor. EVIDE does not verify that she exists or that she had the authority to decide.
The person fills in the form
In New request, the depositor chooses the evidence type Structured human action and completes the form. A selection of the real fields is shown here, with invented values.
EVIDE records the deposit
Received
The structured declaration: title, decision type, declared date, name and role, and the document reference with its declared fingerprint.
- Recorded by EVIDE: Identifier assigned to the deposit
- Recorded by EVIDE: SHA-256 fingerprint of the canonical record of the declaration
- Recorded by EVIDE: Receipt time (UTC), assigned by EVIDE
- Recorded by EVIDE: Evidentiary Artifact Record (EAR), generated automatically
Stays outside
The meeting minutes. EVIDE does not receive the document: it records the reference and the fingerprint declared by the depositor.
Two times, kept apart
The receipt time shows when EVIDE received the deposit. It is not evidence of when the decision was actually taken.
What the fingerprint covers
Covered by the fingerprint of the deposit: the canonical record of the declaration - title (recorded as the decision summary), decision type, declared date and time, name and role, document references with their declared fingerprints, the DAPI of the depositing account, and protocol data added by the platform.
Kept in the record, but outside that fingerprint: description, internal contact, additional notes, case topic, case code, evidence reference, business area and organisation.
The EAR has its own fingerprint. It reproduces, among other things, the title, the description, the declared name, role and date, the document references and the fingerprint of the deposit.
The form for people does not offer EVIDE ANCHOR declarations or declared relations between declarations: those are features of the API path.
A written reservation is linked
From the page of the first deposit, the depositor uses + Create linked request and uploads the reservation as a PDF. In the scenario the reservation is attributed to the purchasing manager; the upload is made by the depositing account.
- Recorded by EVIDE: The PDF is received: EVIDE calculates the SHA-256 fingerprint of the file exactly as uploaded.
- Declared: Title and description describe the file; its attribution to the purchasing manager is a declaration.
- The platform keeps the file only temporarily: it is deleted when the service's retention period expires, or earlier, when a FEDIS is issued. The fingerprint and the EAR remain. The owner must keep their own copy.
- Not established: The link does not show that the reservation was delivered, read or accepted.
What a lawyer can examine
Months later, the lawyer examines what the owner makes available. Deposits are not public: publication in the registry is a separate, optional step (see below).
Declared content and attribution
What was declared, to whom it was attributed and in which role.
Two separate times
The declared decision time and the EVIDE receipt time are distinct. Any date appearing inside the uploaded reservation remains part of that document's content.
Document references
If the company produces the minutes, their fingerprint can be compared with the one declared at deposit.
File identity
The reservation produced by the owner can be checked against the fingerprint recorded at upload.
Links between deposits
The order of the two deposits and the link between them.
Materials available afterwards
The record page of each deposit, the canonical JSON of the declaration with its checksum, the EAR of each deposit, and the owner's own copy of the PDF.
After the deposit: EAR, optional FEDIS, registry
Evidentiary Artifact Record (EAR)
- Recorded by EVIDE: Generated automatically by the platform when the deposit is finalised - not on request.
- Recorded by EVIDE: A plain-text summary of the recorded state of the deposit, which the owner can download with its own SHA-256 checksum.
- Recorded by EVIDE: When the service generates a new EAR, it creates a separate version rather than overwriting the previous one.
- Not established: It records what was declared and what the platform computed. It is not a verification of the facts.
FEDIS - optional
Forensic Evidence Declaration & Integrity Statement. The owner can request it at deposit or later, from the record page.
- RequestStarts an evaluation and a quote. It does not generate the document.
- Evaluation and quoteCarried out by the certifier.
- GenerationOnly on the certifier's explicit command.
- Qualified electronic signatureApplied by the certifier: a distinct, later step.
- Qualified electronic time stampA further distinct step.
What a FEDIS identifies, with SHA-256 fingerprints
Structured declaration or API deposit: the Canonical Intake Record and the frozen EAR.
Uploaded file: the fingerprint of the received file, calculated by EVIDE at intake, and the frozen EAR. The file itself is not part of the FEDIS package and is not kept by the platform after certification.
- Not established: The time stamp applies to the FEDIS document when it is affixed; it does not retroactively make the intake time qualified. A FEDIS does not prove the event or the truth of the content, and guarantees neither admissibility nor evidentiary value.
Public registry - a separate step
Optional: publication is the owner's choice. It is possible only after a FEDIS has been issued, and the certifier carries it out on the owner's instruction. It is never an automatic result of a deposit or of a FEDIS.
In this illustrated example no FEDIS is requested and nothing is published.