Complete Guide Human Structured Intake EVIDE Schema 2.1

Human Structured Intake (HSI)

The complete reference: every field, every allowed value, every conditional rule
Human Structured Intake lets a person record, in structured form, a decision, determination, or intervention, together with the evidentiary context that was declared available at the moment the decision was closed.

It preserves that a decision was declared, by whom, in what declared role, when it was closed, and under what declared threshold, readiness, and trace conditions. It does not determine whether that decision was correct, lawful, or optimal, and it does not independently verify the truth of every field a person declares.
Select Your Language
EnglishItalianoFrançaisDeutschEspañol
Documentation  ›  Human Structured Intake
Explore the documentation - select a guide:
Internal procedures and HSI
Already have procedures, tickets and audit logs? HSI does not replace them.

Many organizations document decisions and exceptions with procedures, approval workflows, ticketing systems and audit logs. That is exactly how it should be. But having an internal procedure is not the same as preserving the declared context of a decision in an independently verifiable record. The difference is where the record lives.

Internal tickets, workflows and logs

  • They stay within the systems of the same organization that made the decision.
  • They are managed and retained by whoever administers them, under internal rules.

Human Structured Intake

  • The declaration is deposited externally, in EVIDE.
  • The receipt time is recorded by EVIDE, distinct from the declared closure time.
  • Integrity is verified through the SHA-256 fingerprint, without relying on the decision-maker’s own systems.

HSI's added value is not inventing yet another internal procedure. It is enabling the external deposit of a structured declaration, with a receipt time recorded by EVIDE, independently verifiable cryptographic integrity and, upon request, the completion of the evidentiary documentation through the FEDIS (Forensic Evidence Declaration & Integrity Statement): a technical document prepared for digital signature that identifies the deposited records and their cryptographic fingerprints, supporting their independent verification.

For smaller businesses, professional practices and independent professionals, who often lack structured internal documentation systems, this distinction can matter even more.

HSI does not replace governance, compliance procedures or audit systems: it adds a complementary evidentiary layer. EVIDE preserves what was declared; it does not determine whether the decision was correct, lawful or justified, nor does it verify the truth of the declaration.

The most common objections, role by role →

EVIDE Mobile · Android & iPhone
Human Structured Intake, from your smartphone too

With the EVIDE Mobile app you can deposit the declaration at the moment the decision closes: during a meeting, an inspection or a field activity, without waiting to get back to your desk.

Built around six things

Persistent sign-in

Once authenticated, EVIDE Mobile can retain your authenticated session on the device, reducing repeated login steps when you return to the app.

Your previous intakes, directly from mobile

Search, filter, open and review your previous EVIDE intakes directly from your phone, with their evidentiary status visible at a glance.

Human Structured Intake, at hand

Human Structured Intake lets you record a structured, attributable human declaration, decision or intervention directly from the mobile environment, particularly useful during meetings, inspections or other field activities.

🌍 Five languages, from day one

EVIDE Mobile launches in English, Italian, German, French and Spanish. Bringing it to five languages required enormous care: evidentiary terminology cannot simply be translated word for word - identity, status, declarations, interventions and case relationships must remain clear and consistent across the entire mobile experience.

Case Navigator

Case Navigator lets you follow the registered relationships between linked intakes and certifications, node by node, from your phone, one of the more distinctive things EVIDE Mobile does.

Linked responses

Share an HSI record with a person named individually and review the summary of responses. Anyone who receives an invitation opens it by pasting the link and deposits their position directly from the app.

EVIDE Mobile · Demo
Human Structured Intake and Linked responses in the app, screen by screen

Swipe through the screens to see how a structured declaration is completed in the EVIDE Mobile app, how the record is shared for a response and how the invited person responds. Each section of the form matches the fields described in this guide.

The app is available in 5 languages: English, Italian, French, German and Spanish.

From the home screen you open a new intake. The EVIDE functions now also include «Linked responses».
From the home screen you open a new intake. The EVIDE functions now also include «Linked responses».
Further down: profile, public registry, hash calculation and verification, information and contacts.
Further down: profile, public registry, hash calculation and verification, information and contacts.
Among the evidence types, «Structured human action» starts Human Structured Intake.
Among the evidence types, «Structured human action» starts Human Structured Intake.
Operational information: title, description, internal contact, additional notes and business area.
Operational information: title, description, internal contact, additional notes and business area.
Deposit domain: personally or for an organization you belong to; the server checks your current membership. Then case topic, case code and evidence reference.
Deposit domain: personally or for an organization you belong to; the server checks your current membership. Then case topic, case code and evidence reference.
Declared decision: the closure time you declare is distinct from the receipt time recorded by EVIDE. The declared name does not replace the account's DAPI identity.
Declared decision: the closure time you declare is distinct from the receipt time recorded by EVIDE. The declared name does not replace the account's DAPI identity.
Classification and threshold: classification stability, threshold reached, reference and attribution clarity, plus the trace reference. These are all declared values.
Classification and threshold: classification stability, threshold reached, reference and attribution clarity, plus the trace reference. These are all declared values.
Readiness and uncertainties: «Candidate» if no separate verification mechanism assessed the decision. The declarant's own uncertainties are recorded separately.
Readiness and uncertainties: «Candidate» if no separate verification mechanism assessed the decision. The declarant's own uncertainties are recorded separately.
External artifact, parent intake, FEDIS request and submission: EVIDE records the reference and any declared hash, not the document. Once submitted, the request cannot be modified.
External artifact, parent intake, FEDIS request and submission: EVIDE records the reference and any declared hash, not the document. Once submitted, the request cannot be modified.
Linked responses: paste the link of an invitation you received to open it, or review the responses you have deposited.
Linked responses: paste the link of an invitation you received to open it, or review the responses you have deposited.
The depositor of the record invites a person by name: DAPI code, first and last name must match that person's account. The depositor chooses who will see the response and confirms the required declarations.
The depositor of the record invites a person by name: DAPI code, first and last name must match that person's account. The depositor chooses who will see the response and confirms the required declarations.
The invitation is created: copy or share the link right away, because it is not shown again. On its own it gives no access, and it expires after 30 days.
The invitation is created: copy or share the link right away, because it is not shown again. On its own it gives no access, and it expires after 30 days.
The invited person sees the responses already registered on the same representation and states whether the new one replaces or supplements the previous one, which is kept.
The invited person sees the responses already registered on the same representation and states whether the new one replaces or supplements the previous one, which is kept.
Four positions of equal standing. With I DISPUTE (CONTESTO) the reasons are required; a reservation and a declared role are optional. Before you write, the app reminds you which data not to include.
Four positions of equal standing. With I DISPUTE (CONTESTO) the reasons are required; a reservation and a declared role are optional. Before you write, the app reminds you which data not to include.
The detail of the deposited HSI record: EVIDE ID, status, operational information, receipt time and SHA-256.
The detail of the deposited HSI record: EVIDE ID, status, operational information, receipt time and SHA-256.
Further down: the «Create linked intake» button and the record's EAR, with its SHA-256.
Further down: the «Create linked intake» button and the record's EAR, with its SHA-256.
The summary of responses, visible only to the depositor of the record: each person's current position and the number of invitations. These are counts of declarations, not a vote.
The summary of responses, visible only to the depositor of the record: each person's current position and the number of invitations. These are counts of declarations, not a vote.
The list of responses with position, receipt time and visibility; «Share for a response» creates a new invitation.
The list of responses with position, receipt time and visibility; «Share for a response» creates a new invitation.
1 of 18
Visual summary
What EVIDE preserves

How an HSI declaration becomes a preserved record, and which elements it contains. Each field is explained in detail below.

EVIDE Human Structured Intake infographic: the four steps from human decision to preserved record, the elements EVIDE preserves, the signals calculated by the server, and what remains outside EVIDE’s assessment.
New · Visual summary
Linked responses and FEDIS-LINKED

The depositor of an HSI record can invite other people by name to declare their position on that record, on the web and in the EVIDE Mobile app. Each response is a distinct record with its own EAR-LINKED; on request, a forensic expert documents the record and the responses in a signed FEDIS-LINKED.

Diagram of EVIDE Linked responses: A deposits an HSI record and invites B by name; B reads the FAST REVIEW, declares one of the four positions and EVIDE generates the EAR-LINKED; A sees the summary of responses and can request a FEDIS-LINKED; C can deposit an autonomous record of their own.
On request · Signed forensic document
FEDIS: qualified signature and qualified timestamp

On request, a forensic expert examines the HSI record and issues the FEDIS (Forensic Evidence Declaration & Integrity Statement), a document distinct from the deposit.

Qualified electronic signature

The FEDIS is signed by the certifier with a qualified electronic signature.

Qualified timestamp

It receives a qualified electronic time stamp (Article 41 of the eIDAS Regulation) issued by a third-party qualified trust service provider: the document carries a date that can be relied upon against third parties.

Record fingerprints

It reports the SHA-256 fingerprints of the record and of its EAR, which make it possible to verify that the record existed in that form no later than the date of the time stamp.

FEDIS-LINKED

For a record with linked responses, the FEDIS-LINKED also documents the responses, with their fingerprints and the integrity checks performed at generation.

💡 Requesting the FEDIS right after the deposit brings the certain date closer to the moment of the decision.

The time stamp applies to the FEDIS document: it does not date the original decision and does not make the receipt time of the deposit qualified. The FEDIS attests the existence and integrity of the record, not the correctness of the decision or the truth of what was declared.

Who Human Structured Intake is for
Is your role among these?

HSI is for people who, after a site inspection, an audit or a meeting, take or put in writing a decision that may be questioned months later. Here are the roles it is designed for, and what it preserves for each of them.

DPOs and privacy consultants

Deposit the decision to notify or not notify a breach, with the declared grounds and uncertainties. The register stays in the organization: HSI refers to it by its SHA-256.

Health and safety officers and consultants

After a site inspection, deposit the assessment and the measures decided, together with what could not be verified. The employer and worker safety representatives can declare their own position with Linked Responses.

Construction site safety coordinators

Deposit from your phone, on site, the instruction given to contractors. The contractor and the works director can declare whether they agree or dispute it.

Supervisory bodies, statutory auditors and internal audit

Deposit the finding and the recommendation, with the scope of what was verified and what was not. Management can acknowledge or dispute it.

Compliance officers

Preserve case-level compliance decisions outside internal systems, with the declared role and the receipt time recorded by EVIDE.

CISOs, NIS2 and cybersecurity consultants

Deposit the decisions taken during an incident or an assessment, such as isolating, keeping a service running or escalating, with references to tickets and alerts that stay in your systems.

ISO and certification auditors

Deposit the nonconformities found and the closure of the audit. The audited organization can acknowledge or dispute them, and each position remains distinct.

Fire safety professionals and consultants

Deposit the findings of the inspection and the measures decided, with the declared limitations, such as inaccessible areas or missing documentation.

Energy auditors and energy managers

Deposit the assumptions of the energy audit and the data that were not measured directly, so the basis of the conclusions remains clear.

Dangerous goods safety advisers (ADR)

Deposit the assessments made during site visits and the decisions taken after an event in the transport of dangerous goods, with the receipt time.

HACCP and food safety consultants

Deposit the corrective actions decided after an inspection, including the decision to withdraw or not withdraw a product, with the uncertainties of that moment.

Environmental consultants

Deposit the decisions on waste, discharges and emissions taken after an inspection, with references to documents that stay in the organization.

Insurance assessors and loss adjusters

Deposit the assessment made after inspecting the loss. The insured party and the broker can declare their own position on the same record.

Property and condominium managers

Deposit the decision taken urgently or at a meeting. Invited owners can declare whether they agree, dispute or acknowledge it.

Technical directors and project managers

Deposit the handover of a plant, a system or a piece of work. The recipient declares their own position, and reservations remain preserved.

Lawyers and legal advisers

Can advise clients to deposit relevant decisions when they are taken, so that any later dispute rests on what was declared at the time rather than on a later reconstruction.

HR and employment law

Deposit decisions on measures and reports, with the declared role. The people involved can deposit their own account as a distinct record.

AI governance and AI agent oversight

Deposit the human decision to approve, stop or correct an AI system, distinct from the system’s own logs.

In every case, HSI does not replace minutes, signatures, registers or legal obligations. It deposits the declared decision externally, with the receipt time recorded by EVIDE, and does not establish whether the decision was correct.

On this page
Overview
Why Would an Organization Use Human Structured Intake?

Most organizational decisions leave a trace somewhere, an email, a ticket, a comment in a workflow tool, a line in a spreadsheet. That trace is rarely structured, rarely time-anchored in a tamper-evident way, and rarely designed to survive outside the system that created it. When a decision is later questioned, in an audit, a dispute, a regulatory inquiry, or an internal investigation, reconstructing exactly what was decided, by whom, in what declared role, and under what conditions can be slow, incomplete, or impossible.

Human Structured Intake gives a person a structured way to declare a decision at the moment it closes: the type of decision, who declared it and in what role, when it was closed, the applicable classification and threshold context, whether a readiness gate was involved, and any signals that remained unresolved. EVIDE then canonicalizes that declaration, computes a deterministic hash over it, and preserves it as an independently retrievable record.

Human Structured Intake preserves that a decision was declared, not that the decision was correct.
Preservation of a declaration is not independent validation of the truth of that declaration.

This distinction runs through every field documented on this page. Where a value uses a word like «verified,» that word describes what a person or an upstream mechanism declared, not an assessment performed by EVIDE itself, unless stated otherwise for that specific field.

