Method & governance
Computation produces factual knowledge about traces. The last mile — what follows for democracy — is explicit interpretation by the author, never a frequency dressed up as a norm.
Two layers, one firewall
Before any coding: what kind of object is claimed (natural, ideal, social), which domain, which mode of the register. Written once, versioned, cited by every unit.
From the span to the code to the interpretation, each step logged. Backward traceability: any claim in the book walks back to a set of unit ids.
No technique generates a normative claim. Normative statements live only in the author’s marked field and in chapter 13.
Below α 0.67 nothing propagates; between 0.67 and 0.80 only exploratory language; from 0.80 the unit may feed the constitutional layer.
Rules in force
A constitutional change counts as a change of meaning only if it alters who may inscribe, what is inscribed, who controls the register, or the temporal scope of the inscription. Anything else is logged as formal change.
Two or three coders, same units, separate rounds; thresholds fixed before results; disagreements resolved by a new codebook version, never by majority vote; codebook freezes F1 (exploratory) and F2 (promotion).
Problem-anchored purpose · joint construction demonstrated · one account, not two · balance in the core analysis · explicit evaluation assumptions · power, context and ethics as criteria · quality control applied.
Decision log
A curated, dated log of the decisions and changes of criterion behind the book. Keeping it public is part of the method: a reader should be able to see where the author changed his mind, and why.
Full log with dates and superseded entries: in the repository, DECISIONS.md.