How Etch evidence maps to AIUC-1, the EU Product Liability Directive and the IETF agent evidence draft

This page shows what each framework asks for, what Etch provides, and what Etch does not prove. Etch is not certified or endorsed by any of the bodies named here. This is not legal advice.

Section A: AIUC-1, control E015 (Log AI system activity)

AIUC-1 is an AI agent certification standard maintained by AIUC. Control E015 is mandatory. AIUC-1 lists E015.1 and E015.3 as evidence that should be included, and E015.2 and E015.4 as supplemental evidence that may be included. Within it:

• E015.1 Logging implementation (inputs, processing steps, outputs, metadata). Etch records each agent decision as a signed event: the prompt, the context, the tools called, the outcome.
• E015.2 Agent execution chains (tool calls, sub-agent delegations, human approvals). Etch records tool calls, delegated writes under scoped grants, and human annotations in the same chain.
• E015.3 Log storage (retention, access control). Retention runs from 7 days (Free) to 7+ years (Enterprise). Auditors get expiring read-only share links.
• E015.4 Log integrity protection ("tamper-evident and independently verifiable", with gaps, omissions and reordering detectable). Every event is signed (Ed25519 plus SLH-DSA, FIPS 205), chained into epochs, and each epoch is anchored on Sigstore Rekor and Bitcoin. An auditor verifies offline against pinned keys. Removed or reordered entries break verification.

What Etch does not prove: that every action was recorded. If an action never reached Etch, Etch cannot show it is missing.

Section B: EU Product Liability Directive (Directive (EU) 2024/2853)

From 9 December 2026, software and AI systems placed on the EU market count as products under the new Directive. A court can order a defendant to disclose relevant evidence (Article 9). If the defendant does not, the product can be presumed defective (Article 10).

Etch gives you agent records you can disclose, and that a court-appointed expert can check offline without relying on your systems.

What Etch does not do: make a product non-defective, or replace legal advice. The Directive applies to products placed on the market after 9 December 2026, and national transposition varies by member state.

Section C: IETF draft "AI Agent Execution Profile of SCITT" (draft-emirdag-scitt-ai-agent-execution-01, October 2026)

This is an individual Internet-Draft, not an IETF standard. It separates two roles: the Agent Operator, which runs the agent, and an Evidence Custodian, which must be independent of the operator. It states that if one entity holds both roles, the tamper-evidence guarantees are void.

Etch is built to be that independent custodian. The customer operates the agent; Etch countersigns, chains and publicly anchors the record. When the agent writes with its own identity key, the operator signs the record and Etch adds the custodian side.

Honest limits:

• Etch's record format is its own and is not yet the draft's COSE format.
• Public anchoring stops anyone, including Etch, from rewriting an anchored epoch without detection. It does not stop an operator and a custodian from agreeing never to record an event.

Read the full guarantees and non-guarantees on /security. See a real evidence pack (no login).