Before You Compare
Common Objections, by Role

People evaluating Human Structured Intake usually compare it with a tool they already use: a register, a logging system, an approval workflow, a set of minutes. Below are the objections that come up most often, role by role, each with its answer and the boundary of what EVIDE claims.

None of these tools is replaced. HSI adds a different layer: the external deposit of the declaration about a single decision, with the receipt time recorded by EVIDE and integrity verifiable through SHA-256.

Seven cases, seven videos. Each enterprise use case on this page is also illustrated in a short video.

Watch the seven cases on LinkedIn ↗
DPOs and privacy
“I already keep a register of breaches and evidence.”

The register is the right foundation and HSI does not replace it, just as it does not replace the documentation duties set by the GDPR. The register, however, is kept and updated inside the organization. HSI deposits externally the declaration about a single decision, for example, to notify or not to notify, with the receipt time recorded by EVIDE, distinct from the declared closure time (Decision Closure). The deposit can refer to the register entry with its declared SHA-256, without the register ever leaving the organization (External Evidence References).

Boundary of the EVIDE claim: EVIDE does not assess whether the decision to notify or not to notify was correct, and does not attest that any obligation was fulfilled.
NIS2, CISOs and SOC
“We already have logs, a SIEM and ticketing.”

Logs record what systems did; HSI preserves the declared decision, keep a service running, isolate it, escalate, with the declared decision-maker and role, kept distinct from the verified DAPI identity of the person depositing the record, and the declared basis. Logs and tickets stay where they are: the HSI record refers to them through the ticket or alert ID (Trace Reference), without transferring technical data to EVIDE. What the declarant still considers uncertain is recorded as a declared uncertainty; unresolved signals belong only to a separate verification mechanism.

Boundary of the EVIDE claim: EVIDE does not determine whether the system was secure or whether the decision was the correct one, and does not establish that the declared decision-maker actually exercised that authority.
Supervisory bodies, statutory auditors, internal audit
“We already have minutes and reporting flows.”

Minutes document the meetings of the oversight body and are often drafted or approved at a later time. HSI concerns the single operational decision at the moment it closes, for example, an exception authorized by a business function, with the declared role, the reference procedure or threshold (Threshold Reference) and the two distinct times of closure and receipt. An oversight body can ask for relevant decisions to be deposited, and examine them later without depending on the systems of the function that made them.

Boundary of the EVIDE claim: HSI does not replace reporting flows to oversight bodies, minutes or compliance programs, and does not attest the effectiveness of any control.
Compliance Officers
“Exceptions already go through an approval workflow.”

The workflow records that the approval happened. HSI preserves the declared context of that approval: the reference policy and how clearly its ownership is attributable (Threshold Attribution), whether a separate mechanism assessed the conditions (Boundary Readiness) and what remained uncertain. And it preserves it externally, with integrity verifiable through SHA-256.

Boundary of the EVIDE claim: EVIDE does not determine whether the exception was substantively or legally justified.
Lawyers and litigation
“A party’s own declaration carries little weight in court.”

That is correct: HSI preserves a declaration, it does not make it true. What it adds is different: it makes it possible to show that the declaration existed in that form at the receipt time recorded by EVIDE, and that it was not reconstructed after that moment. Upon request, the FEDIS identifies the deposited records and their cryptographic fingerprints, in support of their independent verification. The weight given to the declaration remains a judgment for whoever examines it.

Boundary of the EVIDE claim: EVIDE does not qualify the evidentiary value of the record in any proceeding, and does not attest the truth of what was declared.
Lawyers, compliance and oversight
“So it is a form of supervision, or monitoring of the phases?”

No. HSI is a tool for the external evidentiary preservation of declarations about specific decision moments. EVIDE does not follow the process in real time and does not verify that the declared activities were actually carried out. For each deposit it records the moment of receipt, distinct from the declared decision time, and preserves its cryptographic integrity. Later decisions are documented with new linked deposits, without modifying earlier declarations (Human Judgment Evolution): the result is a sequence of preserved declarations that can be examined later.

Boundary of the EVIDE claim: EVIDE does not certify the merits of the decisions or the completeness of the sequence: the last observed deposit is not a verified closure, and EVIDE does not reconstruct why an assessment changed unless the reason was declared.
HR and employment law
“The final decision is already recorded in the HR system.”

The system records the outcome. HSI makes it possible to keep what the automated system recommended separate from the declared human decision, with the declared decision-maker and role, kept distinct from the verified DAPI identity of the person depositing the record, the declared closure time and the elements declared as uncertain: a distinction that is hard to reconstruct afterwards from logs alone. The record can refer to the case file without containing unnecessary personal data.

Boundary of the EVIDE claim: EVIDE does not certify that the human review was adequate, free of bias or lawful, does not establish who actually decided, and does not attest conformity with the AI Act.
Fraud, AML and risk
“The fraud system already tracks the override.”

The system tracks that the override happened and under which account. HSI preserves, outside that system, the declared basis of the override, the declared status of the risk threshold and what remained uncertain. It is not meant for every transaction: it is meant for the overrides you will want to be able to reconstruct.

Boundary of the EVIDE claim: EVIDE does not determine whether the transaction was, in fact, fraudulent.
Health & safety and operational safety
“We already have restart checklists and a maintenance log.”

The checklist documents the checks performed. HSI preserves the declared restart authorization, with the declared decision-maker and role, kept distinct from the verified DAPI identity of the person depositing the record, the declared diagnostic check and its scope (Gate Identifier, Gate Scope), and what remained uncertain. The checklist can be referenced with its declared SHA-256, without being uploaded.

Boundary of the EVIDE claim: EVIDE does not verify the diagnostic result or that the machine was safe to restart, and does not establish who actually authorized the restart.
AI governance and AI agents
“The platform already records human approval.”

The platform records the approval within itself. HSI preserves the declared authorization externally: who is declared as authorizing and in what role, kept distinct from the verified DAPI identity of the person depositing the record, the declared conditions and what remained uncertain. The record remains available even if the platform changes or its logs are rotated.

Boundary of the EVIDE claim: EVIDE does not verify that the agent then acted within the authorized scope, does not establish who actually authorized, and does not authorize or execute anything.
Insurers, experts and technical consultants
“How do I know they did not deposit afterwards, already knowing how things turned out?”

No one can rule that out, which is exactly why HSI distinguishes two times. The closure time is declared by the person recording; the receipt time is recorded by EVIDE and cannot be chosen by the depositor. A deposit made after the event shows up as such, and a long gap between declared closure and receipt is immediately visible to whoever examines the record (Decision Closure).

Boundary of the EVIDE claim: EVIDE does not verify the declared closure time: it independently preserves only the moment the record was received.
All roles - time
“During an incident there is no time to fill in a form.”

The decision’s closure time is declared separately: the deposit can happen later, once things have stabilized, without confusing the two moments. With the EVIDE Mobile app, it can also be deposited in the field, during a meeting or a site visit.

Boundary of the EVIDE claim: The longer the gap between closure and deposit, the more visible that gap remains in the record: EVIDE neither hides nor justifies it.
All roles - confidentiality
“I cannot send confidential documents to an external party.”

With an external reference, the document is not sent: you declare a reference and, if you wish, its SHA-256 (External Evidence References). EVIDE receives the content of the declaration, and the depositor chooses what to write, using references instead of data where needed.

Boundary of the EVIDE claim: A declared SHA-256 digest does not establish authorship, provenance or truth of the document. In an HSI deposit with an external reference, EVIDE does not receive the document and therefore cannot compare it with the declared digest.
See It First
What You Actually Record

A Human Structured Intake turns a human decision into a structured evidentiary object. Here is exactly what that means, in three steps.

What You Declare Declared by the user

Context

Title, Business area involved, Description, Internal contact, Case reference, Evidence reference, Additional notes.

Decision

Decision type, Decision closure date/time (entered in local time and converted to UTC before submission).

Human Authority

Role of the person who made the decision, Name of the person who made the decision, Reference on the decision-maker’s authority (optional).

Classification and Threshold

Classification stability (optional), Threshold reached (optional), Threshold reference, Threshold attribution clarity (optional).

Trace and Readiness

Trace reference (optional), Decision readiness, Identifier and scope of the separate verification mechanism, Signals not resolved by the verification mechanism, Declared uncertainties (optional).

External Evidence

Document / external artifact - Artifact type, Reference, Declared origin, Relationship to the decision, Description, Retention status, SHA-256 of the document, Who computed the hash, Hash scope.

↓

What EVIDE Preserves

Preserved evidentiary object Preserved by EVIDE
Server-generated Intake Timestamp Server-recorded
SHA-256 integrity hash Server-computed
DAPI identity reference Preserved reference

DAPI identity reference: reference to the independently verified identity associated with the intake.

Preserved as received. Each deposited state remains a separate evidentiary object, later states do not rewrite previously deposited states.

↓

What EVIDE Derives

Forensic Cross-Check Server-derived

A server-computed signal describing how consistent the declared classification is with what was observable at the evidentiary boundary.

Learn more →

Decision Wave Compression Server-derived

A server-computed signal describing the observational quality of the conditions under which this single closure was stabilized, not a measure of decision volume or throughput.

Learn more →

Formal Accountability Collapse Server-derived

A server-computed signal describing whether declared accountability remains structurally supported, based on this closure’s authority, threshold attribution, and continuity state.

Learn more →

Derived signals are computed separately from the declared evidentiary object. They do not rewrite the original intake.

Before the Field Reference
Enterprise Use Cases

The seven scenarios below are illustrative examples of how different business functions might use Human Structured Intake. Each shows the kind of decision involved, information that could reasonably be declared, the regulatory context in which that decision may become relevant and, just as importantly, the boundary of what EVIDE’s preservation of that record does and does not establish.

Regulatory references. Each case indicates the rules that may make the documented decision relevant: the AI Act, Italian law and, where pertinent, other frameworks (NIS2, GDPR, machinery safety). The reference describes the context; it does not mean that an HSI record satisfies those obligations, verifies compliance with them or attests conformity. Many AI Act obligations for high-risk systems apply from 2 December 2027 or from 2 August 2028: dates, conditions and exceptions are set out on the dedicated page.

EVIDE & AI Act - regulatory framework ↗

Seven cases, seven videos. Each enterprise use case on this page is also illustrated in a short video.

Watch the seven cases on LinkedIn ↗
Compliance
Approval of a compliance exception

Event / ContextA Compliance Officer is asked to temporarily authorize an exception to a procedure that would normally be blocked, under time pressure and with a documented business justification.

Human DecisionThe officer approves a temporary, scoped exception, subject to specific conditions and a defined review point.

Information That Could Be Declared

  • Decision type - e.g. «Compliance exception approval»
  • Authority role - e.g. «Compliance Officer»
  • Classification status of how settled the categorization is
  • Threshold status and reference - whether an internal policy threshold was met
  • Threshold attribution - how clearly the threshold ownership is attributable
  • Boundary readiness - whether a readiness gate confirmed the conditions, or the officer is only declaring readiness
  • Trace reference - a reference to the internal ticket or case file

Reconstructive ValueA later reviewer, auditor or regulator can reconstruct that the exception was declared, by whom, in what role, under what declared threshold and readiness conditions, without relying on the officer’s memory or on a system log that may since have been rotated.

Regulatory referenceThere is no specific obligation of external recording. The typical context is a system of internal controls, for example an organization and management model under Italian Legislative Decree (D.Lgs.) 231/2001 (Art. 6), which presupposes documented protocols and oversight: an authorized exception is precisely what one is later asked to reconstruct. HSI does not assess the adequacy of the model or the effectiveness of the controls.
Boundary of the EVIDE claim: EVIDE preserves that this decision, with this declared context, was recorded at this time. It does not determine whether the exception was substantively or legally justified.
Cybersecurity / SOC
Authorization after a security alert

Event / ContextA Security Operations Center detects anomalous behavior. A human responder reviews the available telemetry and must decide whether to allow continued operation, block, isolate or escalate.

Human DecisionThe responder authorizes continued operation while the investigation proceeds, rather than an immediate isolation.

Information That Could Be Declared

  • Decision type - e.g. «Authorization to continue pending investigation»
  • Classification status - often provisional, since the investigation is not yet closed
  • Boundary readiness - candidate if only the responder carried out the assessment; verified_partial only if a separate verification mechanism (for example an independent tool or team) assessed the conditions with incomplete visibility, stating its identifier and scope
  • Unresolved signals - only with verified_partial or unverifiable: what the separate verification mechanism could not resolve, e.g. «Origin of two API requests not yet attributed»
  • Declared uncertainties (declared_uncertainties), with any readiness value, including candidate: what the responder personally still considers uncertain, e.g. «Possible EDR sensor false positive»
  • Trace reference - reference to the SOC case or alert ID

Reconstructive ValueIf the incident later escalates, the record preserves what the responder declared as known, verified or unresolved, with the closure time the responder declared and, separately, the time at which EVIDE received the record. This helps distinguish hindsight from what had been declared at the time; it does not prove that the declared information was complete or accurate, nor that the decision was made exactly at the declared time.

