Evidence Pack Sample

Proof, not promises.

See the structure of the evidence PalmerAI produces when requests or documents are controlled, approved, blocked, and recorded under policy. The point is not to dump raw data. The point is to show a decision record that a buyer, auditor, operator, or partner can understand quickly.

What the evidence shows

  • Policy snapshot
  • Request or document summary
  • Inspectability state
  • Detected classes
  • Decision and reason codes
  • Approval record
  • Audit timeline
  • Hashes and timestamps

Decision evidence view

Policy version The evidence record keeps the policy context that shaped the outcome.
Decision Allowed, approval-required, or denied status is explicit and reviewable later.
Reason codes Decision rationale is visible without exposing raw content by default.
Hashes File and evidence integrity markers make the record usable in audit and assurance reviews.
Evidence orientation

This page is structured like a decision-evidence sample, not a dashboard screenshot dump.

Why evidence beats raw logging

Raw logs are noisy, hard to review, and often contain either too little decision context or too much risky detail. PalmerAI evidence is designed around reviewability: what entered, what policy applied, what decision was made, who approved it, and what supporting integrity markers exist.

Who this is for

  • Buyers evaluating whether the governance story is real
  • Auditors and security reviewers checking decision evidence
  • Operators and customer admins validating approval flow
  • Partners who need tenant-safe reporting without raw content leakage

Sample Structure

Policy snapshot

Tenant, use case, policy version, and the relevant document-control or request-control settings that shaped the outcome.

Entity summary

Request ID or document ID, file metadata, hashes, timestamps, and a concise safe summary of what entered the workflow.

Classification and risk

Inspectability state, extractor used, detected classes, reason codes, and confidence or deterministic signals where applicable.

Decision and approval state

Allowed, approval required, or denied, plus the linked approval record and final actor decision where relevant.

Illustrative Records

Request evidence sample

Request

Request ID: req_2ac...889

Use case: supplier_support_summary

Tenant: acme-eu

Created at: 2026-03-14T09:38:02Z

Decision

Risk: high

Decision: approval_required

Reason codes: external_supplier_data, policy_trigger_approval

Policy version: pol_b84...cd1

Approval

Approval ID: apr_1ce...b09

Status: approved

Approved at: 2026-03-14T09:41:26Z

Actor: operator_admin

Exportable evidence

Timeline: request -> policy -> approval -> allow

Audit state: reviewable

Buyer-safe summary: ready

Document evidence sample

File

Name: supplier-contract-q2.docx

SHA-256: 1f2c...9ab7

MIME: application/vnd.openxmlformats-officedocument.wordprocessingml.document

Uploaded at: 2026-03-14T09:42:11Z

Decision

Inspectability: inspectable

Detected class: legal_contract

Decision: approval_required

Reason codes: legal_contract_requires_approval

Approval

Approval ID: apr_7fc...2a1

Status: approved

Approved at: 2026-03-14T09:47:33Z

Actor: customer_admin

Evidence fields

Policy version: pol_b84...cd1

Timeline: intake -> inspect -> approval -> exportable evidence

Use case / tenant: supplier_review / acme-eu

Export state: ready

Evidence is where the governance story becomes credible.

The value is not that PalmerAI says it governs AI. The value is that it can show what entered, what happened, who decided, and which policy applied. That is what buyers, auditors, operators, and partners can actually review later.