Record-keeping
Hash-chained audit logs capture LLM calls, signals, decisions, overrides, retries and corrections so consequential work remains traceable and reconstructable.
Agent6 is designed around the control patterns European enterprises will need: automatic record-keeping, effective human oversight, accuracy, robustness and cybersecurity. Legal classification still depends on the customer workflow, but the architecture is built for regulated use from day one.
Hash-chained audit logs capture LLM calls, signals, decisions, overrides, retries and corrections so consequential work remains traceable and reconstructable.
Customer-facing, financial and compliance-relevant outputs route through a human review queue with reasoning traces, verification details and named approval.
Schema validation, Chain-of-Verification, checkpoint recovery, model failover and local fallback reduce fragile automation and improve operational continuity.
The Agent Passport is the governance container that prevents autonomous agents from becoming uncontrolled actors. No passport, no execution.
Low-risk, reversible and well-bounded decisions can move at machine speed under audit, schema validation and passport limits.
Strategic, legal, financial, ethical or irreversible decisions are escalated to the human review queue with full context and traceability.
Four engineering primitives make the Stack reliable enough for regulated workflows.
CoVe, schema validation and experiment orchestration identify hallucinations, compare variants and track reliability over time.
Every LLM call, signal, decision, override and correction is reconstructable through the hash-chained audit trail.
Crashed workers resume from the last completed phase; provider outages trigger failover; exhausted tasks fail cleanly.
PIN-protected review preserves human authority for customer-facing, financial and compliance-relevant work.
Human review becomes operational memory: attributed, reversible and automatically injected into future work of the same task type.
A human rejects or adjusts an output with written remarks and context.
The system converts the correction into a structured operating rule.
The rule is logged with reviewer, source task, timestamp and audit reference.
Future matching tasks receive the correction automatically before execution.
A standard node can be a commodity small-form-factor PC hosting local agents and a local LLM. Regulated workloads can run with zero outbound network calls while frontier models remain optional for tasks that genuinely need them.