Run evidence and a tamper-evident log
flintspark keeps two records. Every run keeps its steps and evidence so a reviewer can see why Flint, flintspark's agent, did something. Approvals, take-overs and other safety events also go into a separate append-only audit log, where each entry carries the hash of the one before it.
- Run recordSteps, what Flint looked at, the rule, the decision and the evidence. Not hash-chained. 90 days by default
- Audit logApprovals and safety events. Append-only and hash-chained
What is recorded for each run?
Each step of a run stores what Flint looked at, the rule that fired, the decision it made and the evidence for it. The attempt at each route is kept too, so a reviewer can see which route did the work and how long it took.
Everything stored has already been through redaction.
Run record · step 3 of 5
- Looked at
- The order list page, redacted
- Rule
- Stock below the reorder level
- Decision
- Prepare the request needs approval
- Evidence
- Screenshot and the values read
- Route
- Allow-listed read · 1 attempt
What is hash-chained, and what is not?
Approvals and safety events are. Run steps and evidence are not. Each log entry carries the hash of the entry before it, so a later edit to a past entry breaks the chain after it and can be detected.
The chain shows that a change happened. It does not by itself stop a person with database access from making one.
flintspark's audit log is not a validated GxP or 21 CFR Part 11 system.
In the hash-chained log
- Approval decisions
- Grant mints and checks, replays included
- Take-overs
- Trust-mode switches
- Live-demo confirmations
- Redaction drops and purges
- Session claims and bridge connections
In the run record only
- Each step of a run
- What Flint looked at
- The rule that fired
- Screenshots and other evidence
How long are records kept?
Run records are kept for 90 days by default. The period is set in configuration, not in code, and the audit log has its own setting.
A nightly maintenance job removes what has expired, along with stored files nothing refers to any more, and each purge is written to the audit log.
Retention · defaults, set in configuration
- Run records
- 90 days
- Stored files
- 90 days
- Teach recordings
- 30 days
How does a reviewer trace a decision?
From the run to the step, and from the step to the decision and its evidence. An approval links back to the exact action it covered.
Decisions can also be searched across runs, by words or by meaning, so a reviewer can find what happened days later.
- Start at the run: its status, its steps and who answered each question.
- Open a step: what Flint looked at, the rule that fired and the screenshot.
- Open the decision: what was decided and why.
- For an irreversible action, open the approval and the audit entries for its grant.
What is decision memory?
The stored record of each run: what happened, what was decided and why, with its evidence. It lets a reviewer see why Flint did something, days later.
When a person answers a question, the answer is kept as a preference. The next run prefills the question, and the person confirms with one click. Decision memory is part of the run records, so it is kept for the same period and is not in the hash-chained log.
Question · prefilled
Which supplier should the request go to?
Suggested from 3 earlier answers. Confirm or change it.
Questions about this page
Can a past approval be edited without anyone noticing?
Not without a trace. The audit log is append-only and each entry carries the hash of the entry before it, so changing a past entry breaks the chain after it and the change is detectable. The chain shows that a change happened; it does not by itself stop a person with database access from making one.
How long does flintspark keep run records?
Run records are kept for 90 days by default, and the period is set in configuration. A nightly maintenance job removes expired records and stored files, and each purge is written to the audit log. Teach recordings have their own, shorter setting.
Where can I see why Flint chose an action?
On the run. Each step shows what Flint looked at, the rule that fired, the decision it made and the evidence. Decisions are also searchable across runs, so a reviewer can find a past decision days later without opening each run.
See Flint run
Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.
We reply from hello@flintspark.ai.