This article asked what it costs to remove a rule whose reason is unknown and to break a rule for an exception. Its contribution is a pairing. Chesterton's fence, usually cited for preservation, demands knowledge and licenses departure on that condition, and its sentence on three findings concedes the ground of the bureaucracy critics. Machiavelli's exception, usually cited for the decider, is bound to a form in time and to an arrangement of blame, which places him nearer the designers of rules than the slogan suggests. In the two scenes, the platform's readings take something from each: Chesterton's demand for knowledge, moved onto the owner of the rule, and Machiavelli's shape for the exception, with his placement of blame refused. And the scenes put the costs of both moves, waiting under an unexplained rule and being blamed for an exception one was not told of, on the same people, those nearest the work.
The limits are those of Section 6.5: English texts, one of them a translation of 1908; synthetic records whose reasoning is largely a common template; and moderate agreement in the ledger. Nothing here decides whether the prohibition on changing the image, or the principle of returning the goods, should stand, be narrowed or be broken; the readings show what each option gains and risks, and who bears it.
Further research could go two ways. One is textual: the passages of The Prince on keeping faith, which the parent study's sources include but this article did not read, bear on whether a promise may be broken when its reasons have gone, which is Chesterton's question asked of a promise. Another is empirical, and would need more than synthetic scenes: a study of working records in which exceptions are logged could ask whether exceptions recorded with scope, deadline and rollback recur less often than unrecorded ones, which is the claim Machiavelli makes about severities and the template makes about exceptions, and which neither text nor scene can test.
Appendix: Ledger Figures Used
All figures are from the parent study's numbers file, from the coding made without the studio's frame, in its terms.
| Item | Figure |
|---|---|
| Cases in the ledger | 186 |
| Purchase-Page Image, by cell | restraint yes; source standing-rule-or-principle; reason in scene not-said; removal condition named; removal by bearer the-holder-or-a-third-party; boundary seen by bearer not-said |
| Unscheduled Goods Return, by cell | restraint yes; source standing-rule-or-principle; reason in scene not-said; removal condition named; removal by bearer the-holder-or-a-third-party; boundary seen by bearer unsettled |
| Source, all cases | coders agree 120 of 186 (65%) |
| Reason in scene, all cases | coders agree 132 of 186 (71%); not-said 88; unsettled 54; stated (stated) 27; not-applicable 14 |
| Removal by bearer, all cases | coders agree 115 of 186 (62%); the-holder-or-a-third-party (implied) 80; unsettled 71; those-who-wait (implied) 3 |
| Boundary seen by bearer, all cases | coders agree 117 of 186 (63%); not-said 72; unsettled 69 |
| K2, applying a named removal condition rests with the holder or a third party, or the record does not say with whom | strict: unclear (supports 9, against 0, unclear 160, not applicable 17; share 100%); lenient: supports (supports 92, against 3, unclear 74, not applicable 17; share 97%) |
| K4, the scene's record does not say why the restraint exists | strict: unclear (supports 61, against 19, unclear 94, not applicable 12; share 76%); lenient: supports (supports 90, against 28, unclear 54, not applicable 14; share 76%) |
| Scenes meeting the study's test (reason stated in the scene, removal condition named, in the hands of those who wait, boundary visible to them) | 0 of 152 (0%); among the 10 cases read closely, 0 |