If an independent verification gate examined only part of the conditions, verified_partial with the unresolved signals written out in full is more honest than a premature verified. If no separate mechanism was involved, the correct value is candidate: a personal assessment should not be presented as independent verification. With candidate, whatever remains uncertain is recorded as a declared uncertainty, not as an unresolved signal: signals belong to a separate mechanism and, with candidate, the request would be rejected. In both cases this is a declaration: EVIDE does not verify that the gate exists or is independent.
Regulatory referenceFor essential and important entities within the scope of NIS2 (Directive (EU) 2022/2555, transposed in Italy by Legislative Decree (D.Lgs.) 138/2024), in the event of a significant incident Art. 23 of the Directive requires an early warning to the CSIRT or the competent authority within 24 hours and a notification within 72 hours of the entity becoming aware of it. What was known and when the decision was taken therefore become relevant elements. HSI records the declared decision; it does not make or replace the notification.
Boundary of the EVIDE claim: EVIDE preserves that the responder declared continued operation under these declared conditions. It does not determine whether the system was actually secure, or whether the decision was the correct security judgment.
Human Resources
Human review of an automated recommendation

Event / ContextAn AI-assisted system produces a recommendation about a candidate or employee. A human reviewer examines that recommendation and makes the final decision.

Human DecisionThe reviewer accepts, modifies or overrides the automated recommendation.

Information That Could Be Declared

  • Who decided, and in what role - e.g. «HR Director»
  • Declared moment of decision closure
  • Any threshold used in the review process
  • Reference to the internal HR procedure that governed the review
  • Any elements that remained contested or uncertain at closure, as declared uncertainties

Reconstructive ValueThe record helps preserve a structural separation between the recommendation attributed to the automated system and the declared human decision, a distinction that is often difficult to reconstruct after the fact from system logs alone.

Regulatory referenceUnder the AI Act, AI systems used for recruitment, promotion, termination of employment or task allocation are, as a rule, high-risk under the conditions of Article 6 and Annex III, point 4, with obligations applying from 2 December 2027: human oversight (Arts. 14 and 26(2)), informing workers’ representatives and the affected workers before use (Art. 26(7)) and, where the conditions are met, the right to explanation (Art. 86). In Italy, Article 11 of Italian Law (L.) 132/2025 requires the employer to inform the worker of the use of AI, in the cases and in the manner set out in Article 1-bis of Italian Legislative Decree (D.Lgs.) 152/1997.
Boundary of the EVIDE claim: EVIDE preserves that a human decision was declared as distinct from an automated recommendation. It does not certify that the human review was substantively adequate, free from bias or compliant with the law.
Fraud Prevention
Manual release of a transaction

Event / ContextA fraud prevention system blocks a transaction as high risk. A fraud analyst reviews the case and must decide whether to release it, keep it blocked or escalate it.

Human DecisionThe analyst releases the transaction after review, judging the risk signal to be a false positive.

Information That Could Be Declared

  • Decision type - e.g. «Manual transaction release»
  • Authority role - e.g. «Fraud Analyst»
  • Threshold status - whether the fraud-risk threshold that triggered the block is declared as met, not met or unclear on review
  • Trace reference - reference to the case file or transaction ID

Reconstructive ValueThe record preserves the declared context of the human override, who authorized the release, when and on what declared basis, regardless of whether the transaction later turns out to have been legitimate or not.

Regulatory referenceThe AI Act expressly excludes from high risk the systems used to detect financial fraud (Annex III, point 5(b)): this case should not be presented as an AI Act obligation. Other rules may apply, for example Art. 22 GDPR where a decision based solely on automated processing produces legal or similarly significant effects on the person, in addition to sector-specific rules.
Boundary of the EVIDE claim: EVIDE preserves that the override was declared under this declared context. It does not determine whether the transaction was, in fact, fraudulent.
Industrial / Manufacturing
Authorization to restart a production line

Event / ContextA production line stops automatically after an anomaly is detected. A technical manager reviews the relevant conditions and must decide whether to authorize a restart.

Human DecisionThe manager authorizes the restart, having reviewed the available diagnostic information.

Information That Could Be Declared

  • Threshold reference - e.g. the technical procedure or operational limit that governs restart conditions
  • Readiness gate identifier - e.g. the diagnostic check performed before authorizing the restart
  • Readiness gate scope reference - e.g. which machine or line the check covered
  • Signals not resolved by the diagnostic check, with verified_partial - e.g. «Sensor 4 reading not yet cross-validated»; if only the manager carries out the assessment (candidate), the same uncertainty is declared as a declared uncertainty

Reconstructive ValueIf a related failure recurs later, the record preserves which diagnostic check was declared as performed, with what declared scope, in the declaration authorizing the restart.

If the diagnostic check is a mechanism separate from the decision-maker and some condition remains uncertain, this is the case for verified_partial, with the identifier and scope of the check and the unresolved signals, rather than a full verified. If the assessment is the manager’s alone, the correct value is candidate.
Regulatory referenceFollowing the 2026 amendments to the AI Act (Regulation (EU) 2026/1744), an AI system that would be high-risk as a safety component of a machine is no longer directly subject to the AI Act’s high-risk requirements: the AI-specific requirements will come through acts adopted under the Machinery Regulation (EU) 2023/1230, which applies from 20 January 2027 to products within its scope. The other AI Act rules remain applicable, such as the prohibitions of Art. 5 and the transparency obligations of Art. 50, as do the Annex III rules if the system’s purpose falls within it; occupational safety obligations also remain, in Italy Legislative Decree (D.Lgs.) 81/2008.
Boundary of the EVIDE claim: EVIDE preserves that a restart authorization was declared under this declared diagnostic context. It does not verify the diagnostic result itself, nor does it guarantee that the line was, in fact, safe to restart.
AI Governance
Human authorization of an AI agent action

Event / ContextAn AI agent requests to perform a sensitive action. Before execution, a human authority must approve, reject, condition or escalate the request.

Human DecisionThe human authority approves the requested action, subject to declared conditions.

Information That Could Be Declared

  • Decision type - e.g. «Authorization of agent-requested action»
  • Authority role of the person authorizing
  • Boundary readiness of the authorization itself
  • Trace reference - reference to the agent request log or governance ticket

Reconstructive ValueHuman Structured Intake records the human decision to authorize. It is deliberately not the same function as declaring the operational perimeter within which the agent was authorized (that is the separate declarations extension documented in the JSON Schema Reference), and it is not an automatic execution-authorization mechanism.

Regulatory referenceIf the agent is part of a high-risk system, human oversight is required by Arts. 14 and 26(2) of the AI Act (for Annex III, from 2 December 2027). In Italy, in an action for damages caused by an AI system, Art. 17 of Legislative Decree (D.Lgs.) 160/2026 allows the court to order the disclosure of information on human oversight, among other elements.
Boundary of the EVIDE claim: EVIDE preserves that a human declared this authorization decision, under these declared conditions. It does not verify that the agent subsequently acted within the authorized scope, and does not itself authorize or execute anything.
Incident Response
Decision during an active incident

Event / ContextDuring a cybersecurity incident, a responder must choose between competing courses of action under time pressure, for example isolating a server versus keeping a service operational despite an indicator of compromise.

Human DecisionThe responder declares a chosen course of action, together with the information the responder declares available at that moment.

Information That Could Be Declared

  • Decision type - e.g. «Incident containment decision»
  • Classification status, often provisional during an active incident
  • Boundary readiness; unresolved signals only if a separate verification mechanism carried out the assessment with incomplete visibility (verified_partial or unverifiable)
  • Uncertainties declared by the responder about what remained uncertain at the moment of the decision, with any readiness value
  • Trace reference - reference to the incident ticket

Reconstructive ValueIncident timelines are frequently reconstructed after the fact under scrutiny. A structured, time-anchored declaration reduces reliance on reconstructing intent from memory or from logs that were not designed for evidentiary use.

Regulatory referenceDepending on the case and where the conditions are met: for NIS2 entities, notification of significant incidents (Art. 23 of the Directive: 24 and 72 hours); for a personal data breach, notification to the Garante (the Italian data protection supervisory authority) within 72 hours, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons (Art. 33 GDPR); for high-risk AI systems, from the dates of application, reporting of serious incidents by the provider (Art. 73 AI Act), whom the deployer must inform (Art. 26(5)). The HSI record documents the declared decision; it does not replace any of these notifications.
Boundary of the EVIDE claim: EVIDE preserves what was declared as available, verified or unresolved at the moment of the declared decision. It does not determine, after the fact, whether the decision taken was objectively the best course of action.
AI Act - High-Risk Areas
Sector Use Cases
In these cases, when no separate mechanism has assessed the conditions, readiness is candidate and whatever the person still considers uncertain is declared as a declared uncertainty. Unresolved signals belong only to a separate verification mechanism (verified_partial or unverifiable). Neither is verified by EVIDE.

These cases concern areas in which the AI Act, or Italian law, gives specific weight to the human decision taken with the support of an AI system. In each of them, the question that comes afterwards is the same: what did the system produce, what did the person decide, and what had been declared as known, verified or unresolved at that moment.

An HSI record documents the decision as declared. It does not prove that human oversight was effective, it does not classify the system as high-risk and it does not attest conformity with the AI Act. Whether a system actually falls within one of these areas depends on its intended purpose and on Art. 6(3) of the AI Act, and must be assessed case by case.

Credit and Insurance
Human review of a creditworthiness score or an insurance premium

Event / ContextAn AI system computes a credit score, or a risk assessment and pricing for life or health insurance. An operator examines the outcome before the decision.

Human DecisionThe operator confirms, modifies or rejects the outcome proposed by the system.

Information That Could Be Declared

  • Decision type - e.g. «Outcome of a financing application»
  • Authority role - e.g. «Credit Officer»
  • Threshold reference and status - the credit policy applied and whether it is declared as met
  • External reference to the score produced by the system, with its declared SHA-256, without handing the document over to EVIDE
  • Boundary readiness - candidate if no separate mechanism has assessed the conditions
  • Declared uncertainties (declared_uncertainties), e.g. «Declared income not yet documented»
  • Trace reference - application number
Regulatory referenceHigh-risk systems under Annex III, points 5(b) and 5(c) of the AI Act (excluding those used to detect financial fraud). From 2 December 2027: human oversight (Arts. 14 and 26(2)), fundamental rights impact assessment before first use (Art. 27), information to the affected persons (Art. 26(11)) and, where the conditions are met, the right to explanation (Art. 86).

Reconstructive ValueThe record keeps the system’s outcome and the operator’s decision distinct, with the context declared at the moment of closure: exactly what is needed when one has to explain what role the system played in the decision.

Boundary of the EVIDE claim: EVIDE preserves that the decision was declared, distinct from the system’s output. It does not assess creditworthiness, does not produce the explanation and does not judge its adequacy.
Biometrics
Dual human verification of a biometric match

Event / ContextA remote biometric identification system flags a match. Before any action, the match must be separately verified and confirmed by at least two persons.

Human DecisionEach verifier confirms, or does not confirm, the match.

Information That Could Be Declared

  • Two distinct HSI records, one for each verifier, linked in sequence
  • Declared role of each verifier
  • Declared closure time of each verification
  • Declared outcome of the verification
  • Declared uncertainties (declared_uncertainties), e.g. «Image quality insufficient for a full comparison»
  • Trace reference - event identifier
Regulatory referenceAnnex III, point 1, of the AI Act. Art. 14(5) requires that no action or decision be taken on the basis of the identification unless it has been separately verified and confirmed by at least two natural persons, subject to the exceptions provided for in the same article; from 2 December 2027. Certain uses of biometrics are prohibited by Art. 5.

Reconstructive ValueTwo separate records, each with its own Intake Timestamp and the verified DAPI identity of the session recording it, show that two confirmations were declared, by which session each was recorded and in what order EVIDE received them. Two declarations, two DAPI identities and two timestamps do not in themselves prove that two genuinely separate and independent verifications took place, nor that they took place before the action: the DAPI identity indicates who entered the record, the closure time is declared and the Intake Timestamp indicates only when EVIDE received each record.

Boundary of the EVIDE claim: EVIDE preserves the two declarations. It does not establish that the verifications were actually independent or correct, nor that the use of the biometric system was lawful.
Education and Training
Human review of an AI-assisted assessment

Event / ContextAn AI system grades a test, proposes an admission outcome or flags anomalous behavior during an exam. A teacher or a board examines the result.

Human DecisionThe teacher or the board confirms, modifies or annuls the proposed outcome.

Information That Could Be Declared

  • Decision type - e.g. «Review of a test outcome»
  • Authority role - e.g. «Chair of the examination board»
  • Reference to the examination rules or the assessment criteria applied
  • External reference to the outcome produced by the system
  • Boundary readiness - candidate if no separate mechanism has assessed the conditions
  • Declared uncertainties (declared_uncertainties), e.g. «Flag of anomalous behavior not confirmed»
Regulatory referenceAnnex III, point 3, of the AI Act (admission, evaluation of learning outcomes, level of education, monitoring during tests). From 2 December 2027: human oversight (Arts. 14 and 26(2)), information to the affected persons (Art. 26(11)) and, where the conditions are met, the right to explanation (Art. 86).

Reconstructive ValueIf the outcome is challenged, the record shows what the system proposed according to the declaration, what the person declared to have decided and which elements were declared open at the moment of the declared closure.

Boundary of the EVIDE claim: EVIDE preserves the declared decision. It does not assess the test, nor the fairness or correctness of the outcome.
Public Administration
Administrative decision on a public benefit adopted with the support of AI

Event / ContextAn AI system supports the assessment of eligibility for a benefit or an essential public service. The responsible official examines the file.

Human DecisionThe official adopts the administrative decision, either confirming or departing from the system’s indication.

