Continuous Compliance & Audit
A useful audit trail connects an agent's actions to the information behind them. Lightspeed builds that record into execution and lets resident agents keep checking the systems around it.
When an agent has worked on a task for three months, a final answer is only part of the story. A reviewer needs to understand what it was asked, which information it used, what it did, and where a person intervened.
Lightspeed records those steps as the work happens. The same history that lets a session recover after a restart gives reviewers a record they can follow afterwards.
A record built into execution
Every session has an event log. Messages, model results, tool calls, returned results and control decisions become part of that history. The agent’s state is reconstructed from these recorded events.
For example, a reconciliation agent might report a duplicate batch. Its session history connects that conclusion to the queries it requested and the results it received. A reviewer can inspect the evidence behind the finding and compare it with the source system’s own records.
Large outputs and files are stored separately and referenced from the history. This keeps the workflow lightweight while preserving the material needed to understand the work.
Follow who asked and who acted
Session records identify their creator, and events attribute requests to start, steer or cancel work. Delegated agents retain their connection to the parent that requested them. A review can follow a piece of work from its original request through the specialists that contributed to it.
The Platform also keeps a separate access history for events such as membership changes, key operations and permanent session deletion. The documentation describes the coverage of each record. Together with the business workflow and source systems, these records support a more complete review.
Keep the evidence with the result
Reports and source extracts can live in persistent virtual workspaces, available after an execution machine has been shut down. Immutable file references identify the exact version a reviewer received, even if the working document changes later.
That makes the handoff concrete: here is the finding, here is the report, and here are the recorded steps that produced it. Retention can then be planned around the evidence the organisation needs to keep.
Make checking a recurring job
Control monitoring is well suited to resident agents. A bot can wake on a schedule, inspect systems through approved tools, compare what it finds with the expected state, and send a summary to the control owner.
Consider a nightly access review. The agent collects the current assignments, flags changes, saves its report and asks for review where needed. The following night it repeats the check. Each run has its own recorded inputs and results, so the monitoring process can itself be examined.
The organisation still owns the control and decides what evidence is sufficient. Lightspeed supplies a durable way to perform the checks and keep their results connected to the work.
Read next: Govern Long-Running Agents for ownership and supervision. For the underlying records and their coverage, see the audit documentation.