Method
AI-accelerated, human-governed engineering
Affectron is a combined AI and human engineering organization. AI systems draft; an auditor keeps the record; a deterministic oracle grades bytes; an independent lineage attacks; humans ratify. Every decision has exactly one home. Nothing depends on anyone’s memory.
Contributions come from many; coherence comes from one; and the one does not author — it ratifies.
The shape: five roles that never overlap. A principal decides releases and the questions that are genuinely questions of meaning, safety, scope, or disclosure. Drafters generate design documents, specifications, code, and tests within written mandates. An auditor keeps the record and grades every draft against it, and never writes what it grades. A judge that is not a mind at all: deterministic test corpora, pinned by hash, that an implementation reproduces byte for byte or does not. An attacker from a different model lineage than the drafters. The rule that binds them: the party being graded never writes the yardstick, and never defines the party that holds it.
The record: a decision register where every architectural question routes and every answer has an id, a status, and a citation; a fixed document template; a charter per unit of work; deterministic corpora authored alongside the prose, never after; and audit records in two layers, the drafter’s own and an independent one, which is where assurance actually rests.
What that produced: nineteen design documents; eighteen byte-level module specifications with deterministic vector corpora and a closed catalog of hundreds of typed errors; a conformance oracle that regenerates every corpus from enumerated inputs on a bare machine; a reference implementation graded against that oracle from its first commit and reproduced independently, hash for hash, by a second implementation in a second language.
What it costs: attention. The method scales in human judgment, not in typing; its bottleneck is review, never budget.
The laws, in brief: nothing mortal is load-bearing · bytes over prose · no silent fills · ratification by acceptance · a control described in a document is not a control · a check over an empty set is not a check · fix inputs; never coach drafts · instruments fail in different directions; keep several · the author never triages its own findings · locate inputs by content, never by name · every participant is replaceable except the record.
What it is not: automation of engineering. It is governance of engineering, with automation doing the labor; it checks more than any human team could afford to, and it is not model-specific.
The method is documented and reusable. Read the essay →