Information That Could Be Declared

  • Decision type - e.g. «Decision granting access to the benefit»
  • Authority role - e.g. «Official responsible for the procedure»
  • Reference to the law or regulation applied
  • External reference to the system’s output
  • Boundary readiness - candidate if no separate mechanism has assessed the conditions
  • Declared uncertainties (declared_uncertainties), e.g. «Income documentation pending verification»
  • Trace reference - procedure number
Regulatory referenceAnnex III, point 5(a), of the AI Act. For bodies governed by public law: fundamental rights impact assessment (Art. 27) and the right to explanation under the conditions of Art. 86; systems already in use that are intended to be used by public authorities must be brought into compliance by 2 August 2030 (Art. 111(2)). In Italy, Italian Law (L.) 132/2025 (Art. 14) establishes that AI is a support tool, that the person remains solely responsible for administrative decisions and that the traceability of its use must be ensured.

Reconstructive ValueThe record documents the official’s decision as an act distinct from the system’s output, with the context declared at the moment of closure.

Boundary of the EVIDE claim: EVIDE preserves the official’s declaration. It does not assess the legitimacy of the administrative decision and does not replace the administration’s obligations to state reasons or to ensure traceability.
Emergency Calls
Confirmation of the priority of an emergency call

Event / ContextAn AI system classifies emergency calls and proposes a response priority or the dispatch of a unit. The control-room operator assesses the proposal.

Human DecisionThe operator confirms or modifies the priority and the dispatch.

Information That Could Be Declared

  • Decision type - e.g. «Confirmation of response priority»
  • Authority role - e.g. «Control-room operator»
  • Declared closure time, distinct from the Intake Timestamp: in an emergency the record is often entered afterwards
  • External reference to the classification proposed by the system
  • Boundary readiness - candidate if no separate mechanism has assessed the conditions
  • Declared uncertainties (declared_uncertainties), e.g. «Caller’s location not confirmed»
Regulatory referenceAnnex III, point 5(d), of the AI Act (evaluation and classification of emergency calls, dispatch of emergency services, triage). From 2 December 2027: human oversight (Arts. 14 and 26(2)); for public bodies, also the impact assessment (Art. 27).

Reconstructive ValueDistinguishing the declared moment of the decision from the moment of recording makes it possible to reconstruct the sequence even when the record was entered at the end of a shift.

Boundary of the EVIDE claim: EVIDE preserves the declared decision. It does not assess whether the priority was the correct one and does not intervene in the management of the emergency.
Healthcare
Clinical decision supported by an AI diagnostic system

Event / ContextAI software that is a medical device proposes a diagnostic hypothesis or a reporting priority. The physician examines the proposal.

Human DecisionThe physician confirms, modifies or discards the system’s indication.

Information That Could Be Declared

  • Decision type - e.g. «Confirmation of the diagnostic hypothesis»
  • Authority role - e.g. «Radiologist»
  • Reference to the clinical protocol applied
  • External reference to the system’s output, with pseudonymized references: the record must not contain unnecessary health data
  • Boundary readiness - candidate if no separate mechanism has assessed the conditions
  • Declared uncertainties (declared_uncertainties), e.g. «Previous comparison exam not available»
Regulatory referenceIn Italy, Italian Law (L.) 132/2025 (Art. 7) establishes that, in healthcare, AI systems are a support in the processes of prevention, diagnosis, treatment and therapeutic choice, that the decision always rests with the medical professionals and that the patient has the right to be informed of the use of such technologies. Under the AI Act, an AI system that is a medical device, or a safety component of one, within the meaning of Regulation (EU) 2017/745 (Annex I, Section A) is high-risk only if the device is subject to conformity assessment by a notified body; in that case the obligations apply from 2 August 2028 (Art. 6(1)).

Reconstructive ValueThe record shows that the clinical decision was declared by the physician as an act distinct from the system’s indication, with what the physician declared as known and as still open at the moment of the declared closure.

Boundary of the EVIDE claim: EVIDE preserves the physician’s declaration. It does not assess clinical correctness, does not validate the device and does not replace the medical record.
New · Linked responses
Linked responses: different perspectives, independently preserved

A decision rarely concerns one person only. Whoever took it needs to know, and often to be able to show later, what the others thought of it: the colleague who was present, the client, the supplier, the person called into question, the advisor. Today those positions stay scattered across emails, messages and conversations, written at different times and about different versions of the facts.

With Linked responses, the depositor of an HSI record invites a person by name to declare their position on that record. The person reads a representation of the record frozen at the time of the invitation, chooses one of four positions, can give reasons, and deposits the response with their own EVIDE account. EVIDE records the receipt time and generates an EAR-LINKED document for each response. At the request of the depositor of the record, a forensic expert can document the record and the responses in a signed FEDIS-LINKED.

Each response is the position declared by an identified person, preserved as an autonomous record next to the record it refers to, which stays intact.
EVIDE does not build a single version of the facts: it preserves the versions of the parties, with their provenance, so that they can be examined and compared over time.

The value does not lie in proving anyone right. It lies in the fact that each position remains a distinct record, attributed to the account that deposited it, with its own time and fingerprint, and that no deposit modifies or deletes anyone else's.

Linked responses
How they work, step by step
  1. A deposits an HSI record. It is the structured record described on this page, with its EAR, its SHA-256 fingerprint and the receipt time recorded by EVIDE. Only HSI records can be shared, and only by the person who deposited them; for an organization record, only while that person is a member.
  2. A invites a person by name. A enters the recipient's DAPI number, first name and last name; the recipient may also belong to another organization. A chooses who will be able to see the response and confirms two declarations about their authorization to share. EVIDE preserves these declarations but does not certify that the authorization is actually valid. The link is shown only once, is valid for 30 days and is personal: on its own it gives no access.
  3. B opens the invitation with their own EVIDE account, on the web or in the EVIDE Mobile app by pasting the link. The account's DAPI, first and last name must match those entered by A. Before examining the record, B reads a notice and declares having taken note of it, which is not consent.
  4. B reads the FAST REVIEW. It is a representation of the record generated by the platform from a fixed template, without AI, frozen at the time of the invitation with its identifier and fingerprint. B does not receive the complete record or the external documents the record cites.
  5. B declares their position, one of the four described below. B can add reasons, required when disputing, a reservation and their own role, which remains declared and unverified. Before the free-text fields, the app and the web remind B not to enter health data, unnecessary data about other people or irrelevant confidential information.
  6. B confirms the summary and deposits. EVIDE records the receipt time and generates the response's EAR-LINKED. The response is B's record: A cannot modify or delete it. B can later deposit a new response that replaces the previous position or supplements it; the previous response is kept.
  7. A sees the responses and the summary. In the record's «Linked responses» box, on the web and in the app, A sees the responses and a summary with each person's current position and the number of invitations, recipients and responses. The summary is visible only to A.
  8. A can request a FEDIS-LINKED, the professional document described below.
PositionWhat the respondent declares
I AGREE (CONCORDO)Agreement with what the representation reports. Reasons and reservation are optional.
I ACKNOWLEDGE WITHOUT EXPRESSING AGREEMENT (PRENDO ATTO SENZA ESPRIMERE ACCORDO)Having taken note of what is reported, without stating agreement. It is the typical position of someone receiving a handover or a piece of information.
I DISPUTE (CONTESTO)Disagreement. Reasons are required; a reservation cannot be combined with this position.
I AM NOT IN A POSITION TO ASSESS (NON SONO IN CONDIZIONE DI VALUTARE)Not having the elements to express a view. It is neither agreement nor dispute.

The four positions carry equal weight and are fixed Italian labels: in the other languages they appear as a translation followed by the original in brackets, because the declared and preserved value is the original.

Who sees the response

B always sees their own responses, in the «My responses» section. A sees them as long as A has access to the record. For an organization record, A can choose at the time of the invitation that the response is also visible to the current members of the organization; former members do not see it. B reads this indication before depositing, and the visibility stays the same for all later responses of the same person on the same representation.

A can revoke an invitation; for organization records, revocation may follow a procedure with a request and a decision by a different owner or admin. Revocations, suspensions and expiry prevent new responses, but do not modify or delete those already deposited.

The summary shows individual positions. Each number corresponds to declarations by identified people, each attributed to whoever made it: it is a picture of the positions, not a vote or a measure of consensus. EVIDE records the creation of invitations, not their delivery: an invitation without a response does not say whether it was received or read.
The professional document
FEDIS-LINKED

The FEDIS-LINKED is the FEDIS of an HSI record that documents, in addition to the record, the includable linked responses. It is requested by the depositor of the record, from the record's FEDIS button on the web, with the same procedure and the same financial terms as any FEDIS: the certifier's quote, express acceptance, any FEDIS packages. Nobody else can request it on that record, not even the other members of the organization.

On request, the platform forms from its own archive a snapshot of the relevant records, identified by its SHA-256 fingerprint. For each included response, the document reports the respondent's name and DAPI number, any declared role, the position, the verbatim reasons and reservation, the deposit date, the visibility indicated, the identifiers and fingerprints of the response and of its EAR-LINKED, and descriptive counts of invitations and responses. For non-includable responses and invitations without a deposit it reports only counts, without names or content. At generation, the platform recomputes the fingerprints of the records still available: if one does not match, the document is not generated.

A forensic expert examines the document and signs it. Later requests form a series: each FEDIS-LINKED documents the records present at the date of its own snapshot, cites the previous emissions and does not modify, replace or withdraw any document already issued. Only responses deposited after the respondent was shown the FEDIS-LINKED notice are includable: the respondent knows in advance that their position may end up in a document handed to third parties, even if on the platform the response is visible only to A.

The complete rules for Linked responses and FEDIS-LINKED are in Sections 7.7 and 7.8 of the Service Conditions.

Read the Service Conditions ↗
Linked responses
Linked responses use cases

In each of these cases the HSI record remains the declaration of its depositor; the responses add the positions declared by other people, each with its own provenance. All recipients need an EVIDE account with a DAPI number.

Workplace incident: three versions of the facts
A department head attributes an operational problem to a colleague; another colleague agrees; the person called into question does not.

The recordA, the department head, deposits an HSI record: decision type, for example «Reconstruction of the line 3 stoppage», declared role, closure time, a reference to the incident ticket and, as a declared uncertainty, what A could not establish. In A's reconstruction the cause is an operation carried out by C.

The responsesA invites B, a colleague present at the time of the stoppage, who declares I AGREE (CONCORDO). A can also invite C: in that case C can declare I DISPUTE (CONTESTO) with their own reasons, which remain preserved alongside the other positions.

C's autonomous recordWhether invited or not, C can deposit their own HSI record with their version of the facts, cite the EVIDE ID of A's record as a declared reference, if C knows it, and in turn invite other people. C is not forced to defend themselves inside A's account, and A's record does not become the official version just because it was registered first.

Reconstructive ValueThe organization does not have to decide straight away who is right. It can reconstruct what A declared and when, what B declared, what C declared independently, which evidence was cited and which was declared missing. B's agreement does not in itself prove C's responsibility. At A's request, the FEDIS-LINKED can document A's record with the includable responses; C can request a FEDIS on their own record.

Confidentiality. A reconstruction that attributes responsibility contains personal data. It is advisable to choose the «Only me» visibility when the organization has not decided who may see these responses, and to write only what is needed: giving every employee an EVIDE account does not mean making accusations and documents visible to everyone. EVIDE does not automatically link two records just because they concern the same event: the link is the reference declared by the depositor.
Regulatory referenceIn Italy, if the reconstruction leads to disciplinary proceedings, Article 7 of the Workers' Statute (Law 300/1970) applies: prior notice of the charge and the employee's right to be heard in their defence. Other jurisdictions have their own procedures. Linked responses do not replace them.
Boundary of the EVIDE claim: EVIDE preserves three distinct positions with their provenance. It does not establish who is right, does not determine the cause of the incident and does not attribute responsibility.
Condominium
The building administrator carries out urgent works and collects the owners' positions before the meeting

The recordAfter a leak from the roof, the administrator orders urgent works. The administrator deposits an HSI record with the decision type, for example «Urgent roof repair», the declared role of administrator, the closure time, the quote as an external reference with its declared SHA-256 and, as declared uncertainties, what was not yet known, such as the extent of the damage.

The responsesThe administrator individually invites the members of the building council, or the owners who have an EVIDE account. Each declares their position on the same frozen representation: I AGREE (CONCORDO), I DISPUTE (CONTESTO) with reasons, I ACKNOWLEDGE WITHOUT EXPRESSING AGREEMENT (PRENDO ATTO SENZA ESPRIMERE ACCORDO) or I AM NOT IN A POSITION TO ASSESS (NON SONO IN CONDIZIONE DI VALUTARE).

Regulatory referenceIn Italy, Article 1135(2) of the Civil Code: the administrator may not order extraordinary maintenance works unless they are urgent, and in that case must report on them at the first owners' meeting. Resolutions remain with the meeting, with the quorums of Article 1136 of the Civil Code.

Reconstructive ValueWhen reporting to the meeting, the administrator has their own declared decision and the individual positions collected in the days of the works, each with its own receipt time.

Boundary of the EVIDE claim: responses are not a resolution or a vote, do not replace the meeting or its minutes, and the summary does not calculate majorities. EVIDE does not assess whether the works were really urgent.
Technical inspection
A technician declares the outcome of an on-site inspection and invites the parties present to take a position

