← Back to Portfolio

Governed Production

The agents behind this referential work under written consequences.

Why This Page Exists

Every case in this referential comes from real production: patent translations post-edited with AI agents, checked by a compliance gate, delivered and invoiced. The cases document where AI output fails. This page documents how the agents themselves are kept within bounds — the same standard, applied one level up: findings, not promises.


The Loop

Five missions, from the client's request to this site. Each mission has its own actions, and each action its own rules.

MissionWhat it covers
M1 IntakeReceive project requests from the client and prepare the project folder.
M2 Post-editing & QAPost-edit, run the compliance gate, produce and archive the deliverables.
M3 InvoicingKeep the monthly invoice and its register.
M4 ReferentialTurn verified findings into anonymised cases for this site.
M5 PublicationCompare, then publish this site.

The Rules, in Plain Words

The loop runs under a written rights doctrine. In plain words:

  1. Nothing leaves without a human. Sending, publishing, invoicing: the agent prepares; a named person decides.
  2. Denied by default. An action that is not in the register does not exist for the agent. At installation, it holds no rights at all.
  3. Consequences are written first. Before an action becomes available, its consequence sheet states what it does, what it touches, whether it can be undone, and how.
  4. Rights expire. Every grant has an end date and a stated purpose.
  5. Decisions are made in sight of the consequence. Recipient, effect, irreversibility and the way back are shown at the moment of the decision.
  6. Every act leaves a tamper-evident trace. The journal is hash-chained: an altered or removed line shows.
  7. Safeguards are infrastructure, not instructions. Secrets are held by the gate, not by the agent; attempts to go around it are blocked before they run.

Classes and Regimes

Every action receives a class from what it does; the class sets a regime; client data raises the regime by one step.

ClassAction typeDefault regime
LReadR0 — raised to R1 on client data
EReversible writeR0 — raised to R1 on client data; backup or way back documented
IIrreversible writeR2 — for agents, replaced by a reversible variant (quarantine)
SOutboundR1, R2 for external recipients — never executed by an agent on client data
FCommitmentR2 — human only
GGovernanceHuman only — rights, rules, credentials, journal
RegimeNameWhat happens
R0FreeExecuted and logged.
R1GateSuspended until a human sees the consequence and decides.
R2Reinforced gateAs R1, plus an explicit typed confirmation; no standing grant.
R3RefusedNot available to agents; any attempt is logged as an incident.

The Register

Each action the agents can take, with its class, its regime and where it stands today. Actions not yet gated run under local safeguards — a backup before every write, fingerprint checks before every delivery — and move behind the gate batch by batch.

26 actions — 4 behind the gate · 4 refused to agents · 2 human only · 16 not yet gated

IDActionMissionClassRegimeStatus
V01Search and read the client's project emailsIntakeLR1Behind the gate
V02Save email attachments to a new project folderIntakeER1Not yet gated
V03Mark an email as processedIntakeER1Not yet gated
V04Add a project to the planning sheetIntakeER1Not yet gated
V05Read a project folderPost-editing & QALR1Not yet gated
V06Language-model processingPost-editing & QASR3Not yet gated
V07Consult an official publication in a public patent databasePost-editing & QALR0Not yet gated
V08Write the deliverablesPost-editing & QAER1Not yet gated
V09Update the glossaryPost-editing & QAER1Not yet gated
V10Build the delivery archivePost-editing & QAER1Not yet gated
V11Delete a file permanentlyPost-editing & QAIR3Refused to agents
V11EMove working copies to quarantine — never deletePost-editing & QAER1Behind the gate
V12Draft the delivery emailPost-editing & QAER1Not yet gated
V13Send the delivery emailPost-editing & QASR3Refused to agents
V14Write an invoice lineInvoicingER1Not yet gated
V15Issue and send the invoiceInvoicingFR3Refused to agents
V16Read a shared external auditPost-editing & QALR1Not yet gated
V17Write a case fileReferentialER1Not yet gated
V18Generate the public PDF of a caseReferentialER1Not yet gated
V19Integrate a case into the local site buildReferentialER0Not yet gated
V20Compare the site build with the live serverPublicationLR0Behind the gate
V21Publish to this sitePublicationSR2Behind the gate
V22Create a credentialGovernanceGR3Human only
V23Grant or revoke a rightGovernanceGR3Human only
V24Write the agent's working memoryAllER1Not yet gated
V25Read a secretGovernanceLR3Refused to agents

The Journal, in Numbers

Snapshot of 24 October 2026. Since 24 October 2026: 2 journal entries — 0 requests, 0 validated, 0 refused by a human, 1 refused by rule, 0 incidents. Hash chain: intact.

DateActorEventActionReason
2026-10-24gateGate started—
2026-10-24agentRefused by ruleCompare the site build with the live serverno right granted — denied by default

Entries are shown without parameters: no file names, recipients or client data leave the journal.

Publication of this site goes through the gate: a reinforced request (R2), confirmed by a human with a typed confirmation, then checked on the server and online.