https://www.computableauthority.com Research entries and syllabus lectures from the Computable Authority field guide, as they're published. en Mon, 10 Aug 2026 10:34:19 GMT https://www.computableauthority.com/research/what-is-computable-authority https://www.computableauthority.com/research/what-is-computable-authority Authority is the right to decide. Computable authority is that same right, expressed so a machine can exercise it inside defined limits — and prove it did. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/research/why-ai-needs-machine-readable-policy https://www.computableauthority.com/research/why-ai-needs-machine-readable-policy Capable models with no authority layer are not governed systems. They are fast improvisation with an institution's name attached. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/research/the-policy-versioning-problem https://www.computableauthority.com/research/the-policy-versioning-problem A decision is only defensible against the rule that was in force when it was made. Almost no institution can produce that rule on demand. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/research/the-definitions-problem https://www.computableauthority.com/research/the-definitions-problem Most policy disputes are not about rules. They are about what a word meant, to whom, and when. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/research/from-regulation-to-execution https://www.computableauthority.com/research/from-regulation-to-execution The compilation pipeline: how a published instrument becomes an artifact a runtime can evaluate — without losing its provenance. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/research/the-future-of-governance-infrastructure https://www.computableauthority.com/research/the-future-of-governance-infrastructure Institutions will exchange authority the way systems now exchange data — and that requires shared infrastructure, not shared documents. Three prior efforts got partway there; none closed the gap. Fri, 07 Aug 2026 14:38:05 GMT https://www.computableauthority.com/syllabus/policy-problem/why-policies-fail-machines https://www.computableauthority.com/syllabus/policy-problem/why-policies-fail-machines The Policy Problem — Modern institutions rely on policies as the primary mechanism for expressing authority. However, policies were designed for human interpretation rather than machine execution. As artificial intelligence systems increasingly participate in institutional decisions, a fundamental challenge emerges: how can authority be represented in a form that machines can execute and independent parties can verify? Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-problem/limitations-of-documents https://www.computableauthority.com/syllabus/policy-problem/limitations-of-documents The Policy Problem — The document is the dominant carrier of institutional authority, and it is a carrier with no defined behaviour. This lecture examines what a document can and cannot do as a governance instrument, and why format modernisation — PDF to HTML to XML — does not by itself close the gap. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-problem/human-vs-machine-readable-authority https://www.computableauthority.com/syllabus/policy-problem/human-vs-machine-readable-authority The Policy Problem — Machine-readability is often treated as a downgrade of legal text. This lecture argues the opposite: the machine-readable form is a second, disciplined expression of the same authority, and the two forms must be governed together. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-problem/why-ai-creates-urgency https://www.computableauthority.com/syllabus/policy-problem/why-ai-creates-urgency The Policy Problem — Interpretation has always been unrecorded, and institutions absorbed the resulting variance because human throughput was low. Autonomous systems remove that slack. This lecture examines why the authority layer becomes load-bearing precisely when execution becomes machine-speed. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/policy-decomposition https://www.computableauthority.com/syllabus/policy-engineering/policy-decomposition Policy Engineering — Decomposition is the first unit operation of policy engineering: reading an instrument and separating it into the elements a machine will need. This lecture establishes the method and the discipline of not resolving ambiguity silently. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/definitions https://www.computableauthority.com/syllabus/policy-engineering/definitions Policy Engineering — Definitions decide outcomes more often than rules do. This lecture treats the definition as the primary object of policy engineering: scoped, versioned, and shared across rules. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/rules https://www.computableauthority.com/syllabus/policy-engineering/rules Policy Engineering — A rule is an operative statement binding conditions to a normative outcome. This lecture covers rule form, modality, and the discipline of writing one rule per statement. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/exceptions https://www.computableauthority.com/syllabus/policy-engineering/exceptions Policy Engineering — Exceptions are where most policy failures live. This lecture treats the exception as a first-class object with its own conditions, authority, and expiry. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/conditions https://www.computableauthority.com/syllabus/policy-engineering/conditions Policy Engineering — A condition is the point at which authority meets fact. This lecture examines evaluability: which conditions a machine can test, which require judgement, and how the boundary is declared. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/decision-logic https://www.computableauthority.com/syllabus/policy-engineering/decision-logic Policy Engineering — Decision logic is the evaluable structure that turns facts into an outcome. This lecture covers ordering, completeness, and the requirement that every path terminate in a defined result. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/policy-engineering/contradiction-and-conflict https://www.computableauthority.com/syllabus/policy-engineering/contradiction-and-conflict Policy Engineering — A decomposition can be complete and still be incoherent. This lecture covers the failure modes that appear only once a policy is expressed as structure — the conflicts prose was able to conceal — and treats their detection as a required step before any artifact is issued. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/the-second-system https://www.computableauthority.com/syllabus/observed-system/the-second-system The Observed System — Every institution operates two decision systems: the one it has documented, and the one it actually runs on. This lecture establishes that the divergence between them is structural rather than pathological — a property of how institutions work, not evidence that a particular one is failing. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/decision-boundaries https://www.computableauthority.com/syllabus/observed-system/decision-boundaries The Observed System — If the operating system is not a set of written rules, what is it made of? This lecture introduces the decision boundary — the point at which an institution's answer changes — as the unit that makes an unwritten system measurable rather than merely acknowledged. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/evidence-and-admissibility https://www.computableauthority.com/syllabus/observed-system/evidence-and-admissibility The Observed System — Reconstruction is only as sound as the record it rests on. This lecture treats a decision log as evidence subject to admissibility tests, and establishes the conditions under which a body of decisions can support any claim about a boundary at all. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/reconstruction https://www.computableauthority.com/syllabus/observed-system/reconstruction The Observed System — Given admissible evidence, the operating system can be reconstructed as a structured approximation. This lecture states the extractability thesis — that a latent decision system can be inferred from behaviour — and, just as importantly, the limits of what such inference can establish. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/reconciliation https://www.computableauthority.com/syllabus/observed-system/reconciliation The Observed System — Reconstruction produces a second description of the same institution. Reconciliation compares the two. This lecture argues that the comparison must be made boundary to boundary rather than text to text, and that agreement is as significant a result as divergence. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/observed-system/adjudication https://www.computableauthority.com/syllabus/observed-system/adjudication The Observed System — A divergence is a fact. Whether it is a problem is a further claim requiring further evidence. This lecture separates detection from adjudication and sets the standard of proof required before an institution is told that its practice is causing harm. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/executable-authority/policy-compilation https://www.computableauthority.com/syllabus/executable-authority/policy-compilation Executable Authority — Compilation converts a decomposed policy into an executable authority artifact. This lecture treats compilation as a governed act with inputs, review, and issuance — not a file conversion. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/executable-authority/deterministic-execution https://www.computableauthority.com/syllabus/executable-authority/deterministic-execution Executable Authority — Determinism is what makes an outcome auditable: the same artifact and the same facts must produce the same outcome on any conforming runtime, today and years from now. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/executable-authority/verification https://www.computableauthority.com/syllabus/executable-authority/verification Executable Authority — Verification is confirmation by a party who did not execute the decision. This lecture examines what must be recorded for verification to be possible without access to the executing system. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/executable-authority/policy-versioning https://www.computableauthority.com/syllabus/executable-authority/policy-versioning Executable Authority — Every decision was made under some version of the rules. This lecture covers immutable issuance, effective dates, and replaying past decisions against past authority. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/executable-authority/governance-apis https://www.computableauthority.com/syllabus/executable-authority/governance-apis Executable Authority — If authority is executable, it must be callable. This lecture covers the interface through which systems request an authority evaluation and receive a bound, traceable outcome. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/future-of-authority/ai-native-institutions https://www.computableauthority.com/syllabus/future-of-authority/ai-native-institutions The Future of Authority — An institution whose authority is computable by default operates differently: rules ship as artifacts, human and machine actors share one source of authority, and change propagates through issuance rather than memo. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/future-of-authority/regulatory-interoperability https://www.computableauthority.com/syllabus/future-of-authority/regulatory-interoperability The Future of Authority — Authority does not stop at a border. This lecture examines what is required for artifacts issued by different jurisdictions to be evaluated together without collapsing their differences. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/future-of-authority/computable-authority-lecture https://www.computableauthority.com/syllabus/future-of-authority/computable-authority-lecture The Future of Authority — Returning to the umbrella discipline with the full apparatus in hand: what has been built across the curriculum, and what computability of authority actually claims — and does not claim. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/future-of-authority/policy-ecosystems https://www.computableauthority.com/syllabus/future-of-authority/policy-ecosystems The Future of Authority — Artifacts do not exist alone. This lecture examines registries, dependencies, and what happens when one institution's artifact becomes another's input. Fri, 07 Aug 2026 13:46:48 GMT https://www.computableauthority.com/syllabus/future-of-authority/future-role-of-policy-engineers https://www.computableauthority.com/syllabus/future-of-authority/future-role-of-policy-engineers The Future of Authority — The discipline needs practitioners. This lecture describes the emerging role: its competencies, its position between legal and engineering functions, and the professional questions still unanswered. Fri, 07 Aug 2026 13:46:48 GMT