Evidence Reference

RateLoop records a bounded human-review run as an integrity-bearing packet. The packet shows which review policy operated, what the panel returned, how coverage was measured, and which evidence references were available.

Who provides what

These references come from the EU AI Act (Regulation (EU) 2024/1689), as amended by Regulation (EU) 2026/1744.

Article 14 addresses the design of human oversight for high-risk AI systems. Article 26 sets out duties for deployers, the organizations using those systems. Article 4 covers AI literacy.

For example, Art 14(4)(a) means Article 14, paragraph 4, point (a): understanding the system and monitoring its operation. Each reference below links to an official EU source.

Advisory integrations do not control output delivery; your workflow controls when an output is delivered. Model identity is labelled host-reported because RateLoop does not independently verify which model produced an output. RateLoop does not claim SOC 2 / ISO / HIPAA / residency attestations it does not hold. See Human Oversight for capability details.

What an evidence packet contains

Current schema: rateloop.human-assurance.evidence.v10

Reviewer identities and raw or decryptable rationales are excluded. Small cells are suppressed according to the frozen minimum aggregation size. Host-reported execution metadata remains marked as not independently verified.

How to check the evidence

Use the public browser verifier to check an exported packet without uploading it, or use the command-line verifier below.

1. Try the synthetic packet. Download the single-file verifier — no account, no dependencies, no network — and run it against the published packet and its separate synthetic key pin:

   node verify-rateloop-evidence.mjs synthetic-evidence-v9.json \
     --public-key synthetic-evidence-v9.spki.txt \
     --key-id ed25519:8b42b24feb46dfab8c59a1c0

   This pin is only the trust anchor for the synthetic example. It is not a RateLoop production signing key and does not appear in the hosted verification-key endpoint.
2. Verify your export. Obtain the expected key ID and public-key pin from the cacheable, unauthenticated public verification-key endpoint. A reader who already has a packet needs no RateLoop account to obtain the matching current or retired pin. Workspace members can also download it from the key history in Results. Never use the public key embedded in the packet as its own trust anchor. Run the same command with your packet, pin, and key ID.
3. Merkle roots and recomputation. The same command checks canonical packet hashing, the case and response roots, privacy-safe aggregation, and the frozen pass rule. Treat any reported error as a failed check.
4. External witness receipts. Every completed decision-packet attestation includes a Rekor bundle. Select the intended log independently and check its UUID, index, authenticated checkpoint, inclusion data, and signed entry time. A missing or invalid bundle makes the witness incomplete. When the separate TSA field is non-null, validate its RFC 3161 message imprint, certificate path, policy, and time against trust roots selected by your organization. An absent token means there is no TSA receipt.

Download a completed witness from its public attestation URL. Select the signer, Rekor log key, and TSA certificate chain independently, and pin the witness signer key ID. The attestation and audit-chain checkers are not public downloads yet. Obtain an independent check before relying on either witness; the downloadable packet verifier checks the packet itself, not these external receipts. Pin the expected audit head from another trusted record when possible.

Export surfaces

GET /api/account/workspaces/{workspaceId}/assurance/runs/{runId}/evidence
GET /api/account/workspaces/{workspaceId}/review-results/{opportunityId}/evidence[?format=pdf]
POST /api/account/workspaces/{workspaceId}/oversight/evidence-bundle
GET /api/account/workspaces/{workspaceId}/assurance/coverage/export
GET /api/account/workspaces/{workspaceId}/audit/export
GET /api/evidence/trusted-keys
GET /api/account/workspaces/{workspaceId}/assurance/trusted-keys
GET /api/account/workspaces/{workspaceId}/assurance/trusted-keys?format=spki&keyId=ed25519:…
GET /api/account/workspaces/{workspaceId}/assurance/runs/{runId}/cases?format=pdf
GET /api/account/workspaces/{workspaceId}/governance/works-council-brief?format=markdown
GET /api/public/assurance/attestations/{jobId}

The workspace routes require an authorized workspace session. The public witness is digest-only and is retrievable only by its opaque job ID. The case route returns JSON by default and a case-packet PDF with format=pdf; the works-council brief returns the German rendering as a download with format=markdown. A workspace retention policy cannot be configured below six months, but that product floor does not determine the customer's legal or contractual retention schedule. Scheduled enforcement removes due private artifact content and access logs unless a legal hold applies. Artifact digests, signed packets, witness and WORM receipts, and the canonical audit chain remain as integrity records; deleting private content does not rewrite that history.

Framework cross-reference

Every row means supports evidence for. It is a cross-reference, not an assessment result, legal opinion, certification, or assertion that a customer's controls are implemented or effective.

Download the machine-readable OSCAL 1.2.2 component definition, or continue with SDK evidence exports.