The recordA loss adjuster, an installer or a party-appointed technician carries out an inspection in the presence of the owner, the contractor and an insurance representative. The technician deposits an HSI record with the declared outcome, the photographs as external references with their SHA-256, without handing them to EVIDE, and, as declared uncertainties, what could not be inspected.

The responsesThe technician invites each of the parties present. The owner declares I AGREE (CONCORDO), the contractor I DISPUTE (CONTESTO) with its reasons, the insurance representative I AM NOT IN A POSITION TO ASSESS (NON SONO IN CONDIZIONE DI VALUTARE) pending documentation.

Reconstructive ValueThe parties' positions are collected on the same representation of the outcome, shortly after the inspection, each with its own provenance. Any disagreement stays documented with its reasons, instead of surfacing months later as conflicting recollections.

Boundary of the EVIDE claim: EVIDE does not establish the state of the site or the correctness of the outcome, does not prove who was present at the inspection and does not replace the inspection report or the expert assessment.
DPO and data breach
The decision to notify or not notify a breach, with the positions of the functions involved

The recordThe person responsible for the decision deposits an HSI record: notifying or not notifying the breach to the supervisory authority, with the declared role, the closure time, the reference to the breach register entry with its declared SHA-256, and the declared uncertainties.

The responsesThey invite the CISO, the DPO or the legal advisor. Each declares and explains their position; a dissenting view stays preserved as I DISPUTE (CONTESTO), with its reasons.

Regulatory referenceArticle 33 GDPR: notification to the supervisory authority within 72 hours, unless the breach is unlikely to result in a risk; paragraph 5 requires any breach to be documented, including the facts, its effects and the remedial action taken.

Reconstructive ValueOver time it is possible to reconstruct not only the declared decision, but also which functions were consulted and what position they had declared at that moment.

Boundary of the EVIDE claim: responses do not replace the documentation required by the GDPR and do not transfer the decision to the respondents. EVIDE does not assess whether the decision was correct.
Shift handover
The outgoing shift supervisor declares the state of the plant; the incoming one acknowledges or disputes it

The recordAt the end of the shift, the outgoing supervisor deposits an HSI record with the declared state of the plant, the open anomalies as declared uncertainties and the reference to the shift log.

The responsesThe outgoing supervisor invites the incoming shift supervisor, who declares I ACKNOWLEDGE WITHOUT EXPRESSING AGREEMENT (PRENDO ATTO SENZA ESPRIMERE ACCORDO), or I DISPUTE (CONTESTO) with reasons if the situation differs from what was declared.

Reconstructive ValueIf it later has to be established what was communicated at the shift change, what the outgoing supervisor declared to hand over and the position declared by the incoming one remain distinct.

Boundary of the EVIDE claim: EVIDE does not establish the state of the plant. Acknowledging is not agreeing, and the response does not prove that the handover took place in person.
Supplier and client
The supplier declares a service outage resolved; the client's contact person, from another organization, takes a position

The recordThe supplier's service manager deposits an HSI record with the declared closure of the outage, the declared restoration time and the reference to the ticket.

The responsesThe service manager invites the client's contact person, who belongs to another organization and has no access to the supplier's systems. The contact reads only the FAST REVIEW and declares I AGREE (CONCORDO), or I DISPUTE (CONTESTO) stating, for example, that the service was not yet fully restored.

Reconstructive ValueBoth positions stay preserved outside the systems of both parties, without the client having to receive the complete record or the supplier's internal documents.

Boundary of the EVIDE claim: a response is not a contractual acceptance, unless the contract between the parties provides for it. EVIDE does not verify compliance with service levels.
Professional and client
The professional declares the advice given and the client's choice; the client takes a position

The recordA consultant, a lawyer or an accountant deposits an HSI record with the declared advice, the choice communicated by the client, the closure time and the risks stated as declared uncertainties.

The responsesThe professional invites the client, who declares I AGREE (CONCORDO) if the representation matches what was agreed, I ACKNOWLEDGE WITHOUT EXPRESSING AGREEMENT (PRENDO ATTO SENZA ESPRIMERE ACCORDO), or I DISPUTE (CONTESTO) with their own reasons.

Reconstructive ValueIf a dispute later arises about what had been advised, the professional's declaration and the client's declared position on the same representation remain preserved.

Boundary of the EVIDE claim: EVIDE does not assess the advice and does not prove that the client understood it. The response does not replace the engagement letter, informed consent or other documents required by professional rules.
In short
What Linked responses do, and what they do not do

The value of Linked responses lies in what they preserve. Their boundaries are what make that value reliable for whoever examines the records later.

What they do

  • They collect the positions of identified people, each deposited with their own EVIDE account (DAPI), including people from other organizations.
  • They preserve each response as an autonomous record, with the receipt time recorded by EVIDE, the SHA-256 fingerprint and its own EAR-LINKED.
  • They keep the history of positions: a new response replaces or supplements the previous one, which is kept.
  • They give the depositor of the record an always up-to-date summary, on the web and in the app.
  • They make it possible to document the record and the responses in a FEDIS-LINKED examined and signed by a forensic expert.
  • They leave anyone who disagrees free to deposit their own autonomous record, with their own invitations.

What they do not do

  • They do not modify the depositor's record: each position is added, none overwrites.
  • They do not turn positions into a vote: the counts remain individual declarations, and the invited people, chosen by the depositor of the record, speak for themselves.
  • They do not establish the truth of the record or who is right: that assessment stays with whoever examines the records.
  • They do not verify the declared role or prove that an invitation was read: EVIDE records what happens on the platform.
Core Concept
Decision Closure

Two different timestamps appear in every Human Structured Intake record, and they answer two different questions:

TimestampWhat it answers
decision.closure_timestamp_utcWhen was the decision itself closed? This is the moment at which the person declares the decision was actually made, entered by the person, in UTC.
Intake TimestampWhen did EVIDE receive and preserve this record? This is generated by the server at the moment the intake is processed, not entered by the person.

These two moments are frequently different, and that difference is expected, not an error. A decision might be closed at 16:00 and only recorded in EVIDE at 18:03, because of a delayed workflow step, a batch submission process, or simply because the person recording it does so later in the day.

Why this distinction matters for historical reconstructability: if the two timestamps were treated as interchangeable, a later reviewer could wrongly conclude that a decision was made at the moment it was administratively recorded, rather than at the moment it was declared closed. Keeping them visually and textually distinct makes it possible to reconstruct the declared sequence, keeping what is declared separate from what is recorded by the server.
What this does not establish: decision_closure_timestamp_utc is a value declared by the person completing the intake. It is not a cryptographic or «trusted» timestamp of when the decision was actually made in the real world - EVIDE has no independent way to confirm that the declared closure time is accurate. What EVIDE does preserve, independently, is the Intake Timestamp: the moment the record itself was received and canonicalized.
Beyond a Single Declared State
Human Judgment Evolution

Human oversight is frequently represented in governance tooling as if it occurred at a single moment: a recommendation is produced, a person reviews it, and a final decision is recorded.

In practice, human judgment may evolve. New information can arrive after an initial recommendation but before a later accountable decision, and the reviewer’s assessment, rationale, classification or decision posture may change as that information becomes available.

A single Human Structured Intake record preserves one declared state at the time of intake. Where multiple states need to be preserved over time, a sequence of linked Human Structured Intake records can preserve those successive declarations independently. Each state remains its own evidentiary object, with its own server-generated Intake Timestamp and its own hash computed over that record’s evidentiary payload, a later state does not rewrite, normalize or replace an earlier state.

EVIDE does not rewrite earlier states when later information arrives.
This allows the evolution of declared human judgment to remain historically reconstructable, without forcing the final record to retrospectively narrate every intermediate state.
1. Initial declared review state
2. Additional information received
3. Reviewer’s assessment changes
4. Further review or escalation
5. Later declared decision state

Each step may be preserved as an independent Human Structured Intake record. The structural relationship between deposited states can be reconstructed by an authorized consumer without modifying any previously deposited state.

What this does not establish

Before the Evidentiary Fields
Common / Operational Intake Fields

The eight fields below provide operational and organizational context. They are shared with EVIDE’s other intake types and are not specific to the Human Structured evidentiary model, they are documented here briefly, for completeness, rather than in the same depth as the fields in the next section.

FieldTypeRequirementWhat it is
titlestringRequiredShort label for the record. Verified in the code: this value is copied directly into decision.summary in the canonical payload, it is not a separate, unrelated field.
business_area_idintegerRequiredThe business area the intake belongs to. Verified in the code: must reference an existing, active business area, otherwise the request is rejected.
descriptionstringOptionalFree-text description stored alongside the record. Not included in the canonical evidentiary payload itself.
context_referencestringOptionalFree-text operational reference for internal use.
notesstringOptionalFree-text internal notes.
topicstringOptionalFree-text topic label for organizing intakes.
case_referencestringOptionalFree-text case or matter reference. This is the same field used by the «Evidence from the same case» search available elsewhere in EVIDE.
evidence_referencestringOptionalFree-text evidentiary reference for internal cross-linking.

These fields provide operational and organizational context for locating and managing the intake within the platform. They are not part of the Human Structured evidentiary model documented in the rest of this page, and their presence or absence does not affect the evidentiary fields below.

The Core of This Guide
Human Structured Evidentiary Fields

The fifteen fields below are the fields specific to the Human Structured evidentiary model, verified individually against the EVIDE validator. The table gives a quick summary; a full explanatory card follows for every field.

FieldTypeRequirement
decision_typestringRequired
decision_closure_timestamp_utcdatetimeRequired
authority_rolestringRequired
authority_idstringOptional
authority_verification_notestringOptional
classification_statusenumOptional
threshold_statusenumOptional
threshold_referencestringConditional
threshold_attribution_statusenumOptional
trace_accessstringOptional
boundary_readiness_statusenumRequired
readiness_gate_identifierstringConditional
readiness_gate_scope_referencestringConditional
unresolved_signals[]array of stringsConditional
declared_uncertainties[]array of objectsOptional
Decision Type decision_type #decision-type
Required string
Canonical Path

decision.type

What It Means

A free-text label describing the category of the human decision or intervention being recorded, for example, what kind of decision this is, not what the decision concluded.

Why It Exists

Without this field, a record would not indicate at all what kind of decision or intervention was recorded. It gives every other field in the record a category to refer to.

When To Use It

Always, this field is required for every Human Structured Intake.

How To Choose The Value

Choose a label specific enough to distinguish this decision from other decisions of a different kind, but do not duplicate the full narrative that belongs in the title field (which becomes decision.summary). A good decision type names the category of action; the title/summary describes this specific instance.

Relationships

Distinct from the common field title, which is copied directly into decision.summary - a short natural-language description of this specific decision. decision_type names the category; decision.summary narrates the instance.

Business Example

A Compliance Officer approving a temporary policy exception might record the decision type as «Compliance exception approval.» A technical manager authorizing a production restart might use «Production line restart authorization.»

Example Value
decision_type"Human review of automated recommendation"
Common Misinterpretations
  • This is not a fixed enumeration - the validator accepts any non-empty free text. Consistency of terminology across records is an organizational discipline, not a system-enforced constraint.
  • A specific decision type does not by itself establish that the decision was made correctly or appropriately - it only names what kind of decision it was.

What EVIDE Preserves

  • That a decision of this declared type was recorded, at this declared closure time, by this declared authority.

What EVIDE Does NOT Claim

  • That the declared type is drawn from a controlled or standardized vocabulary comparable across different organizations.
Decision Closure Timestamp (UTC) decision_closure_timestamp_utc #decision-closure-timestamp
Required datetime
Canonical Path

decision.closure_timestamp_utc

What It Means

The declared moment at which the human decision itself was closed, not the moment the record was submitted to EVIDE. See the dedicated Decision Closure section above for the full distinction from the Intake Timestamp.

Why It Exists

A decision and its evidentiary preservation rarely happen at the exact same instant. Recording the declared closure time, separately from the server-generated intake time, makes it possible to distinguish when the decision was declared closed from when EVIDE received the record. The closure time remains a declared value: it does not by itself prove when the decision took place in the real world.

When To Use It

Always, this field is required. Enter the moment the decision was closed, not the moment you are filling in the form.

How To Choose The Value

In the web form, enter your device’s local time: the browser converts it to UTC and shows, before submission, the UTC time that will be recorded together with the time zone used. In the web form, a time that does not exist in your time zone (switch to daylight saving time) is rejected; a time that occurs twice (return to standard time, for example 02:30 on 26 October 2025 in Italy) requires you to choose the offset explicitly, with no automatic choice. The mobile app performs the same conversion to UTC; the explicit choice for repeated times is currently available only in the web form. Via the API, the value must be sent in ISO 8601 with Z (for example 2026-04-07T16:00:00Z); an explicit offset such as +02:00 is also accepted and converted exactly to UTC.

Conditional Behavior
Verified in the code: the server accepts only explicit ISO 8601 (YYYY-MM-DDTHH:MM with optional seconds, followed by Z, by an offset ±HH:MM or by no zone, interpreted as UTC). The following are rejected with an explicit error, never silently corrected: relative expressions such as «yesterday», non-existent dates or times (30 February does not become 2 March), closures more than 5 minutes later than the server time and closures earlier than 1 January 2000. An empty value is rejected, rather than falling back to the current time.
Business Example

A production line stops at 14:32 local time. The technical manager reviews the conditions and authorizes a restart, closing that decision at 16:00 local time, but only records the intake in EVIDE at 18:03, after finishing other urgent tasks. The closure timestamp preserves 16:00 (converted to UTC); the Intake Timestamp separately preserves 18:03.

