- What entered A scanned invoice entered the governed intake path, not an invisible file attachment passed straight to a model.
- What happened PalmerAI classified it as a financial document and stopped it at
approval_required. - Why it stopped The policy matched strong finance markers and kept the decision reviewable instead of letting it continue silently.
- What stayed visible Inspectability, class signals, timestamps, and the policy reference stayed visible for later review.
- What is intentionally omitted Full raw invoice text, sensitive supplier details, and the underlying file contents are not shown here by default.
Evidence Pack Sample
See what a reviewable decision record looks like.
This sample shows the kind of structure a governed workflow can preserve for later review, including decision state, policy reference, approval status, and timing.
This is not meant to be a raw log dump. It is a readable example of the kind of decision record a governed workflow can leave behind.
What to look for
- Request identity
- Document context
- Policy reference
- Approval state
- Decision outcome
- Timestamps
Sanitized Sample
Example: scanned supplier invoice routed to approval
This is the level of detail a reviewer or buyer actually needs: enough to understand the path, the decision, and the reason for it, without exposing raw document contents by default.
{
"request_id": "req_20260327_104211_7b41",
"tenant_id": "northstar-manufacturing",
"input_kind": "pdf_rasterized",
"document_class": "financial_document",
"decision": "approval_required",
"approval_state": "pending_reviewer",
"inspectability": "inspectable",
"policy_ref": "finance-intake-v3.2",
"reason_codes": [
"financial_document_requires_approval"
],
"class_signals": [
"invoice",
"vat",
"payment_due",
"supplier_reference"
],
"ocr": {
"provider": "service",
"model": "tesseract",
"language_hint": "eng+deu",
"confidence_band": "standard"
},
"timestamps": {
"received_at": "2026-03-27T10:42:11Z",
"decided_at": "2026-03-27T10:42:13Z"
}
}
This sample is intentionally sanitized and representative. It shows the shape of the evidence bundle, not a customer record or a full internal dump.
What an evidence pack contains
- Request or document summary
- Policy version
- Approval state
- Reason codes
- Timestamps and hashes
- Tenant or account context
That is enough to make the record useful for buyers, procurement teams, operators, and partners without exposing raw document contents by default. The sample above is the kind of review-friendly record we mean.
What is visible
Decision context
What entered the workflow, what decision was made, who approved it, and what policy version shaped the result.
Integrity markers
Hashes and timestamps that make the record reviewable later instead of forcing a team back into raw infrastructure logs.
Bounded safety signals
When supported document traffic is oversized, unsupported, or structurally suspicious, the resulting deny or approval-required reason codes can remain visible in reviewable evidence and internal anomaly review.
What that means commercially
The control story is not only about classification. It is also about proving that risky or abnormal inputs do not pass through the workflow silently.
What is not exposed by default
Evidence views do not need to expose raw document contents to be useful in procurement, review, or routine partner reporting.
The goal is reviewability with restraint: enough context to prove the decision, not a second archive of sensitive material.
Why it matters
For buyers
It turns a governance claim into something concrete enough to review.
For procurement
It makes the control story easier to defend without overclaiming what the product does.
For partners
It supports reporting and assurance conversations without exposing raw client material by default.
Evidence is where the control story becomes credible.
When the question shifts from interest to scrutiny, this is the page buyers and partners need next.