# Audit and evidence · Neural Inverse Govern > One append-only log of every change and every enforced decision, chained per organisation, signed every minute and verifiable offline, with evidence toward the frameworks you report against. Source: https://neuralinverse.com/govern/audit/ --- ![](/photos/facility.jpg) [Neural Inverse Govern / Audit and evidence](https://neuralinverse.com/govern/) # A record your auditors can verify without trusting us. One append-only log of every change and every enforced decision, chained per organisation, signed every minute and verifiable offline, with evidence toward the frameworks you report against. Chain HMAC-SHA256 per organisation Seals Signed every minute Verification Offline, standalone verifier Retention Hot, cold and archive tiers Standards Evidence toward your frameworks Overview Regulated organisations have to show what happened, who did it and that the record was not changed afterwards. Govern writes every change and every enforced decision to one append-only log in the same transaction as the change, chains it per organisation, seals it with signatures, and lets you verify it yourself, offline, with keys published by your own installation. Certification stays with your organisation and its assessor. [What it does ↓](https://neuralinverse.com/#capabilities)[How it works ↓](https://neuralinverse.com/#workflow)[Enforced and recorded ↓](https://neuralinverse.com/#enforcement)[Where it runs ↓](https://neuralinverse.com/#where)[Get started ↓](https://neuralinverse.com/#get-started) What it does ## What the audit record holds, and how you prove it. One ledger, signed exports, retention you control and the records around it. - **Written with the change:** Every change and every enforced decision is written in the same database transaction as the change. If the entry cannot be written, the change does not happen. - **Hash chains:** Each organisation has its own HMAC-SHA256 chain, so removing, reordering or changing an entry breaks it. An organisation that needs one strict order for every entry can choose a single chain. - **Signed seals:** Every minute the heads of the chains are sealed into a Merkle root signed with Ed25519, and every five minutes a signed checkpoint is made. Holding the chain key is not enough to rewrite history unnoticed. - **Immutable rows:** The database refuses any update or delete of audit entries, apart from the verified move of old entries to the cold tier. - **What an entry holds:** Organisation, actor, action, resource, outcome, verified client address, request id, region and project. Request bodies, credentials and tokens are never captured. - **Query both tiers:** A query language reads recent and archived entries together. A query that would be too wide is refused whole, never answered partially. - **Signed exports:** NDJSON or CSV exports of any time window, with a manifest signed with Ed25519 that names the file's hash and its place in the chain. Anyone holding the file can check it. - **Offline verification:** A standalone verifier checks an exported chain and archived segments with no network access and no connection to Govern, for air-gapped sites and external auditors. - **Your own entries, alone:** An organisation can download its own archived segments and prove its entries complete and in the chain, without anyone else's data and without the operator's chain key. - **Retention tiers:** Recent entries stay in PostgreSQL. Older entries move to your S3-compatible bucket as signed segments under your KMS key, and can be archived under Object Lock in compliance mode. Retention can be lengthened, never shortened. - **Legal holds:** A legal hold on an organisation or a person keeps the organisation's entries in the hot tier. - **App activity:** The Neural Inverse Editor, Agents app and CLI record a signed-in person's actions in the same chain, with identity taken from the token, a strict schema and DLP applied. - **Vendor audit records:** Audit and usage records pulled from AI vendors' APIs or pushed by tools are kept beside Govern's own, with their own read interface and signed exports. - **Compliance rule packs:** Rule packs check your organisation's state for evidence toward SOC 2, ISO 42001, the EU AI Act, GDPR, HIPAA and other frameworks, and store findings and evidence records for your assessor. - **Access review evidence:** Every campaign's items, decisions, reviewers and times, with the audit entries behind them. - **Context evidence:** Which context fed each AI request, which model call used it and which agent instructions a session started with, in a separate chain verified daily. How it works ## From a change to proof an auditor can check. 1. Write The entry is written in the transaction of the change, or the change fails. 2. Chain It is linked to the previous entry of its organisation's chain. 3. Seal Chain heads are sealed and signed every minute, with a checkpoint every five. 4. Tier Older entries move to your bucket only after they are written, read back and matched. 5. Export A time window is exported with a signed manifest. 6. Verify Your auditor checks the chain, the seals and the archive offline. Who uses it ## Built for every role that answers for AI. - **Compliance teams:** Export evidence for a period, run rule pack checks and record evidence for each control. - **External auditors:** Verify exported chains and archived segments offline, with the public keys of your installation. - **Security operations:** Query who did what, with which tool and under which rule, across recent and archived entries. - **Operators:** Keep the chain and signing keys stable, configure tiering and run the platform verification. Enforced and recorded ## What the ledger guarantees, and what it only reports. Some records are proven by Govern itself. Others are what an app or a vendor reported; they are labelled as such. Enforced - **No change without a record:** A change whose audit entry cannot be written does not happen. - **Fail toward keeping:** An entry leaves PostgreSQL only after the object holding it was verified. A range whose chain does not verify is never archived. - **No delete:** Govern has no delete operation on the audit bucket, and its identity needs no permission to delete. - **Integrity on delivery:** An export file that no longer matches its manifest is never delivered, and an archived object that does not match refuses the query. Recorded - **App activity:** Attested by the app, not proven by the server. A modified app can misreport its own events, but not who it is or in whose name. - **Vendor records:** Show what the vendor reported. They give Govern no control over the vendor's service. - **Compliance findings:** Checks count records; a pass means a check found what it looks for, not that a control is met. The audit package carries a hash, not a signature; use a signed export for signed evidence. Govern produces evidence toward the controls of frameworks such as SOC 2, ISO/IEC 27001, ISO/IEC 42001, HIPAA and the EU AI Act. It does not certify your organisation; certification stays with you and your assessor. Where it runs ## Your database, your bucket, your keys. [Deployment options](https://neuralinverse.com/deployment/) - **Hot tier:** PostgreSQL, protected by the immutability trigger. Without a bucket, the whole log stays here. - **Cold and archive tiers:** An S3 or S3-compatible bucket with versioning, Object Lock and server-side KMS encryption. An on-premises store with Object Lock works air-gapped. - **Keys:** The chain key and the master key that seals the signing keys stay with your operator. Public keys are published by your installation. - **Hosted by us:** We run it for you; the hot window and archive retention come from your edition. Get started ## Set it up with the documentation. - [Evidence](https://neuralinverse.com/docs/evidence/) - [The audit ledger](https://neuralinverse.com/docs/evidence/audit-ledger/) - [Verify offline](https://neuralinverse.com/docs/evidence/verify-offline/) - [Exports and signed packages](https://neuralinverse.com/docs/evidence/exports/) - [Retention and tiering](https://neuralinverse.com/docs/evidence/retention-and-tiering/) - [Client events](https://neuralinverse.com/docs/evidence/client-events/) - [Vendor AI audit connectors](https://neuralinverse.com/docs/evidence/vendor-connectors/) - [Push receivers](https://neuralinverse.com/docs/evidence/push-receivers/) - [Compliance rule packs](https://neuralinverse.com/docs/evidence/compliance/) - [Audit log](https://neuralinverse.com/docs/govern/audit/) Related [Identity and access → Single sign-on, provisioning, least-privilege roles, just-in-time access and reviews.](https://neuralinverse.com/govern/identity/)[Third-party AI tools → The control level Govern has over each third-party AI coding tool.](https://neuralinverse.com/govern/third-party-tools/)[Context for agents → Governed, attributed context from your code, issues and team knowledge.](https://neuralinverse.com/govern/context/) ![](/photos/team.jpg) ## Talk to our team. Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation. [Request access](https://neuralinverse.com/contact/?topic=access)[Contact us](https://neuralinverse.com/contact/)