Audit Trail Actions Are Past-Tense Verbs

One readable action per Audit Trail entry

Plans: Plans that include the Audit Trail (The Growth and above) Where: Audit Trail, the Evidence Log, CSV and PDF exports, the API (action.code)

Who benefits: CTOs, IT managers and auditors who read the Audit Trail as evidence.

Actions used to be a mix of styles, such as supplier.template.updated, evidence_uploaded and AI_ACCESS_*. Every entry now shows a single past-tense verb (Created, Updated, Removed, Uploaded and so on), and the Subject Type column says which kind of record it applied to. New entries from all parts of the product are recorded this way, and older entries are displayed under the same verbs.

How to use it

1. Click Audit Trail and open the Action filter. It lists verbs only.
2. Pick a verb and click Apply. You also get older entries that were stored under a longer code. The API filter filter[action][eq]=updated behaves the same way.
3. Need the stored originals? The full audit trail export (a .jsonl.gz file) keeps the raw codes exactly as written.

Stored entries are not changed, so hash chain verification gives the same result as before. action.group is unchanged. See Audit Trail Integrity and Accepted Link Breaks.