|
|
xi | |
Acknowledgements |
|
xii | |
|
|
1 | (42) |
|
1.1 The Structure of the Argument |
|
|
2 | (2) |
|
1.2 Rebooting `Code as Law' |
|
|
4 | (15) |
|
|
7 | (2) |
|
|
9 | (1) |
|
|
10 | (1) |
|
d Code is both More, and Less, than Law |
|
|
11 | (2) |
|
|
13 | (2) |
|
|
15 | (2) |
|
Digital Rights Management |
|
|
17 | (2) |
|
1.3 Aspiring to Legitimacy in Code |
|
|
19 | (3) |
|
a From Operation to Production |
|
|
20 | (1) |
|
Fuller's Internal Morality of Law |
|
|
20 | (1) |
|
|
21 | (1) |
|
b Towards Digisprudence: Legitimate `Code as Law' |
|
|
22 | (1) |
|
1.4 `Code as Law', Code versus Law, or Something Else? |
|
|
22 | (10) |
|
|
23 | (2) |
|
b Why Not `Compliance by Design'? |
|
|
25 | (4) |
|
Other Notions of `by Design' |
|
|
29 | (1) |
|
c Normative Relationships in Code and Law |
|
|
30 | (2) |
|
The Programmer of the Programmer |
|
|
32 | (1) |
|
|
32 | (7) |
|
a Blockchain Applications |
|
|
32 | (1) |
|
|
33 | (2) |
|
|
35 | (2) |
|
|
37 | (2) |
|
|
39 | (4) |
|
PART I COMPUTATIONAL LEGALISM AND THE RULE(S) OF CODE |
|
|
|
2 A Design Perspective: Code is More than Law |
|
|
43 | (26) |
|
|
44 | (5) |
|
a Real and Perceived Affordance |
|
|
46 | (2) |
|
|
48 | (1) |
|
2.2 Infusing Code with Normativity |
|
|
49 | (18) |
|
|
50 | (2) |
|
b Postphenomenology and Code's Mediation of Reality |
|
|
52 | (1) |
|
c Code Mediating Perception |
|
|
53 | (1) |
|
|
54 | (5) |
|
Affordance and Technological Mediation |
|
|
59 | (1) |
|
e A Spectrum of Technological Normativity |
|
|
60 | (3) |
|
Constitutive and Regulative Normativity |
|
|
63 | (2) |
|
f Technological Constitutionalism |
|
|
65 | (2) |
|
|
67 | (2) |
|
3 A Legal Philosophy Perspective: Code is Less than Law |
|
|
69 | (42) |
|
|
70 | (9) |
|
a Solipsism and Positivism |
|
|
73 | (2) |
|
b Legalism According to Legisprudence |
|
|
75 | (4) |
|
3.2 Computational Legalism |
|
|
79 | (28) |
|
|
80 | (1) |
|
|
81 | (2) |
|
|
83 | (1) |
|
|
83 | (3) |
|
The Absence of Interpretation |
|
|
86 | (1) |
|
|
87 | (1) |
|
Does Code Contain Rules per set |
|
|
87 | (4) |
|
Constitutive and Regulative Rules |
|
|
91 | (4) |
|
Rules for Humans; Rules for Machines |
|
|
95 | (1) |
|
|
96 | (1) |
|
|
97 | (2) |
|
|
99 | (1) |
|
|
100 | (2) |
|
|
102 | (2) |
|
Code as a-legal `Positivism' |
|
|
104 | (1) |
|
e The Veiling of Code's Production |
|
|
105 | (2) |
|
|
107 | (4) |
|
PART II WHAT MAKES A GOOD RULE? |
|
|
|
|
111 | (24) |
|
4.1 Normative Criteria for Law-Making: The Aspirations of Legality |
|
|
111 | (21) |
|
a Input and Output Legitimacy in Law |
|
|
115 | (3) |
|
b Fuller's Internal Morality of Law |
|
|
118 | (3) |
|
c Wintgens's Legisprudence |
|
|
121 | (1) |
|
|
121 | (1) |
|
The Requirement of Justification |
|
|
122 | (1) |
|
Freedom and the Trade-Of F Model |
|
|
123 | (2) |
|
The Principle of Coherence (PC) |
|
|
125 | (5) |
|
The Principle of Alternativity (PA) |
|
|
130 | (1) |
|
The Principle of Temporality (PT) |
|
|
131 | (1) |
|
The Principle of Normative Density (PN) |
|
|
132 | (1) |
|
|
132 | (3) |
|
|
135 | (24) |
|
5.1 Input and Output Legitimacy in Code |
|
|
136 | (4) |
|
|
140 | (5) |
|
a Brownsword's `Technological Management' |
|
|
140 | (2) |
|
b Leenes's `Techno-regulation' |
|
|
142 | (1) |
|
c Koops's `Criteria for Normative Technology' |
|
|
143 | (2) |
|
|
145 | (8) |
|
a Hildebrandt's `Legal Protection by Design' |
|
|
145 | (2) |
|
b Applying Fuller to Code |
|
|
147 | (1) |
|
|
147 | (4) |
|
|
151 | (2) |
|
|
153 | (6) |
|
PART III LEGITIMATING CODE: THEORY AND PRACTICE |
|
|
|
6 The Digisprudential Affordances |
|
|
159 | (48) |
|
6.1 Assessing Decisions, or Assessing Design? |
|
|
160 | (1) |
|
|
161 | (5) |
|
a Contestability as an Overarching Affordance |
|
|
163 | (1) |
|
Affording Evidential Scrutiny to Courts |
|
|
163 | (3) |
|
6.3 From Characteristics to Affordances |
|
|
166 | (39) |
|
|
166 | (1) |
|
Digisprudential Affordance: Choice |
|
|
167 | (9) |
|
|
176 | (2) |
|
|
178 | (1) |
|
|
178 | (1) |
|
Digisprudential Affordance: Transparency of Provenance |
|
|
179 | (1) |
|
Digisprudential Affordance: Transparency of Purpose |
|
|
180 | (2) |
|
Digisprudential Affordance: Transparency of Operation |
|
|
182 | (2) |
|
|
184 | (1) |
|
|
185 | (2) |
|
|
187 | (1) |
|
Digisprudential Affordance: Delay |
|
|
188 | (7) |
|
|
195 | (1) |
|
|
196 | (1) |
|
|
197 | (1) |
|
Digisprudential Affordance: Oversight |
|
|
198 | (2) |
|
|
200 | (3) |
|
|
203 | (1) |
|
|
204 | (1) |
|
|
205 | (2) |
|
7 Operationalising Digisprudence |
|
|
207 | (24) |
|
7.1 The Programmer of the Programmer |
|
|
208 | (3) |
|
a From Primary and Secondary Rules to Primary and Secondary (Dis)affordances |
|
|
209 | (2) |
|
|
211 | (2) |
|
7.3 Integrated Development Environments |
|
|
213 | (3) |
|
a Code Verification versus Legal Proof: Justice being Seen to be Done |
|
|
215 | (1) |
|
7.4 Code and Natural Language |
|
|
216 | (13) |
|
a The Interpretative Affordances of Programming Languages |
|
|
217 | (2) |
|
b The Linguistic Relativity of Programming Languages |
|
|
219 | (2) |
|
c Describing Code Isomorphically |
|
|
221 | (1) |
|
Behaviour-Driven Development |
|
|
222 | (2) |
|
Interpreting Code as a Visual Model |
|
|
224 | (5) |
|
|
229 | (2) |
|
8 Rebooting Code as Law: Conclusions and Next Steps |
|
|
231 | (10) |
|
8.1 The Contemporary Relevance of Digisprudence |
|
|
232 | (2) |
|
|
234 | (5) |
|
a The Future of Compliance by Design |
|
|
234 | (2) |
|
|
236 | (1) |
|
c Legitimacy Impact Assessment' |
|
|
237 | (2) |
|
|
239 | (2) |
Bibliography |
|
241 | (19) |
Index |
|
260 | |