The Book · Chapter 22 of 28
Chapter 22Source-to-System Legal Mapping
What degree of mapping is proportionate to a function, and how can the method expose uncertainty without producing a false appearance of completeness?
The chapter develops
Source-to-System Legal Mapping, the method of the book.
Source-to-System Legal Mapping
Legal authority must be mapped systematically from source to computational action and remedy.
Doctrine 20 of the Book’s twenty-one. A proposed formulation, not an enacted rule.
Summary
Legal inventories and system diagrams often leave the decisive translation choices between them unexplained. This chapter develops Source-to-System Legal Mapping around the legally consequential pathway, following authority across product and organisational boundaries to practical remedy. Ten stages, artefacts and decision gates connect sources, legal time, competence, interpretation, data, computability, safeguards, deployment and continuing correction. The method draws on legal knowledge-system isomorphism and Rules as Code while treating translation loss, institutional ownership and remedial capacity as explicit questions. It also tests its own weaknesses, including documentation theatre, gate capture and the apparent completeness of a finished dossier. Proportionality governs depth without supplying an invented calibration, and the reasons framework distinguishes ownership of a deployment from judgment on an individual case. The dossier is proposed as evidence for review, procurement and design; it creates no authority, certifies no legality and must remain capable of supporting refusal to automate.
- legally consequential pathway
- Source-to-System Dossier
- legal proposition register
- competence and control
- computability classification
- deployment authority
- decision ownership
- continuing legality
The chapter text
The text of this chapter is read in the Codex, by members and owners of the Book. Membership opens every published chapter; the Book gives you all twenty-eight for good.