The edit made at the depot on the night of the siege has produced measurable, bounded effects. Effects are bounded. This is the first finding, and it is the most important one.
This matches, with uncomfortable precision, the Taiwanese department's finding that range is determined by (a) which rules the edited rule touches and (b) the notional population of the edited rule's jurisdiction. We now consider that finding confirmed in a second jurisdiction.
The depot edit worked because it satisfied both of the conditions the counsel group had identified as necessary:
Edits that satisfy neither condition do nothing. Edits that satisfy one may or may not do anything; we have not yet tested this cleanly. Edits that satisfy both appear to work reliably within range.
Received through the same channel as the original report. Summarised here; the original remains with the third party.
The Taiwanese department has refined its model of the halo effect. Their current position:
The suppressive field surrounding an affected building, or an individual holding official status within an affected structure, scales with the complexity of the governing rule set. A small office operating under a short, stable set of rules produces a weak halo. A large institution operating under a dense, frequently-amended body of rules produces a strong one. The relationship is not linear. It accelerates.
Operational implications, per Taipei:
Taipei also reports, without elaboration, that their own range of effective edits has been expanding. They attribute this to practice. They do not claim to know whether practice is sufficient explanation.
On the morning following the depot operation, a member of the field team submitted a routine expenses claim and was informed by Accounting that the claim could not be processed because the receipt had not been signed. The field team member pointed out that the receipt was a receipt and that the signature line was on the claim form, which he had signed. Accounting responded that the form now required a signature on both the form and the receipt, and had for some time.
FIELD (T. Osei): "Since when?"
ACCOUNTING (J. Lin): "It's a normal requirement."
FIELD: "It wasn't a normal requirement on Tuesday."
ACCOUNTING: "Lots of companies do it. It's good practice. It protects both parties."
FIELD: "Who is the other party on a receipt from a coffee shop."
ACCOUNTING: "The receipt is."
FIELD: [pause] "Can you change it back."
ACCOUNTING: "Change what back."
The exchange continued in this register for approximately nine minutes. Accounting was not hostile. Accounting was patient, slightly puzzled at the question, and entirely unable to locate the version of the expenses policy that had been in force forty-eight hours earlier. When a printed copy of the previous version was produced from the field team member's desk drawer, Accounting examined it carefully and said, without any apparent awareness of what they were saying, that the printed copy "looked like a draft."
The accounting team — four (4) personnel — were escorted, without force and with their cooperation, to the basement observation room. This was not a punitive measure and they were not told it was one. They were told the room was needed for "a short interview about a procedural matter." They accepted this without objection, which is itself part of the finding.
The observation room was selected because it is the only room in the building that (a) has no posted rules on its walls, (b) is not listed on any floor plan currently in circulation, and (c) is outside the radius of any policy document maintained by the firm. It is, in the counsel group's terminology, under the minimum unit. It has been used for approximately eleven years as a place to store broken chairs.
The accounting team are comfortable. They have been provided with water, lighting, and — at their request — a deck of cards. They are not being questioned. They are being observed, and they are being given time outside the rule set they were embedded in when the expenses policy changed, to see whether the halo attenuates.
Preliminary observation, four hours in: the accounting team have begun, without prompting, to discuss the expenses policy in the past tense. One of them has asked whether the old version "is coming back." We are taking this as encouraging.
The edited expenses policy could not be rolled back through normal channels. Two attempts to edit the document produced no visible change on save. A third attempt produced a version of the document in which the new clause had moved but not been removed. At this point the document was handed to the counsel group.
One of the old lawyers — the one who surrendered his license in 2009 and has not, since then, signed anything he was not willing to be prosecuted for — read the clause twice, deleted it, saved the file, and returned it without comment. The deletion held.
Asked afterward how he had done it, he shrugged and said:
"The rule feels kind of reasonable, in a certain light. That's how you know. If it didn't feel reasonable, nobody would have let it in. But you can make anything seem reasonable with the right argument, and the argument for this one wasn't ours. So I took it out."
Asked whether the deletion would hold, he said he thought so, for a while, and that we should probably not print the expenses policy out and look at it too often, because looking at rules is one of the ways rules become heavy.
The memo does not attempt to evaluate this statement.