Essays on one claim: institutions absorb the evidence that their automated systems are wrong. They argue why the laws hold. No standard cites an essay as a requirement.
Reading order
Read in this order, they state the argument the laws rest on: the mechanism, how it hides, who carries it, why fixing cases leaves it in place, and where the argument comes from.
The mechanism. The evidence that a decision is wrong lands on people who cannot change the rule. Several of the other essays describe its channels.
How the people who absorb a failure improve the metric that should have caught it.
Why the people who correct a system need a route into the rule, and what the institution loses when they have none.
Why fixing each case, even thousands of them, leaves the rule that produces them in place.
What the discipline does not claim, where its argument comes from, and where each neighboring field stops.
Each essay asks one question about automated authority, hidden evidence, or the work people do to keep a system running. They are grouped under the six safeguards the method names.
Capability
2 inquiries
An engineering tradition: What would a safety engineering tradition look like for systems that make decisions on an institution's behalf?
Deliberate non-use: Once a system can do something it could not do before, how can an institution decide, on the record, not to use it?
3 inquiries
Endogenous authorization: How does a system already in place shape the evidence used to decide whether to keep it?
The compulsion problem: Since a standard cannot force anyone to adopt it, how can it be written so that contracts, courts, insurers, and regulators enforce it?
What does not convert: Why do a system's capability and track record never give it authority on their own?
Evidence
5 inquiries
Absorption as concealment: How do people who quietly work around a system's errors keep those errors out of its metrics?
Friction as accidental governance: When automation removes the handoffs and reviews that used to catch errors, what has to be built to catch them instead?
The antihuman metric: How can a dashboard reward a system for hitting its targets while the system wears out the people who run it?
The human subsidy to institutional continuity: What kinds of uncounted work keep an institution looking functional, and how does it come to call that work dedication?
What outcomes hide: Why does judging an institution by its outcomes hide who carried the burden of producing them?
Dependency
3 inquiries
Automation and capture: At what point does relying on a system leave an institution unable to question, replace, or halt it?
Dependence runs both ways: What does an institution owe the people who cannot leave its system?
The consumption of adaptive capacity: When, if ever, may an institution ask people to spend their limited time and stamina making up for its own defects?
Standing
3 inquiries
Challenge density: When challenges pile up, why should an institution add reviewers or narrow the system rather than limit who may challenge?
Dependence without standing: If an institution relies on people to catch its system's errors, why does it owe them a formal way to change the system?
The model of a person is not the person: If a model predicts a person well, why should that person still be able to challenge its decisions about them?
Correction
7 inquiries
Democratic vs. coercive governability: What decides whether logs, audits, and escalation paths give people a way to challenge a system or a way to be controlled by it?
Ethotechnical design: When a design does not fit people, how can it be built so the institution adjusts before the people do?
Exception learning: Why does resolving challenges one at a time leave the rule that caused them in place?
Where difficulty lives: Which layer of a system should absorb a given disturbance, and why does it so often reach a person instead?
Insulation: What keeps evidence that a decision was wrong from reaching the people who could change the rule?
The sovereign override: When a hard rule fails staff in an emergency, how can the software stay strict while each emergency override is recorded as evidence against the rule, not as staff misconduct?
What Ethotechnics is not: What does Ethotechnics leave out, and which familiar words does it stop relying on?
The site has three layers. Theory says why the laws hold. Method states the laws, the condition each one requires, and the standards, mechanisms, and evals that enforce them. Tools are the diagnostics, validators, and APIs that apply the method to a deployed system.
A Method page may cite an essay here as motivation. It may not cite one as a requirement. The laws and the core axioms are what a standard enforces, and the axioms page states the premises they rest on. The essays argue for those premises at length.