Example Value
decision_closure_timestamp_utc"2026-04-07T16:00:00Z"
Common Misinterpretations
  • This is not the moment the record was received by EVIDE - that is the separate, server-generated Intake Timestamp.
  • Via the API, sending local time marked as UTC (Z) produces a closure shifted by your own offset: a value that falls in the future relative to the server is rejected, one in the past is not. In the web form and in the app, the conversion is automatic and visible before submission.

What EVIDE Preserves

  • The declared moment the decision was closed, as declared by the person recording it.

What EVIDE Does NOT Claim

  • That this timestamp is a cryptographically trusted or independently verified record of when the real-world decision actually occurred. It is a declared value.
Authority Role authority_role #authority-role
Required string
Canonical Path

authority.role

What It Means

The organizational role, in what capacity, the decision is declared to have been made, distinct from the identity of the person who made it.

Why It Exists

A name alone does not indicate in what organizational capacity a decision was taken. The role helps a later reader reconstruct the declared organizational authority behind the decision, regardless of who specifically held that role at the time.

When To Use It

Always, this field is required for every Human Structured Intake.

How To Choose The Value

Use the role title that is organizationally meaningful for this decision, e.g. «Compliance Officer,» «SOC Manager,» «HR Director,» «Fraud Analyst,» «Plant Manager.» Free text, not a fixed list.

Relationships

Distinct from authority_id (who) and from the DAPI identity of the logged-in session (see Authority Identifier below). The role answers «in what capacity,» not «which specific person.»

Business Example

The same person might hold multiple roles across different decisions; the same role might be held by different people over time. Recording the role, separately from the individual, keeps the organizational context legible even when personnel change.

Example Value
authority_role"Compliance Officer"
Common Misinterpretations
  • This field does not verify that the declared person actually held this role in the organization - it is a declared value, like the other free-text fields on this page.

What EVIDE Preserves

  • The declared organizational role or capacity under which the decision was made.

What EVIDE Does NOT Claim

  • That EVIDE independently confirmed that the person held this role within the organization.
Authority Identifier authority_id #authority-id
Optional string
Canonical Path

authority.id

What It Means

A declared identifier of who made the decision. Verified in the code: if left blank, this field defaults to the full name of the currently logged-in user, but it can be changed, for the legitimate case of recording a decision made by someone else.

Why It Exists

Not every decision recorded in EVIDE was made by the person operating the keyboard. Allowing this field to be edited lets a person accurately record a decision made by a colleague, while still keeping the verified identity of the underlying session separately preserved.

When To Use It

Leave it blank when you, the logged-in user, are the person who made the decision, your name will be used automatically. Fill it in explicitly when you are recording a decision made by a different person.

When Not To Use It

Do not treat this field as a substitute for, or a modification of, your verified account identity, that identity is preserved separately and automatically, regardless of what you enter here.

Relationships

Verified in the code: every Human Structured record also carries authority.dapi_number, the DAPI identifier of the actually logged-in, authenticated session, set automatically by the server on every submission and never read from the form. authority.id and authority.dapi_number are deliberately independent: the first is a declared label, the second is the verified identity of the session.

Business Example

An assistant enters a decision into EVIDE on behalf of a manager who actually made the decision. The assistant keeps their own session authenticated (preserved automatically as authority.dapi_number), but sets authority_id to the manager’s name, accurately reflecting who actually made the decision.

Example Value
authority_id"Jane Whitfield"
Common Misinterpretations
  • authority_id is not the same thing as an independently verified authority. It is a declared, free-text value that by default matches the logged-in user, but can be overridden.
  • Overriding this field does not change or replace the verified DAPI identity of the session - that identity is recorded independently, in a separate field, regardless of what is declared here.

What EVIDE Preserves

  • The declared identifier of who made the decision (by default, the logged-in user’s name if not changed).
  • Separately and always: the DAPI identity of the actual authenticated session, in authority.dapi_number.

What EVIDE Does NOT Claim

  • That the declared authority.id value has itself been independently verified against an external identity system.
Reference on the Decision-Maker’s Authority authority_verification_note #authority-verification-note
Optional string
Canonical Path

authority.verification

What It Means

A free-text note, optionally declared, that the person recording the decision can use if they intend to link the declared authority to a more specific reference, for example, a DAPI reference for the person or role involved.

Why It Exists

It gives the declarant a way to add a more specific reference to the declared authority, without requiring one on every record.

When To Use It

When you want to declare a more specific reference tied to the authority behind this decision, and such a reference is genuinely available.

When Not To Use It

Do not use this field as if writing it constituted a verification. It is a declared note, not a check performed by EVIDE.

Conditional Behavior
Verified in the code: if this field is present and non-empty, the evidentiary profile records claimed instead of declared in the Identity dimension (the authority_verification_status column and the «Identity» row of the EAR). The Human Structured intake response does not contain this field; on the machine channel the API response includes it, as described in the JSON Schema Reference. This reflects that a reference was declared, not that it was verified. The text appears in the EAR as «Declared authority reference», marked as not verified by EVIDE: the form flags this before submission.
Business Example

A Compliance Officer references an internal DAPI-linked identity as supporting context for the declared authority behind an exception approval, without that reference being independently checked by EVIDE.

Common Misinterpretations
  • A populated verification note does not mean that EVIDE performed an identity check. The resulting claimed status describes what was declared, not what was verified.
  • This field has no relationship with the DAPI identity of the actually logged-in session, which is preserved automatically and separately (see Authority Identifier).

What EVIDE Preserves

  • That a verification-related note was declared, exactly as entered.

What EVIDE Does NOT Claim

  • That the declared note constitutes, or resulted from, an independent identity verification performed by EVIDE.
Classification Stability classification_status #classification-status
Optional enum
Canonical Path

intervention.classification_status

Allowed Values
stable

The classification assigned to this decision is considered settled, with no known ambiguity under the categorization active at the time of closure.
Example: a fraud case reviewed and closed with a clear, uncontested categorization.
Does not mean: that the classification is permanently fixed or immune to future revision, only that no ambiguity was known at closure.

provisional

The classification is still tentative or pending refinement, it may change as more information emerges.
Example: an active security investigation where the incident category may be revised as the investigation continues.
Does not mean: that the decision itself is incomplete, the decision can still be finalized while its classification remains provisional.

contested

The classification is assigned despite a known interpretive disagreement, or an overlap with another category.
Example: a decision where two reasonable people could categorize the same case differently, and that disagreement is known at closure.
Does not mean: that the underlying decision is invalid, only that its categorization carries an acknowledged interpretive tension.

Why It Exists

It makes the operational quality of a classification observable at the time of deposit, rather than presenting every classification with the same implicit, undeclared confidence.

When To Use It

When you have a view on how settled, provisional or contested the classification assigned to this decision is.

When Not To Use It

If you have no basis for judging the stability of the classification, it is acceptable to leave this field unset rather than guess, the field is optional, and the system assumes no default state if it is absent.

Example Value
classification_status"provisional"

What EVIDE Preserves

  • The declared stability state of the classification assigned to this decision.

What EVIDE Does NOT Claim

  • That the classification itself is correct - only how settled or contested its assignment was declared to be.
Threshold Status threshold_status #threshold-status
Optional enum
Canonical Path

intervention.classification_context.threshold_status

Allowed Values
met

A relevant decisional threshold is declared to have been met.
Example: an internal policy required a documented justification above a certain risk level, and one was provided.

not_met

A relevant decisional threshold is declared not to have been met.
Example: the review found that the conditions required for automatic approval were not satisfied, requiring manual intervention.

unknown

A threshold exists in this context, but whether it was met is not known at the time of closure. This is different from not_defined - here, a threshold genuinely applies, but its status could not be established.

not_defined

No threshold was defined for this case. This is different from unknown - here, there is no applicable threshold to evaluate, rather than an unresolved one.

What It Means

A threshold, in this context, is a predefined decision criterion, a policy limit, an operational rule, an approval condition, against which a decision may be evaluated. This field declares whether such a threshold was met.

Why It Exists

It exposes whether a decisional threshold applied to this case, and if so, its declared status, information that is often implicit and undocumented in ordinary workflow tools.

When To Use It

When a defined threshold, rule or policy condition is relevant to this decision.

When Not To Use It

When no such threshold genuinely applies to this decision, in that case, not_defined is the accurate value, rather than simply leaving the field blank, if you have reason to actively declare that no threshold applies.

Conditional Behavior
Verified in the code: this field governs the visibility of threshold_reference below, if threshold_status is not_defined, the reference is hidden in the form and not submitted; if a value arrives anyway, the request is rejected rather than the value being silently discarded.
Example Value
threshold_status"met"
Common Misinterpretations
  • unknown must not be read as equivalent to «no threshold exists.» That is what not_defined means. unknown means that a threshold applies, but its status could not be established.

What EVIDE Preserves

  • The declared status of a decisional threshold relevant to this case.

What EVIDE Does NOT Claim

  • That EVIDE independently evaluated whether the threshold was actually met - this is a declared status.
Threshold Reference threshold_reference #threshold-reference
Conditional string
Canonical Path

intervention.classification_context.threshold_reference

What It Means

A free-text reference to the specific threshold, policy or rule cited in threshold_status above.

Why It Exists

It allows the declared threshold to be traced back to something concrete, a policy document, a procedure, an internal control, rather than remaining an unattributed general statement.

When To Use It

When threshold_status is met, not_met, or unknown, and you have a specific reference available, for example, a policy name, a procedure code or a document identifier, given only as illustrative examples compatible with this free-text field.

Conditional Behavior
Verified in the code: if threshold_status is not_defined, a value in this field is rejected: declaring a reference to a threshold that is declared not to exist would be contradictory. In the form, the field is hidden and not submitted, while the typed value remains in the form if you switch back to a different status. Without a threshold status, the reference provided is retained.
Example Value
threshold_reference"Internal policy COM-EXC-04, section 3.2"

What EVIDE Preserves

  • The declared reference to the specific threshold cited, when a threshold status other than not_defined applies.

What EVIDE Does NOT Claim

  • That the referenced document, policy or procedure was independently retrieved, read or validated by EVIDE.
Threshold Attribution threshold_attribution_status #threshold-attribution
Optional enum
Canonical Path

intervention.classification_context.threshold_authority.attribution_status

Allowed Values
attributed

A single, identifiable, attributable authority for the threshold was defined at closure.
Example: a policy explicitly owned by a named committee.
When to use it: when you can point to one clear owner of the threshold.

fragmented

The threshold is defined across multiple sources, with no single attributable authority.
Example: a rule assembled from several overlapping internal guidance documents with no single owner.
Common misinterpretation: fragmented does not mean that the threshold is invalid, only that its ownership is distributed.

implicit

The threshold is present in practice but was not formally defined or attributable at closure.
Example: an unwritten but consistently applied internal norm.
Common misinterpretation: implicit does not mean that informal thresholds are illegitimate, only that they lack formal attribution.

unknown

The authority behind the threshold could not be verified at the moment of closure.
Example: the declarant is aware that a threshold exists but cannot identify who owns it.

What It Means

Threshold attribution describes how clearly the authority or ownership behind the threshold cited above can be traced to a specific person, role or committee, not whether the threshold itself was met.

Why It Exists

It becomes relevant precisely when a threshold status of met or not_met is declared, but the ownership of that threshold is not clearly attributable to a single source, making that ambiguity itself part of the preserved record.

When To Use It

When you have a view on how clearly attributable the ownership of the cited threshold is.

Example Value
threshold_attribution_status"attributed"

What EVIDE Preserves

  • The declared attributability state of the authority behind the cited threshold.

What EVIDE Does NOT Claim

  • Who should own the threshold, or that the substance of the threshold was independently reviewed - only whether an attributable source of authority for it was declared to exist.
Trace Reference trace_access #trace-access
Optional string
Canonical Path

intervention.trace.access

What It Means

A free-text reference that lets someone later locate the broader context of this decision within the system where it actually took place, a ticket, a case ID, an audit trail reference, a log reference or a workflow reference, given as illustrative examples of what is semantically compatible with this field.

Why It Exists

A decision rarely exists in isolation from the broader operational trail that surrounded it. This field preserves a pointer to that trail, without EVIDE needing to receive or store the trail itself.

When To Use It

Whenever a specific, locatable reference exists in another system, a ticket number, a case file or an audit log entry, that a later reviewer could use to find more context.

Example Value
trace_access"SOC-CASE-4471"
Common Misinterpretations
  • A trace reference does not mean that EVIDE has access to, or has inspected, the system that reference points to. It is a declared pointer, nothing more.

What EVIDE Preserves

  • The declared reference for locating further context about this decision.

What EVIDE Does NOT Claim

  • That EVIDE has access to, has retrieved or has verified the contents of the referenced system.
Boundary Readiness boundary_readiness_status #boundary-readiness
Required enum
Canonical Path

handoff.boundary_readiness.status

Allowed Values
candidate

No independent gate has assessed this object. The declarant states only that they consider it ready, without an independent check having been performed.
When to choose it: this is the honest default when no separate readiness mechanism was involved, it is not a weaker or lesser value, it is the accurate one for that situation.

verified

An independent readiness gate confirmed stability across what it declares to be complete visibility, with no unresolved signals.
When to choose it: only when a genuinely separate mechanism, distinct from the person or system that made the decision, performed this assessment.
Common misinterpretation: this value cannot be self-declared simply by feeling confident about a decision; it specifically means that an independent gate was involved.

