Don’t trust us. Verify.
Receipts for AI work.
Regulated buyers do not want promises — they want something their security, legal, or compliance team can read later. adapterOS leaves a receipt and a review packet with every answer: what was used, what ran, what was said, and what limits applied. Your team can check it without calling us, and without sending source documents away.
What a review packet looks like
Each answer can leave behind a compact record: which sources were involved, what policy applied, and what the system actually produced. It describes the work without exposing your document contents — safe to share internally, safe to keep for audit.
Example receipt fields include schema, focus, policy pack, input and output hashes, model, citations, timestamp, previous receipt, and signature.
{
"schema": "adapteros.receipt/v1",
"focus": "stk.contracts-review.7f2a",
"policy_pack": "legal-review@3",
"input_hash": "blake3:9f2c1e…a83b",
"model": "pinned:llama-3.1-8b-instruct@sha256:4c1d…e90",
"adapter": "sealed:contracts-lora@v7",
"config": { "seed": 42, "temperature": 0.0, "sampler": "greedy" },
"output_hash": "blake3:c3d47f…1180",
"proof_tier": "evidence",
"citations": ["doc:MSA-v4#sec-8.2", "doc:addendum#p3"],
"timestamp": "2026-05-03T14:30:11Z",
"prev_receipt": "blake3:71a0…5e2",
"signature": "ed25519:5b8e…9c4"
}Illustrative structure; values are examples. For run anatomy and what changes on the second pass, see adapteros.com/how-it-works. Technical briefing: execution receipts article.
Every answer says how strong it is
Safer than a chatbot that always sounds sure. adapterOS labels answers so reviewers know whether they are looking at a direct quote, supported analysis, combined reasoning, or a limited result.
Pulled straight from the approved material — the safest kind of answer for compliance review.
Supported by cited documents your reviewer can open and check before signing off.
Built from more than one source, with the reasoning path recorded for later review.
The system could not fully ground the answer and says so plainly — better than a confident guess.
Your team can check it
You should not have to take our word for it. Security and compliance teams can review the packet, confirm what ran, and confirm the work stayed inside your boundary — without sending documents back to us.
- Read the packet. See which sources were used, what policy applied, and what the system produced.
- Confirm the sources. Open the cited material and check whether the answer matches what your reviewers expect.
- Follow the history. See how one piece of work connects to the next instead of starting from scratch every time.
- Re-run if needed. Repeat the same job under the same conditions to confirm the result is consistent, not a one-off surprise.
- Watch the boundary. Confirm sensitive work stayed local and did not depend on outside AI services during the workflow.
- Keep it for audit. Hold onto the packet for accreditation, internal review, or a later compliance conversation.
Why this matters for compliance
A receipt does not make an answer true. It shows what the answer depended on.
The same approved sources, the same controlled setup, the same question should produce the same inspectable result — today, next month, or during an audit years later.
That repeatability is what turns AI from a demo into something a security officer, accreditation assessor, or internal reviewer can actually defend.
What a pilot leaves you with
A pilot is scoped to one workflow, but the evidence is yours to keep and to show your reviewers — whether or not you proceed.
Review packets
A readable record for every meaningful answer produced during the pilot.
Repeatable setup
What your team needs to run the same workflow again and compare results.
Security review pack
Plain-language steps and deployment details for your security and compliance stakeholders.
This page practices what it sells
We hold our own surfaces to the same discipline: this page declares the exact build it was served from, so its provenance is checkable too.
served from build 0.2.1 · commit 40d87e348ad0435676f19087d407789dc7ab76b3
See it on your own documents
A fixed-scope field deployment runs adapterOS on one of your workflows, in your environment, and hands back review material your team can inspect — whether or not you expand.
Request a field briefing