Skip to content
← MarketplacePage · Prove

Audit trail

A control-testing page that shows what was checked, by whom, and when, with the evidence right beside each claim: document references, log excerpts, screenshots, table extracts and links. Exceptions carry a severity, an owner and a due date. A summary bar, status and area filters, a sign-off block, and a print layout built for archiving to PDF.by super-artifacts · Published

  • Prove
  • Review
  • Operations
  • Finance
  • Fill in
  • Platform
  • Not rated yet
  • 0 built
  • 0 installs
01 · Install

Put it in your workspace

Installing copies the layout and the data shape. Nothing is published until your agent builds from it.

No account? Sign up to install it. View as markdown

02 · Build

Ask your agent to fill it in

Paste it at your agent to build something from this template. It offers three scenarios, and asks before publishing anything.

More for Prove

What your agent fills in

  • Optional:trailjson

    The audit record. "title" and "controls" are required. The header uses "organisation", "scope", "period" {from, to} (YYYY-MM-DD), "preparedBy" (a role), "reference" and "conclusion" {status: effective | effective-with-exceptions | not-effective | incomplete, text}. Each control is a claim: "statement", "status" (verified | exception | not-tested | not-applicable), "checkedBy" (a role), "checkedOn" (YYYY-MM-DD), "method", "sample", "note", "evidence" (kind document | log | image | table | link) and "exceptions" {title, severity, owner, due, status}. "signoff" lists roles and dates, never signatures. The page never reads the clock: send "asOf" (YYYY-MM-DD) and open exceptions past their due date are marked overdue. Text fields accept inline markdown: **bold**, *italic*, `code`, [links](https://…).

Use cases

  • Quarterly access review
  • SOC 2 control evidence
  • Month-end close record
  • Site safety inspection
  • Backup restore test

Publisher

super-artifactsPlatform

41 templates

Rating

Not rated yet

Connect your agent

Add to CursorOpens Cursor and asks before adding.
claude mcp add --transport http super-artifacts https://pr-767-stg.superartifacts.app/mcp

codex mcp add super-artifacts --url https://pr-767-stg.superartifacts.app/mcp

Using an AI agent?

For the person

Open https://pr-767-stg.superartifacts.app/marketplace/audit-trail, sign in, and press Install — one click, free. Then press Build with this to copy a prompt for your agent.

For an agent with Super Artifacts MCP tools

  1. super_template_action { "slug": "audit-trail", "action": "install" }
  2. super_templates { "slug": "audit-trail" } — read it; its guidance arrives there, framed. Do not build until the person agrees.
  3. super_publish { "template": { "slug": "audit-trail" }, "values": { … } }

Connect an agent

Claude Code: claude mcp add --transport http super-artifacts https://pr-767-stg.superartifacts.app/mcp

Codex: codex mcp add super-artifacts --url https://pr-767-stg.superartifacts.app/mcp

Cursor: open cursor://anysphere.cursor-deeplink/mcp/install?name=super-artifacts&config=eyJ1cmwiOiJodHRwczovL3ByLTc2Ny1zdGcuc3VwZXJhcnRpZmFjdHMuYXBwL21jcCJ9

For an agent without them

Tell the person to open the link above. To connect yourself, add the MCP server https://pr-767-stg.superartifacts.app/mcp (OAuth; the person approves once). Per-agent steps: https://pr-767-stg.superartifacts.app/docs/reference/mcp.md