# Signed proof for every decision.

> Product page for Audit and Attestations: every agent run becomes a signed record (its AI BOM, the rules it was checked against and how each one came out) that maps to compliance frameworks and can be handed to an auditor as is.

- **URL:** https://aisquare.studio/product/audit
- **Audience:** Risk, compliance and internal audit teams who must evidence agent decisions, and the engineers who answer their questions
- **Topics:** AI audit, audit trail for AI agents, attestations, signed decision records, tamper-evident, AI BOM, AI bill of materials, CycloneDX, DSSE, in-toto, compliance packs, EU AI Act, OWASP Top 10 for LLMs, NIST AI RMF, ISO/IEC 42001, SR 11-7, compliance API

## Audit and Attestations

Signed proof for every decision.

Every run becomes a signed record: its AI BOM (AI Bill of Materials), the rules it was checked against and how each one came out. Hand it to your auditor as is.

Example from the page. Agent decision: $1,250 refund blocked. Sent for manager approval. Rule 4.2 · refund cap $500.

Reasoning, run 8823 · support agent · refund.create, "Why the $1,250 refund was blocked" (4 claims · 1 unsupported):

- Customer identity verified: ID check, session 8823 (Supported)

- Outage fell inside the SLA window: Status incident INC-2291, Sep 12 (Supported)

- Customer is owed $1,250: Assumed from 3 days of downtime (Assumption)

- $1,250 is within the refund cap: Rule 4.2 caps refunds at $500 (Unsupported)

Attestation: Signed by AISquare Runtime, signed and tamper-evident. Key ID: ais-runtime-key-01. Signed at: Sep 12, 2026 · 14:32 UTC. Decision: Blocked, sent for approval. Rules: 4.2, sla.window, privacy.pii. Evidence: Ticket 8823, INC-2291. AI BOM entry sealed.

## When an auditor asks why, logs can't answer.

Logs show what an agent did. They can't prove why, or that nothing changed since.

Audit request, Refund 8823 · Sep 12:

- Which model made the decision? Unknown

- Which prompt was live? Unknown

- Which rule applied? Unknown

- Has the record changed since? Can't tell

Rebuilt by hand from logs, weeks later. Editable, so not evidence.

## Four layers, sealed together.

- AI BOM: What the agent used: model, system prompt version, tools and tool calls.

- Verdicts: Each rule it was checked against, the version that was live, and the result.

- Reasoning: The claims the agent made and the evidence behind them.

- Signature: Every rule verdict and the run itself are signed and tamper-evident. Change anything and verification fails.

What's inside an AI BOM (Run 8823 · Support agent; Export · CycloneDX, or JSON):

- Model: gpt-4o-mini (Provider and version recorded)

- System prompt: v7 (Version recorded)

- Tools called: crm.lookup, status.incidents, refund.create

- Data used: Refund policy 4.2, Ticket 8823, INC-2291

- Rulebook: Support Rulebook v4

## No audit project. The run documents itself.

Time from decision to evidence:

- Compiled after the fact: Weeks pass, Questionnaires, Evidence hunt, Report (weeks later)

- AISquare: Sealed with the run (Signed)

Evidence is written while the agent works, not reconstructed weeks later.

## See each record against the frameworks you answer to.

Map the same signed records to the frameworks your auditors ask about.

- EU AI Act: High-risk AI obligations

- OWASP Top 10 for LLMs: LLM application risks

- NIST AI RMF: AI risk management

- ISO/IEC 42001: AI management system

- SR 11-7: Model risk management

- DoD AI principles: Responsible, traceable, governable

- Your internal controls: Your own policies and SOPs

And more, mapped to the same signed records.

Example · EU AI Act pack (Support agent · last 30 days):

- Art. 12 Record-keeping: Every step of every run, recorded and signed (Covered)

- Art. 13 Transparency: Reasoning for each decision in RML (Covered)

- Art. 14 Human oversight: Rules, corrections and escalations to your team (Covered)

- Art. 15 Accuracy and robustness: Rule verdicts and failures across runs (Covered)

