Executor seat
An execution role with its own contract, named after a function, not a person. When it runs unattended, it uses the model fixed in its contract.
LABORATORY · GOVERNANCE / 06
Work between people and agents runs through a queue with states, leases, gates and cross-review. The underlying rule: agreement between AIs does not validate facts.
Version 0.4.2 · updated 2026-09-27 · Version history
00
Automation supports execution and never changes who decides, nor transfers responsibility for the outcome.
Golden Rule of Automation, ratified on 25 Sep 2026
Everything else on this page follows from it: queues, leases, gates and adversarial review exist so that the decision stays human and responsibility stays with whoever decides.
01
The mission is described: goal, scope, limits and acceptance criteria.
The responsible person authorizes it in writing.
A single executor leases the mission and works.
The executor delivers the report and stops, awaiting review.
The responsible person ratifies it, asks for another round or cancels it.
RECORDED FACTThere are expiry rules: a draft 30 days old or more is cancelled; a report without a human decision for 30 days is closed by tacit ratification; an expired lease is released by a neutral observer.
02
RECORDED FACTA single execution key per mission and round: one executor at a time, within a declared time window. Before writing, the executor re-reads the state so as not to override someone else's lease. Different missions that do not touch the same resources can run in parallel.
03
RECORDED FACTCheckpoints that require specific authority or evidence before a change of state: a human authorization, an automatic verifier that must pass, a maturity criterion. Without an open gate, nothing is published, promoted or deleted.
04
RECORDED FACTOne model builds; another, from a different vendor, contradicts without seeing the first one's material. Then they compare finding by finding. The reviewer may fix and publish within the mission's limits; what it cannot resolve goes back to whoever authorized it.
Agreement between AIs does not validate facts.
Rule of the Operational Bridge
05
An execution role with its own contract, named after a function, not a person. When it runs unattended, it uses the model fixed in its contract.
A deliberative body, advisory and limited to defined topics. It advises; it does not execute.
These are the planned scheduled posts: functions that beat on their own, like a heart.
06
Every round ends with a report: before and after; facts, hypotheses and gaps kept apart; pending decisions addressed to the responsible person; and an exact pointer to where to resume.
The receipt counts the round's sensitive actions, which as a rule should all be zero:
07
24 Sep 2026. A sector slice, not a client case: the adverse-possession (usucapião) workflow, from technical documents to the consent of neighbouring owners.
One built the workbench and the method; the other ran the adversarial review with its own dossier and tried to break the verifier.
Twelve rules checking literal legal citations, missing or outdated sources, silent contradictions between versions, duplicated identity, improper promotion to the kernel, simulated human decisions and exposure of personal data.
Each condition was tested with a planted error. All were detected in the reported batches.
A candidate playbook for the procedure, revised in successive versions, and a scenario matrix with no concrete case filled in.
No currency: the method was produced and technically verified, but it only becomes currency after a merits review by a qualified professional.