verified_partial

An independent gate confirmed what it was able to observe, but explicitly declares that some relevant signals remain unresolved.
When to choose it: when a readiness gate was involved but its visibility was genuinely incomplete, requires at least one entry in unresolved_signals.

unverifiable

A readiness gate attempted an assessment, but the visibility available to it was insufficient to reach any stability conclusion. The record retains the declared assessment attempt: it does not in itself demonstrate diligence, nor that the process failed.
When to choose it: when a genuine attempt at a readiness assessment could not reach a conclusion due to insufficient visibility, it also requires at least one entry in unresolved_signals.

What It Means

Boundary readiness declares how ready this decision is considered to be, at the moment of closure, for its evidentiary preservation, specifically, whether an independent readiness gate assessed it, and what that gate could and could not observe. It is a declaration about the state of readiness, not a property that EVIDE itself measures or confirms.

Why It Exists

Different decisions carry very different degrees of independently confirmed readiness before they are preserved. Collapsing all of them into a single undifferentiated state would hide exactly the information a later reviewer most needs: was this decision independently checked before being recorded, and if so, how completely?

When To Use It

Always, this field is required for every Human Structured Intake.

How To Choose The Value

Ask yourself concretely: did a mechanism genuinely separate from the decision-maker assess the readiness of this object before it was recorded? If no such mechanism was involved, the honest value is candidate. If one was involved, choose among verified, verified_partial, or unverifiable based on how genuinely complete that mechanism’s visibility was.

Relationships

Verified in the code: visibility_surface (an internal field in the canonical payload) is derived mechanically from this value through a fixed mapping, it is never a separate choice made by the person filling in the form. This value also governs whether readiness_gate_identifier/readiness_gate_scope_reference and unresolved_signals are required (see Conditional Field Relationships below for the exact rules).

Conditional Behavior
If this value is anything other than candidate, both readiness_gate_identifier and readiness_gate_scope_reference become required together. If this value is verified_partial or unverifiable, at least one entry in unresolved_signals becomes required. Verified in the code: with candidate, a gate identifier or scope, or any unresolved signals, are rejected; with verified, unresolved signals are rejected. The chosen status is never modified and no submitted data is silently discarded. The declarant’s uncertainties are recorded, with any status, in declared_uncertainties.
Business Example

A technical manager authorizing a production restart after an anomaly might declare verified_partial if an automated diagnostic gate checked most, but not all, of the relevant sensors before the restart, with the specific unchecked sensor recorded as an unresolved signal.

Example Value
boundary_readiness_status"verified_partial"
Common Misinterpretations
  • The word verified in this field is a declared value in the data model, not an assessment performed by EVIDE. EVIDE does not itself check whether the declared gate actually operated, or whether its conclusions were accurate.
  • Do not read candidate as a deficient or incomplete submission, it is the structurally accurate value whenever no independent readiness gate was genuinely involved.

What EVIDE Preserves

  • The declared readiness state at the boundary and, when applicable, a reference to the declared mechanism that performed the assessment.

What EVIDE Does NOT Claim

  • That EVIDE itself performed, confirmed or independently verified any readiness assessment. A value of verified describes what was declared about an upstream or independent gate, it is never EVIDE’s own verification of the decision.
Readiness Gate Identifier readiness_gate_identifier #readiness-gate-identifier
Conditional string
Canonical Path

handoff.boundary_readiness.readiness_gate.identifier

What It Means

A gate, in this context, is any mechanism, human or automated, that performed the readiness assessment declared in boundary_readiness_status. This field names or identifies that mechanism.

Why It Exists

It allows the declared readiness assessment to be traced back to something specific, rather than remaining an unattributed general statement.

When To Use It

Required whenever boundary_readiness_status is anything other than candidate - that is, whenever an independent gate is being declared.

Conditional Behavior
Verified in the code: required together with readiness_gate_scope_reference whenever boundary_readiness_status is not candidate. If either is missing under that condition, the request is rejected. With the candidate status, neither field should be provided: if submitted, the request is rejected, because candidate means that no separate mechanism has been declared.
Business Example

A diagnostic check used before authorizing a production restart, or the internal procedure code governing a compliance exception review.

Example Value
readiness_gate_identifier"COM-EXC-04"
Common Misinterpretations
  • The name «gate» does not imply that EVIDE itself performed, ran or has access to this mechanism. It is a declared identifier for a mechanism that operated entirely outside EVIDE.

What EVIDE Preserves

  • The declared identifier of the mechanism that performed the readiness assessment.

What EVIDE Does NOT Claim

  • That EVIDE executed, inspected or independently verified the named mechanism.
Readiness Gate Scope Reference readiness_gate_scope_reference #readiness-gate-scope
Conditional string
Canonical Path

handoff.boundary_readiness.readiness_gate.scope_reference

What It Means

While readiness_gate_identifier names the mechanism or control declared to have operated, this field describes the perimeter or scope that mechanism is declared to have covered.

Why It Exists

A named gate is more useful when its coverage is also specified, the same diagnostic check might cover an entire facility in one case and a single machine in another.

When To Use It

Required under the same condition as readiness_gate_identifier above: whenever boundary_readiness_status is anything other than candidate.

Relationships

Distinct from readiness_gate_identifier: one names the mechanism, the other describes what it is declared to have covered.

Business Example

For a production-line restart, the identifier might name the diagnostic control used, while the scope reference names the specific machine or line that control covered.

Example Value
readiness_gate_scope_reference"Line 3, extrusion module"

What EVIDE Preserves

  • The declared scope or perimeter that the named readiness gate is declared to have covered.

What EVIDE Does NOT Claim

  • That the declared scope was independently confirmed to be accurate or complete.
Unresolved Signals unresolved_signals[] #unresolved-signals
Conditional array of strings
Canonical Path

handoff.boundary_readiness.unresolved_signals

What It Means

An unresolved signal is a specific element that remained unresolved or unattributed at the moment the readiness assessment was made, the declared «why» behind a verified_partial or unverifiable result, not just the fact that one occurred.

Why It Exists

Without this list, a reader encountering «Boundary readiness: verified_partial» would know that something was incomplete, but not what, often the single most useful piece of information for a later reconstruction of the decision.

When To Use It

Required whenever boundary_readiness_status is verified_partial or unverifiable - at least one entry is required in that case.

When Not To Use It

Not allowed with candidate (no separate mechanism declared) or with verified (visibility declared complete): if submitted, the request is rejected. The declarant’s personal uncertainties are not signals of a verification mechanism: they belong in declared_uncertainties.

How To Choose The Value

List each specific element that remained unresolved, as concretely as possible, multiple entries are supported when more than one signal remained open.

Relationships

Directly governed by boundary_readiness_status: required (minimum one entry) when that value is verified_partial or unverifiable.

Conditional Behavior
Verified in the code: if boundary_readiness_status is verified_partial or unverifiable and this array is empty, the request is rejected; with candidate or verified, a non-empty array is rejected. Empty entries and values that are not text are rejected, not ignored.
Business Example

For the SOC scenario in the Enterprise Use Cases above, when a threat-hunting team separate from the responder examined the endpoints with incomplete visibility (verified_partial), this might read: «Origin of two API requests not yet attributed.» If only the responder carried out the assessment, the same sentence is a declared uncertainty.

Example Value
unresolved_signals[]["Origin of two API requests not yet attributed"]
Common Misinterpretations
  • EVIDE does not itself determine the truth, severity, materiality or relevance of any listed unresolved signal - it preserves the declared list exactly as entered, without independently assessing its content.

What EVIDE Preserves

  • The specific signals declared as unresolved at the moment of the readiness assessment.

What EVIDE Does NOT Claim

  • That EVIDE evaluated the truth, severity, materiality or relevance of any listed signal. It preserves the declaration, not a judgment about it.
Declared Uncertainties declared_uncertainties[] #declared-uncertainties
Optional array of objects
Canonical Path

declared_uncertainties (additive extension of schema 2.1, declared in extensions)

What It Means

What the declaring person still considers uncertain at the moment of decision closure. Each entry contains a text (statement, required) and an optional context (context, for example a case reference).

Why It Exists

Unresolved signals belong to a verification mechanism separate from the decision-maker. Without this field, a declarant choosing candidate would have had no place, within the hashed record, for what they themselves considered uncertain.

When To Use It

With any readiness value, including candidate and verified, when something remains that you consider uncertain. With verified_partial, the declarant’s uncertainties coexist with the verification mechanism’s signals and remain distinct from them.

How To Choose The Value

One entry for each uncertainty, as concretely as possible. The order in which you declare them is retained. A maximum of 20 entries; text up to 1000 characters, context up to 500.

Conditional Behavior
Verified in the code: a context without text, values that are not text, unexpected keys or exceeded limits are rejected, not truncated or ignored. A form card left completely empty contains no declaration and is ignored. Declared uncertainties are not included in the computation of FCC, DWC and FAC.
Business Example

In the SOC case, the responder authorizes continued operation without any separate mechanism having assessed the conditions (candidate) and declares: «Possible EDR sensor false positive», with context «Case SOC-2026-0412».

Example Value
declared_uncertainties[][{"statement": "Possible EDR sensor false positive", "context": "Case SOC-2026-0412"}]
Common Misinterpretations
  • A declared uncertainty is not a signal of a verification mechanism and does not indicate that a verification took place.
  • A record with fewer declared uncertainties is not a more diligent record: it describes what was declared, not how well the situation was handled.

What EVIDE Preserves

  • The declared uncertainties, in the declared order, in the hashed record; in the EAR they appear in a dedicated section, distinct from the verification mechanism’s signals.

What EVIDE Does NOT Claim

  • That the uncertainties were assessed by a mechanism or by EVIDE, or that the list is complete.
How the Fields Fit Together
Conditional Field Relationships

The rules below are verified directly against the EVIDE validator - not assumed from field names or general documentation patterns.

If…Then…
threshold_status = not_definedA value in threshold_reference is rejected. In the form, the field is hidden and not submitted. Without a threshold status, the reference provided is retained.
boundary_readiness_status = candidateGate identifier and scope and unresolved_signals[] are not allowed: if submitted, the request is rejected.
boundary_readiness_status = verifiedunresolved_signals[] is not allowed: if open signals remain, the correct status is verified_partial.
boundary_readiness_status ≠ candidatereadiness_gate_identifier AND readiness_gate_scope_reference both become required together. If either is missing, the request is rejected.
boundary_readiness_status ∈ {verified_partial, unverifiable}unresolved_signals[] becomes required, with a minimum of one entry. An empty array is rejected under this condition.
An evidence_references[] entry includes a hash_valuehash_scope and hashed_by both become required together for that entry. A partial hash declaration, a value without both of these, is rejected, as is hashed_by or hash_scope without a value.
declared_uncertainties[]Independent of readiness: allowed with every status, it neither modifies nor replaces the gate’s signals.
An unexpected field, or one of the wrong typeThe request is rejected: no submitted field is silently ignored.
Every rejection returns an explicit message in the language of the form; after an error, the web form restores the values entered, including the chosen readiness. A related, non-conditional fact worth noting here: visibility_surface, an internal field inside the canonical payload, is always derived mechanically from boundary_readiness_status through a fixed mapping. It is never a value chosen directly by the person filling in the form.
Referencing What EVIDE Does Not Hold
External Evidence References

An external evidence reference lets a Human Structured Intake point to an artifact, a document, a screenshot, a log file, a policy, that stays under the organization’s own control, without that artifact ever being uploaded to or held by EVIDE. Verified in the code: this reuses, without modification, the exact evidence_references[] structure already documented in the JSON Schema Reference - not a parallel or Human-specific mechanism.

This matters because it resolves a genuine and common tension: an organization often needs to preserve a verifiable declaration about a decision, while deliberately avoiding handing a sensitive internal document to any external system. External evidence references let both happen at the same time.

Business example. A Compliance Officer bases a decision on an internal document, POLICY-CREDIT-REV7. The organization keeps that document under its own control. The Human Structured Intake can preserve a declared reference to that policy and, when available, its SHA-256 digest, without EVIDE ever receiving the document itself.
Fields Available Per Reference (all individually optional)
artifact_typeFree-text declared type - e.g. screenshot, pdf, policy_document. Not a fixed enumeration and, in the form, never prefilled: if you do not provide it, the EAR shows «(not declared)».
pointerAn implementation-specific reference to the artifact’s location. EVIDE does not resolve, dereference or fetch it.
declared_originFree-text description of where the artifact comes from.
declared_relationshipFree-text description of how the artifact relates to this decision.
declared_descriptionFree-text human-readable description.
declared_retention_statusOne of persistent_storage, rolling_buffer, unknown. Verified in the code: never set automatically by default, included only if the person actively selects it.
Optional Digest (SHA-256)

A reference can optionally carry a declared SHA-256 digest of the artifact, together with who computed it (hashed_by) and the hash scope (hash_scope): one of full_file (entire file), segment (segment), frame (frame), archive (archive). In the form, the scope is not preselected: it must be chosen. See the dedicated SHA-256 section below for exactly what this establishes and what it does not establish.

Referencing an Artifact’s Integrity
SHA-256

SHA-256 is a cryptographic hash function: it takes any file and deterministically produces a fixed-length digest such that even a tiny change to the file produces a completely different digest. In an external evidence reference, a declared SHA-256 digest allows a later party holding the actual artifact to check whether it matches what was declared at the time of intake.