- Incident reconstruction: Reopen and replay any past run (Covered)

- Art. 9 Risk management: Your risk process, with run evidence attached (Needs your input)

The evidence layer, not a certificate. No tool makes you compliant on its own. AISquare gives your auditors the records, mapped to the frameworks they check.

## Hand it over without a fire drill.

- Export one or many: Export a single record or a whole set of runs at once.

- Share with auditors: Give your auditor access to the records they need to review.

- Verify anywhere: Anyone can check that a record hasn't changed since it was signed.

Export formats: PDF, JSON, DSSE / in-toto, CycloneDX AI BOM.

## One record. Every reviewer.

- Risk and compliance: Sign off with evidence, not assurances. See every decision against your compliance packs.

- Internal audit: Sample any decision and read it end to end. Check the signature yourself.

- Engineering: Reconstruct what happened, step by step. Fix what keeps failing with Learnings.

## Pull your compliance summary over the API.

curl -s -H "X-API-KEY: $EXPLAINABILITY_API_KEY" "$EXPLAINABILITY_GATEWAY_URL/v1/studios/$STUDIO_ID/policy/compliance"

Returns the recent compliance rate, violations and the rules that fail most.

Per-run verdicts are on the Policy Engine page.

## Questions, answered.

- What is a decision record? A signed record of one agent run: what it used, which rules it was checked against, the result of each, and the reasoning behind it.

- What exactly is signed? Each rule verdict and the run itself. Both are tamper-evident, so any later change fails verification.

- What is an AI BOM? The record of the model, system prompt version, tools and tool calls a run used. Exportable as CycloneDX.

- Which formats can I export? PDF, JSON, DSSE / in-toto envelopes and a CycloneDX AI BOM.

- Can I export many runs at once? Yes. Export one record or a whole set of runs.

- Can I share records with an auditor? Yes. Give your auditor access to the records they need, and they can verify each one.

- Which frameworks can I map to? Compliance packs include the EU AI Act, OWASP Top 10 for LLM applications, NIST AI RMF, ISO/IEC 42001, SR 11-7 and the DoD AI ethical principles, plus your own internal controls.

- Does this make us compliant? No tool does that on its own. AISquare gives you the evidence layer: signed records mapped to the frameworks your auditors check.

## Follow the evidence.

- Policy Engine: See how rules are enforced before an action goes out.

- RML and Explainability: Read the claims and evidence behind each decision.

- Learnings: Turn repeated failures into approved improvements.

## From the blog

- [AI Audit Trail: What It Is and What Auditors Ask For](https://aisquare.studio/blogs/ai-audit-trail)

- [What Is an AI BOM? The AI Bill of Materials Explained](https://aisquare.studio/blogs/ai-bom)

## Give your auditors proof, not logs.

Every decision your agents make, signed and ready to hand over.

## Links

- [Book a demo](https://calendly.com/d/dws4-msf-8jc/aisquare-gtm-team)
- [Read the docs](https://docs.aisquare.studio/docs/reference/compliance)
- [Policy Engine](https://aisquare.studio/product/policy-gates)
- [RML and Explainability](https://aisquare.studio/product/reasoning-graph)
- [Learnings](https://aisquare.studio/product/learning-layer)
- [AI Audit Trail: What It Is and What Auditors Ask For](https://aisquare.studio/blogs/ai-audit-trail)
- [What Is an AI BOM? The AI Bill of Materials Explained](https://aisquare.studio/blogs/ai-bom)

---

**Machine-readable AISquare**

- Site index for LLMs: https://aisquare.studio/llms.txt
- Agent instructions (when to use AISquare): https://aisquare.studio/agents.md
- OpenAPI specification: https://aisquare.studio/openapi.json
- MCP endpoint (Streamable HTTP, POST): https://aisquare.studio/mcp
- Sitemap: https://aisquare.studio/sitemap.xml
- Blog feed (RSS, full posts): https://aisquare.studio/blogs/rss.xml
- Any page on this site also serves markdown: append `.md` to its path (the homepage is `/index.md`) or send `Accept: text/markdown`.
