Countersign

Implementation guide / not legal advice

Human oversight that survives contact with an agent.

Articles 12 and 14 connect traceability with effective oversight by natural persons. An approval console can support that work; it cannot determine scope or create a compliance program.

Control surface

QuestionCountersign supportsYour team still owns
Understand before actionContext, exact arguments, provenance, edit schema, and field-level diffRisk-specific UX, training, and instructions
Intervene or stopLangGraph interrupt/resume, allowed decisions, rejection, and execution outcomesApproved stop procedures and escalation authority
Trace decisionsHash-chained request, decision, expiry, and execution events; evidence exportRetention, access governance, and storage controls
Authorize reviewersAdmin, approver, and viewer roles; captured policy and quorumIdentity lifecycle, training, and delegated authority
Investigate failureOriginal input, edit, policy, runtime outcome, and integrity verificationIncident response, monitoring, and broader technical logs

A practical operating pattern

  1. Identify actions capable of material impact and define policies by action, graph node, risk, or amount.
  2. Include a reviewer-facing description, exact arguments, runtime provenance, and an edit schema where edits are safe.
  3. Require trusted identity and appropriate quorum wherever reviewer attribution matters.
  4. Resume only through the recorded decision path, then append the completed, failed, or halted outcome.
  5. Export and verify evidence, test restore paths, and review authorization and escalation arrangements periodically.

What remains yours

Teams still need to assess classification and applicability, manage risk, document the system, train reviewers, govern personal data, secure infrastructure, handle incidents, and maintain retention and oversight processes.

A hash chain detects altered exported history. It does not replace database controls, encryption, a retention policy, or an externally managed signing key. SQLite is an evaluation path, not a production claim.

Primary baseline

Read Regulation (EU) 2024/1689 and obtain qualified legal advice for role, classification, applicability, and timing. Use this guide as an engineering checklist, not a legal conclusion.