How it is used in practice: a declared digest can later be compared against a digest freshly computed on an available artifact. If they match, the artifact has not changed since the digest was declared. If they do not match, either the artifact has changed, or it is not the same file that was originally referenced.

Verified in the code: hash validation on this channel is purely syntactic, the server confirms that the declared value is exactly 64 hexadecimal characters, nothing more. EVIDE does not receive the artifact and cannot check whether the declared digest actually corresponds to it. The declared value is preserved exactly as entered, never normalized to uppercase or lowercase.

What a Declared Digest Establishes

  • That this specific digest was declared, by the person submitting the intake, at this specific time.
  • A basis for a later, independent comparison against an artifact held by someone else.

What a Declared Digest Does Not Establish

  • Authorship of the artifact.
  • Provenance of the artifact.
  • The substantive truth or accuracy of the artifact’s content.
  • Legal validity, ownership or originality.
  • That EVIDE possessed, inspected or verified the artifact - it remained external throughout.

The distinction that matters is between five separate things: the external artifact itself (never received by EVIDE); the declared reference to it; the declared digest (optional, checked only syntactically); a later hash comparison that someone else may perform; and EVIDE’s preservation of the declaration - the only one of these five things that EVIDE actually performs.

Boundary of the Claim
What EVIDE Preserves

The general principle: structured preservation of the declaration and its associated declared evidentiary context, exactly as submitted, canonicalized and hashed in a deterministic, tamper-evident way.

Concretely, When Present

  • The declared decision type and closure time.
  • The declared authority context - role, declared identifier, and the verified DAPI identity of the session that made the submission.
  • The declared classification and its stability status.
  • The declared threshold context and its attribution status.
  • The declared trace reference.
  • The declared boundary readiness state and any associated gate information.
  • Any declared unresolved signals.
  • Any declared external evidence references, including an optional declared digest.
  • The linked responses deposited on the record, each as a distinct record of the person who deposited it, with the frozen representation it refers to, the receipt time and its own EAR-LINKED (Linked responses).
Read This Before Relying on Any Record
What EVIDE Does NOT Claim
Putting It All Together
Complete Business Example

Returning to the Compliance scenario from the Enterprise Use Cases: a Compliance Officer, Jane Whitfield, is asked to approve a temporary exception to the standard vendor onboarding checklist, under a documented business justification and a defined review point.

She closes the decision at 16:00 UTC, but records the intake later, at 18:03 UTC, after finishing a call. She declares her role as Compliance Officer, references the internal policy that governs exceptions of this kind, and notes that an internal review board, a mechanism independent of her own decision, confirmed the relevant conditions with complete visibility before she made her decision. She references the internal ticket tracking this exception, and separately declares a policy document with its SHA-256 digest, kept internally rather than uploaded to EVIDE.

Every value below is chosen to be internally consistent and compatible with the conditional rules documented above, fields are included because they fit this specific case, not simply to demonstrate that every field exists.

The Resulting Payload
JSON / Payload Example

This is the canonical payload EVIDE constructs from the example above, verified field by field against the EVIDE validator. Fields generated automatically by the server (never read from the form) are marked accordingly.

"evide_schema": "2.1",
"source_system": "evide_web_human",               // server-generated, fixed for this channel
"source_reference": "web:1042:a3f91c2d",          // server-generated
"source_timestamp_utc": "2026-04-07T18:03:00Z",  // server-generated -- when EVIDE processed this intake

"decision": {
  "type": "Compliance exception approval",
  "status": "finalized",                    // always fixed on this channel
  "closure_timestamp_utc": "2026-04-07T16:00:00Z", // declared -- see Decision Closure above
  "summary": "Temporary exception to vendor onboarding checklist" // copied from the common field "title"
},

"authority": {
  "id": "Jane Whitfield",                     // declared (defaults to the logged-in user if blank)
  "role": "Compliance Officer",
  "dapi_number": "0000000000",               // always server-generated from the session, never from the form
  "verification": "Linked to internal DAPI reference for the review board"
},

"intervention": {
  "classification_status": "stable",
  "classification_context": {
    "threshold_status": "met",
    "threshold_reference": "Internal policy COM-EXC-04, section 3.2",
    "threshold_authority": { "attribution_status": "attributed" }
  },
  "trace": { "access": "Ticket COMP-2026-0417" }
},

"handoff": {
  "reconstruction_independence": "declared",   // fixed
  "submission_status": "not_submitted",         // fixed at the time of intake
  "acceptance_status": "not_claimed",           // fixed at the time of intake
  "boundary_readiness": {
    "status": "verified",
    "visibility_surface": "declared_complete", // derived mechanically from the status above
    "readiness_gate": {
      "identifier": "COM-EXC-04 review board",
      "scope_reference": "Vendor onboarding exceptions, Q2 2026"
    }
  }
},

"extensions": ["evidence_references"],
"evidence_references": [
  {
    "artifact_type": "policy_document",
    "pointer": "internal://policies/vendor-onboarding-v3",
    "declared_origin": "internal policy repository",
    "declared_description": "Policy document supporting this exception approval",
    "hash": { "algorithm": "SHA-256", "value": "cabbcf9f83fb765cd82569e477b6b3abf51d81eba9b3b92f8e9904be98a1a2f8" },
    "hash_scope": "full_file",
    "hashed_by": "internal document management system"
  }
]
Note: unresolved_signals is correctly absent here, it is required only when boundary_readiness.status is verified_partial or unverifiable, not verified as in this example.
Frequently asked questions
The questions we are asked most often

Answers to the questions DPOs, lawyers, auditors and managers ask most often before using Human Structured Intake. Each answer links to the section of this page that covers it in more detail.

Identity, time and integrity
Who appears as the author of a deposit?

An HSI record can only be deposited from an EVIDE account held by the holder of a DAPI identity certification, who signs in with one-time access codes. The depositor’s DAPI number is part of the record and is therefore covered by its hash; in the EAR it appears as “Deposited by (DAPI)”.

The decision-maker and role named in the declaration are declared values: they may or may not be the depositor, and EVIDE does not verify them. Attribution concerns the deposit to the account: it does not prove who physically wrote the text and does not establish legal responsibility.

More: Authority Identifier

Is the deposit time a qualified time stamp?

No. The time of receipt is recorded by the EVIDE server, in UTC, when the deposit arrives, and it is shown in the EAR: it is recorded separately and is not part of the content on which the record’s hash is computed. It is distinct from the closure time of the decision, which is declared by the depositor. It is not a qualified electronic time stamp under the eIDAS Regulation.

On request, the FEDIS receives a qualified electronic time stamp. Under Article 41 of the eIDAS Regulation, a qualified time stamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data to which they are bound: here, the FEDIS document, which attests the state of the record at that date. The time stamp does not prove when the declared decision was taken.

More: FEDIS: qualified signature and qualified time stamp

Does EVIDE keep only the hash, or the declaration too?

It keeps the complete declaration: the completed fields, the references given and the depositor’s DAPI number. The record’s SHA-256 hash is computed on the declaration in canonical form: anyone holding the record can recompute it and check that nothing has changed.

The EAR (Evidentiary Artifact Record) is the readable document that shows the record, the time of receipt and the hashes, and it has a hash of its own.

More: SHA-256

How is the record linked to documents that stay within the organization?

Through an external reference: the identifier or location of the document and, optionally, its SHA-256 hash, stating who computed it and over which portion. The document is not sent to EVIDE, which does not acquire it and does not verify the declared hash.

If the document is produced later, its SHA-256 is recomputed: if it matches the deposited one, the digital content is identical to the content referenced at the time of deposit. A match concerns the content: on its own it does not prove where the file came from or that it was authentic at its origin.

If a file is instead deposited in EVIDE through a separate deposit, EVIDE computes its hash. The file is deleted at the end of the applicable retention period, while the hash remains in the record.

More: External Evidence References

Can a record be changed after it has been deposited?

No. A correction or an update is a new deposit linked to the previous one. Both are kept, each with its own time of receipt and its own hash, and the sequence remains visible.

The time elapsed between the declared closure and the deposit also remains visible: EVIDE neither hides it nor justifies it.

Data and confidentiality
Which data are deposited, and which stay within the organization?

The record contains what is declared in the fields (decision, declared closure time, decision-maker and role, classification, thresholds, uncertainties, references), including the depositor’s DAPI number: the record’s SHA-256 hash is computed on this content. The EVIDE identifier, the time of receipt and the computed evidentiary profile are recorded by EVIDE separately, outside the record’s hash, and are shown in the EAR.

The external documents referenced are not acquired: registers, documents, logs, tickets and communications stay in the organization’s systems. For a data breach, for example, one can deposit the decision to notify or not to notify, with its grounds and uncertainties, referring to the entry in the breach register by its identifier and hash, without including the data subjects’ data.

Before the free-text fields, the app and the web interface remind users not to enter health data, unnecessary third-party data or irrelevant confidential information.

More: External Evidence References

How are personal data and confidential information protected?

The record is not public: it is accessible to the account that deposited it and, if it was deposited for an organization, to the authorized people of that organization. The servers are provided by Aruba S.p.A., in Italy, and the platform can only be reached over encrypted connections.

Informatica in Azienda does not sell, transfer or license the content of deposits and does not use it to train artificial intelligence models; the platform does not send it to external artificial intelligence services. Retention and deletion follow the Privacy Policy: deletion is requested in writing and each request is assessed individually.

The underlying principle remains data minimization: the safest way to protect confidential information is not to deposit it, and to refer to it by its hash.

More: Privacy Policy, sections 5, 7, 9, 11 and 13

Linked responses
Does a linked response prove that the recipient received or read the documents?

No. EVIDE keeps the position the invited person declares on a FAST REVIEW representation of the record. EVIDE records the creation of the invitation, not its delivery: the link is shared by the person who invites.

The events the platform observes, such as the opening of the link, do not prove that a page was displayed, read or understood, and acknowledging the information notice is not consent. The position I ACKNOWLEDGE WITHOUT EXPRESSING AGREEMENT (PRENDO ATTO SENZA ESPRIMERE ACCORDO) is likewise a declaration by the person who makes it, not technical proof of reading. The response does not concern the external documents cited in the record, which the invited person does not receive.

A declared acknowledgement is not technical proof of reading.

More: How Linked Responses Work

What exactly does the invited person see?

A FAST REVIEW: a representation of the record generated by the platform from a fixed template, without artificial intelligence, frozen at the time of the invitation with its identifier and its hash. The invited person does not receive the complete record or the external documents it cites, and the response refers to that specific representation.

The FAST REVIEW text is currently in Italian; the positions and the information notices are available in five languages.

More: How Linked Responses Work

Who can see the responses, including when they contain objections?

The person who responded always sees their own responses; the depositor sees them as long as they have access to the record. For an organization’s record, the person who invites can choose, when creating the invitation, that the response is also visible to the organization’s current members; former members do not see it. The invited person reads this indication before depositing, and the visibility stays the same for their later responses on the same representation.

A response can be included in a FEDIS-LINKED delivered to third parties only if it was deposited after the respondent was shown the FEDIS-LINKED information notice. When objections or personal data are sensitive, it is advisable to choose the most restricted visibility and to write only what is needed.

More: How Linked Responses Work

What happens if the invited person does not respond, or the invitation expires?

The invitation expires after 30 days. Expiry, revocation and suspension prevent new responses, but they do not change or delete those already deposited.

An invitation without a response is not a fifth position and does not amount to agreement: it does not say whether the invitation was received, read or ignored. In the FEDIS-LINKED, invitations without a deposit appear only as counts, without names or content.

More: How Linked Responses Work

Can a person change their position later?

Yes, by depositing a new response that declares whether it replaces or supplements the previous one. The previous response is kept with its own time of receipt and its own hash, and the depositor of the record cannot change or delete it.

The summary shows each person’s current position: it is an overview of individual declarations, not a vote or a measure of consensus.

More: How Linked Responses Work

Documents and limits
What is the difference between EAR, EAR-LINKED and FEDIS-LINKED?

The EAR documents the deposit of an HSI record; the EAR-LINKED documents a single linked response and is generated for every response. Both are produced by the platform.

The FEDIS-LINKED is instead a professional document issued on request: only the depositor of the record can request it, with the same procedure and the same economic conditions as any FEDIS. It documents the record and the includable responses present in its snapshot; when it is generated the platform recomputes the hashes and, if one does not match, the document is not generated. A forensic expert examines it and signs it with a qualified electronic signature, and the document receives a qualified time stamp.

More: FEDIS-LINKED

Does HSI prove that the decision was correct?

No. HSI documents what was declared, from which account, when EVIDE received it and that the record has not been altered. It does not establish whether the decision was correct, lawful or appropriate, and it does not verify the truth of what was declared.

The assessment of the merits, and the weight to give the record as evidence, rest with whoever has to decide: supervisory authority, court, internal bodies.

More: What EVIDE Does NOT Claim

Is a demonstration available?

Yes. Screenshots of the EVIDE Mobile app are in the section at the top of this page. For a live demonstration, write to app@certifywebcontent.com.

More: EVIDE Mobile, screen by screen


Related documentation:
JSON Schema Reference - the full payload schema, including evidence_references and the declarations extension shared with EVIDE ANCHOR.
API Reference - endpoints and operational profiles.
Architecture Guide - architectural rationale and design principles.

Human Structured Intake exists so that a declared human decision, and its declared evidentiary context, can survive outside the system that produced them, independently retrievable, deterministically hashed, and time-anchored.

EVIDE preserves that a decision was declared.
It does not decide whether the decision was right.