Grading a Technic

Overview

The manual exists to teach groups how to form their own strategies, not to issue strategies. Grading is the operation that keeps that promise. A grade is a standing judgement on a single question: does this technic put a method into a reader’s hands, or hand them a conclusion. The judgement is signed, provisional, and written where anyone can read it, so the manual’s own content is held to the standard it sets for everything else. This technic is no exception. It is graded by its own test like any other.

How it works

A method tells a group how to decide. A strategy tells them what was decided. A method can be run by two honest groups and reach two different, equally sound answers. A strategy names the answer before any group has met. The plain test is whether the output can be predicted from the page. If the answer is already on the page, the page is deciding, and agency has moved from the group to the manual.

One distinction must be held carefully, because the whole skill rests on it. Some fixed things in a technic are legitimate. A step may fix a process invariant, such as meeting in the open, rotating roles, keeping a record, or finishing what is started, without smuggling a strategy, because these fix how a group works and leave what it decides untouched. The line is crossed only when a step fixes a substantive outcome: a number, a size, a structure, an allocation, a target, a named winner. “Rotate the roles” fixes an invariant and is open. “Split when you reach eight to twelve” fixes the group’s size strategy and is a directive. Telling a process invariant from a smuggled outcome is the grader’s central work.

The unit of this judgement is the step, not the technic. A technic is rarely all method or all strategy. It is usually a method spine with a few steps that cross the line. So grading reads the Operation list and the load-bearing claims one at a time, marks each as procedure or directive, and scores the whole only after.

The line judgement is then held beside the consistency protocol, the five tests from the filter: connection and fidelity, distributed agency, the reading, coupling and reciprocal regard, and carried in the open. The two are scored separately, because a technic can be honest method and still fail a protocol test, or pass every protocol test and still decide for the group.

Operation

1. Read the whole technic once for sense before judging any part of it. A step read in isolation is misread.
2. Take the Operation list step by step. For each step, ask what it fixes. If it fixes nothing, or fixes only a process invariant such as openness, regularity, rotation, reciprocity, or completion, it is procedure. If it fixes a substantive outcome such as a number, a size, a structure, an allocation, a target, or a named winner, it is a directive. Apply the same reading to any load-bearing claim in How it works.
3. Name the directive steps. Record each by its section and number, in plain reference such as “Operation 8” or “How it works, third paragraph.” These are the canalising steps, and they carry the published cause.
4. Score the line. If no step fixes a substantive outcome, the line is open. If the spine is method and one or two steps that are not load-bearing fix an outcome, so that removing or rewording them leaves the procedure intact, the line is leaning. If the technic’s core depends on fixed outcomes, so that removing them leaves no method behind, the line is directive.
5. Run the five protocol tests. Mark each as pass, flag, or fail. Pass is clean. Flag is a real concern that revision should address but that does not on its own disqualify. Fail is disqualifying: the test is not met, and no rewording of detail will meet it.
6. Check yourself for coherence. Ask whether you are granting this because it reads well and hangs together, or because it passed the tests. An elegant technic is not thereby a correct one. If you cannot separate the two, set the coherence flag.
7. Decide the verdict. Grant when the line is open or leaning and no protocol test fails. Withhold when the line is directive or any protocol test fails, and send the technic back for redesign rather than grant it under a heavy flag. Lower only a technic already granted that has since been shown to fail, with the cause published.
8. Write the cause. State plainly what is method and what is directive, cite the canalising steps by number, give the five protocol verdicts, and where you withhold or recommend revision, say what method form the directive steps should take instead. The cause is signed by your account, and your standing rides on it.
9. File the grade as a new record, never an edit to an existing one. A revised judgement is a fresh signed record that supersedes the last, so the trail stays whole.

Cautions & failure modes

• Grading virtue instead of capacity. The easiest fault is to mark a technic down because it does not share your values, or up because it flatters them. The protocol reads conditions, not virtue. A technic is graded on whether it distributes capacity and keeps a group free to decide, never on whether its conclusions please the grader. This is the discipline that is hardest to keep, which is why it is named first.

• Mistaking an invariant for a directive. An over-strict grader marks every fixed thing a smuggled strategy and leaves no technic able to teach anything. Openness, rotation, and completion are the method’s legitimate content. Fix the reading at the level of substantive outcome, not at every constant.

• The grader who becomes a gate. A standing right to judge curdles into a right to rule. Grading gates the adjudicated record only, never speech about a technic: anyone may criticise, refute, or rewrite in the open. Eligibility to grade is a low earned floor, held by many, not an office held by few. Where graders converge until their judgements are one judgement, the layer has begun to consolidate and must be widened, not defended.

• Self-grading. A grade signed by the technic’s own author is the author marking their own work, and it collapses the distance the layer rests on. A grader must not grade what they wrote. Until technics carry a signer, this is held by the grader’s honesty and by review from others.

• Coherence mistaken for correctness. A grade granted because the cause reads cleanly, rather than because the technic passed, has imported the very error the manual warns against. The coherence flag exists to be used.

• A placeholder read as a signature. This register carried sixteen grade records signed peer:REPLACE-WITH-HANDLE, a stand-in for a grader who did not exist. They rendered exactly as a real grade renders: a verdict, five axes, a signature line. Nothing on the page told a reader that the signature was scaffolding, and a scaffold that cannot be distinguished from the thing it stands in for is not a scaffold but a claim. All sixteen were vacated on 30 July 2026 and every entry now shows a pending grade. Kept here as the failure mode it was: the grading layer’s first real fault was not a bad grade but a convincing empty one.

• The frozen grade. A provisional grade treated as final hardens one reading into law. Grades are provisional and open to appeal, reviewed upward by other qualified graders. The bootstrap’s internal review is itself a stage, and it gives way to grading from outside the movement as the layer matures.