Now serving
every U.S. ZIP code — home base in Chico, California. From the
TechNow SAI studio — business systems, made human.
The question nobody can answer yet
The agents are already acting. The proof layer isn't there.
An agent signed it. Which agent?Automations run under shared API keys and service accounts. When something goes wrong, attribution is a log line — written by the same system it describes, and editable by the people it might incriminate.
“Our automation did that” isn't an answerWhen a client, a bank, or a regulator asks who authorized an action, a screenshot and a shrug don't hold up. You need a record that was made at the moment of the act, by a system built to be believed later.
Approval queues are the workaroundBecause nothing proves an agent acted inside its authority, businesses route agent decisions past humans. It's the same tax AXLE exists to address — trust, verified one approval at a time, at human speed.
Everything outside a proof system is unverifiedThat's not an insult and not an accusation — it's the plain state of things. Without enrollment in a certification system, no action can be proven after the fact, no matter how honest everyone involved was.
Here's the lesson the web already learned. Certificates never detected fake websites — they certified real ones. DAAP makes the same move for the agent era: certify the real at the source, and let everything else stand as what it honestly is: unverified.
The three pieces
One system, three parts. This is the design we're building with design partners — described as designed, not dressed up as a finished product.
🛂
1 · Agent PassportsA cryptographic identity issued to each automation you deploy: its origin, its owner, the actions it's permitted to take, its scope limits, and its expiry. If an agent is retired, compromised, or simply out of scope, its passport is revoked — and every receipt it ever issued stays readable.🧾
2 · Signed Action ReceiptsEvery material action — a payment, a submission, a signature, an access request, an outbound message — produces a receipt at the moment it happens: which passport acted, what it did, a hash of its inputs, and the result. Each receipt is hash-chained to the one before it, so altering the record breaks the chain where everyone can see it.🔐
3 · The Audit VaultThe receipts, retained and searchable, exportable for the moments that matter: a disputed transaction, a regulator's question, an insurer's review, a court. Receipts store hashes and metadata — not the content of your documents or calls. The black box, built from receipts we issued, never from surveillance of anyone else.
Enrolled partners whose agents act under live passports earn the right to display the line “Actions verified by DAAP” — and it's revocable on misuse, because a trust mark that can't be taken away isn't worth anything.
Where DAAP sits in the family
One stack, one breath: delegate it, prove it, protect it.
OmniDelegate delegatesOur founding delegation service hands tasks to a chief of staff — and already produces a confirmation record for every task it completes. DAAP receipts are that record, grown up: cryptographic, portable, and provable to anyone. It's also where DAAP gets built and proven first — on our own tasks, before anyone else's.
DAAP provesThe actor and the act. Which passport performed which action, inside what scope, at what time — in a record that shows its own tampering. Proof is the whole product; DAAP sells records you can stand on, and nothing else.
AXLE protectsOur concept for a financial risk layer over agent execution — the pre-execution risk check and, one day through licensed insurance partners, a financial answer when an agent's action goes wrong. Proof first, protection second: an underwriter can't price what nobody can prove.
What a DAAP receipt does — and does not — prove
The honest section. We'd rather draw this line in public than let anyone discover it later.
A receipt proves
- Which enrolled passport performed the action.
- The scope that passport was issued — what its owner authorized it to do.
- What action was recorded, and a hash of the inputs it acted on.
- When it happened.
- That the record has not been altered since it was written — the hash chain shows tampering.
A receipt does not prove
- That the action was wise, well-judged, or a good business decision.
- That the action was legal in substance — only that it happened, by that passport, inside its recorded scope.
- That anyone's intent was honest. Proof of an act is not proof of a motive.
- Anything at all about actors outside enrollment. They are unverified — a statement about the absence of proof, never a claim that something is fake.
And three more lines we won't blur. DAAP is not a deepfake detector — detection is an arms race, and we don't sell claims we can't stand behind; we certify what's enrolled and call the rest unverified. DAAP carries no guarantee — a receipt is evidence, not a promise of payment; anything that stands financially behind a transaction is insurance, and that only ever ships through licensed partners. Version one uses no biometric templates — identity is established with document checks, device signals, and behavioral patterns that never become biometric identifiers. A human-presence layer exists on the roadmap only, gated behind counsel review and written consent flows.
Who should talk to us
You build or deploy automations — agencies and platforms putting agents to work for clients. Your clients' compliance questions are coming — whose agent did this, under whose authority — and a passport-and-receipt layer is the feature that answers them without you building a trust system from scratch.
Your business runs money-moving automations — billing executors, procurement bots, refund and claims intake, customer-message agents. If a disputed action would cost you real money or a real client, you are exactly who the Proof Audit is for.
You're in a regulated sector — healthcare, finance, legal. You're the destination, honestly not the beachhead: the vault, retention schedules, and counsel review have to exist before DAAP belongs in your world. Talk to us now if you want to shape what gets built.
Questions, answered straight
Does DAAP detect deepfakes?
No — plainly, and on purpose. Detection is an arms race against every generator on earth, and a missed fake with our name on it would be the end of the trust we're trying to build. DAAP certifies enrolled agents at the source instead. Anything outside enrollment is called unverified — which is a true statement about proof, not an accusation that something is fake.
Is a DAAP receipt a guarantee that a transaction is safe?
No. A receipt is evidence: proof of which passport acted, within what scope, and that the record is untampered. It is not a guarantee, not indemnity, and not insurance of any kind — DAAP sells proof and records, full stop. Financial protection for agent actions is a separate problem, and it's what AXLE is being designed to explore through licensed partners.
What exists right now?
This page, the published design, a receipt-format specification in progress, and a design-partner program. DAAP is pre-launch and we say so everywhere. The first build target is our own house: OmniDelegate tasks issuing DAAP receipts, so the first receipt chains anyone sees are real ones from work we actually did — including a public sample chain a prospect can verify for themselves.
What is the Proof Audit, exactly?
A free 30-day design-partner exercise. We inventory your live automations, name which ones act with no provable identity and no usable record, and produce sample receipts for your top three actions — so you can see precisely what your proof would look like before anyone talks about a paid pilot. Pilot pricing, when we get there, is set in writing per pilot.
Do receipts store our documents or calls?
No — by design. Receipts hold hashes and metadata: which passport, what action, when, the hash of the inputs, the result. The content of your documents, messages, and calls stays yours. A design partner that contractually needs content retention keeps it in their own vault, under their own policy.
What about verifying humans, not just agents?
Later, and carefully. Version one establishes identity with document checks, device signals, and behavioral patterns — no biometric templates, because biometric law (Illinois' BIPA and its siblings) carries the kind of per-violation damages that end small companies, and because consent and retention have to be designed before collection, not after. A human-presence attestation layer is a gated second phase, behind counsel review.
Design partners: start with the free Proof Audit
Tell us what your automations do. We'll reply from a real inbox, in plain English, within one business day. This form starts a conversation — it creates no partnership, no coverage, and no obligation on either side.
Message received — thank you. 💚
Watch your inbox: we'll reply within one business day. If an automation of yours acted yesterday and you couldn't prove who authorized it, text us and say so — that story is exactly the research we're doing.
Rather just write? Email support@technow-sai.site with the subject DAAP, or text us: (530) 487-0107.
Your agents are already acting. Can you prove what they did?
We're building the proof layer and looking for the partners it should be built for — in the open, in the right order.
Get the free Proof Audit
