Documenting the workflow
Documenting the workflow means recording what happened: who assigned the task, which zone was assigned, what was restricted and what decision was made. AiTrust provides an evidence trail for operations in the controlled path. The organization sets the evidence retention period.
- Intent
- Input control
- Authorization
- AI
- Result validation
- Human
- Evidence (applies)
Highlighted: the points of the flow that this description refers to. Orange marker: a human decision at this point.
What the record covers
The record makes it possible to reconstruct the workflow after the fact: for a review, an incident investigation or an audit. The scope of the record of events and decisions is set for the configuration and the path it covers.
- Evidence trail
- An ordered record of events and decisions in the controlled path. Actions outside it, e.g. from a private account, are not recorded in it.
- Send report
- A summary of the check attached to the model’s response: the zone, the decision and the number of redactions, that is, masked fragments of the content.
- Event log
- A list of events with the time, type, user and zone. In the view shown, it can be filtered and exported to CSV, Excel or PDF.
- Chain verification
- The “Verify chain” button in the logs view recalculates the SHA-256 hash chain of the organization’s events: each entry contains the hash of the previous one, and the result points to the first place where the chain is broken. The hash covers the basic fields of an entry (identifier, type, category and time), so the check reveals the deletion or replacement of an entry in the range checked; it does not prevent changes and does not replace external attestation. The organization assesses the evidential value of the record.
- Retention
- How long records are kept. The organization sets the evidence retention period, taking into account legal obligations and the data minimization principle.
A run record is not a DPIA
A run record is not a data protection impact assessment (DPIA) or a legal opinion. It can be one of the materials for an audit. There is more on the AI Governance page, in the part on audits.
Conditions, transitions and decisions
Diagram of the controlled run
- Step 1: EventAn instruction, a check, a decision or a result in the controlled path.
- Step 2: RecordThe event goes into the log with the time, type, user and zone.
- Step 3: VerificationThe logs view offers chain verification; its scope is confirmed for the given deployment.
- Step 4: Review and exportAn authorized person filters the events and exports the selected range.
- Step 5: RetentionRecords are kept for the period set by the organization.
The report with the response and the event log
The first screenshot comes from the recorded complaint run; the second is a separate example. Both show AiTrust on synthetic data.
Send report with the response
Below the draft reply to the complaint, you can see the “AI send report” bar: zone D, redact decision, 3 redactions. The user sees the conditions under which the response was produced without opening the log.
We show the whole run in the Boundaries in the workflow example.
The “Audit logs” view
A separate example, unrelated to the complaint run. You can see the filters (user, event type, zone, date range), export to CSV, Excel and PDF, the “Verify chain” button and a list of document processing events with zones A and B.
User identifiers were masked for publication.
What the screenshots show
- The send report attached to one result.
- The log view with filters, export and the chain verification button in this example.
What the screenshots do not prove
- The result of chain verification (the screenshot shows the button, not the outcome).
- The contents of the exported files.
- The completeness of the record in other configurations, or events outside the controlled path.
Sample exported report
An export from the application on synthetic data, for comparison with what an organization receives from the logs view, will be made available among the materials for verifying it yourself.
Related areas
Methodologies and compliance
In the platform description
Let’s discuss the scope of the record for your processes
In the demo, we will show the send report and the event log on synthetic data and discuss the scope of the record and the retention period for your organization.