Documentation

Governed AI Records

View as Markdown

Clear Ideas keeps AI activity inside the same governed environment as your approved documents and collaboration history. This makes AI work more reviewable than disconnected prompting in outside tools.

What Becomes Part of the Record

Depending on the feature, governed AI records can include:

  • AI chat history
  • archived chats
  • workflow definitions
  • workflow jobs
  • MCP evidence sessions
  • MCP answer-with-citations responses
  • MCP content reads and summary reads
  • workflow outputs
  • generated files from chats and workflow jobs
  • saved AI responses written back into Sites

Why This Matters

Governed AI records help teams:

  • keep AI work close to the system of record
  • review what was asked, run, or produced later
  • preserve repeatable operating procedures
  • support audit-ready operations over approved documents
  • verify exported evidence without sending the export back to Clear Ideas

Common Examples

AI Chat

Chats and archived chats remain available for later review and can support repeatable knowledge work.

AI Workflows

Workflow definitions and jobs provide a record of what process ran, when it ran, and what it produced.

Saved Outputs

When a chat response or workflow output is saved back into a Site, it becomes part of the governed workspace alongside the approved source material and related work product.

MCP Activity

MCP integrations can also create governed evidence when an external assistant is given document content, file summaries, retrieved context, or an answer generated with citations.

Clear Ideas does not treat every MCP operation as evidence. Discovery operations such as listing sites, listing content, searching, creating folders, or saving files remain in the normal audit trail with MCP correlation metadata. Governed MCP evidence focuses on what information was actually provided to AI context, such as file text, retrieved chunks, summaries, and cited answers.

MCP transport sessions remain stateless for resiliency across web workers. Evidence sessions are durable Clear Ideas records, and explicit MCP session ids are used when a client provides them.

Generated Files

Generated spreadsheets, documents, presentations, and images are governed outputs. They remain connected to the chat or workflow job that produced them and can be included in evidence exports as binary files, not only as text references.

Signed Evidence Exports

Organization administrators can export governed AI evidence from Audit & Governance > Governance Activity. Evidence exports are designed for audit, replay, internal investigation, or external review, not everyday browsing.

When evidence signing is enabled, Clear Ideas adds Ed25519 verification material to the export bundle:

  • a signed export receipt covering the bundle manifest and exported files
  • a bundled public key registry snapshot
  • receipt metadata that identifies the signing key
  • byte hashes for exported evidence files
  • binary generated files, such as .xlsx, .docx, .pptx, and generated images, when they are part of the selected governed record
  • MCP evidence bundles for governed content reads, summaries, retrieved context, and answer-with-citations activity
  • chain metadata for governed records when available

This lets reviewers detect whether evidence files were removed, changed, or replaced after export.

Verify an Evidence Export

Use Verify Evidence Export on Audit & Governance > Governance Activity to check a downloaded evidence ZIP in your browser.

The verifier:

  1. Reads the ZIP locally in the browser.
  2. Finds the manifest, export receipt, public signing key, and governed evidence files.
  3. Verifies the Ed25519 signature against the bundled key registry.
  4. Compares the manifest and exported file hashes against the signed receipt.
  5. Checks governed record chain continuity when chain data is available.

The ZIP is not uploaded during verification. The check runs client-side so a reviewer can validate evidence without creating another server-side copy of the bundle.

Verification Results

A successful check confirms that the signed receipt, manifest, exported files, and available chain metadata match. A failed check usually means the ZIP is not a Clear Ideas evidence bundle, a required verification file is missing, the signing key is unavailable, or one or more exported files no longer match the signed receipt.

The verifier also shows the key used for verification and the key status details included with the export, such as issuer, key status, and not-before metadata when present.

Public Key Registry

Clear Ideas also exposes the current governance signing public keys at:

/.well-known/clearideas-governance-keys.json

Evidence ZIPs include a registry snapshot so the normal verification path can run offline from the export itself. The well-known endpoint is useful when a reviewer wants to compare the bundled key information with the current published signing keys.