[The Electronic Oracle] ② The Questions to Ask When You Face a Model: A Checklist for Citizens and Policymakers
[The Electronic Oracle] ② The Questions to Ask When You Face a Model: A Checklist for Citizens and Policymakers
This checklist is not mainly for model builders. It is for model users—citizens, journalists, policymakers, and administrators.
Question 1: “What number is currently serving as our ‘authority’?”
(Focus: guarding against false certainty)
A model becomes an oracle when its output—stripped of context—poses as the essence of reality.
Checklist
- Is the number accepted without proof?
- Is this number used as the sole justification for a policy decision?
- Have the conditional statements ("if") attached to the number been cut from meetings, reports, or documents?
Examples
- "Next year's growth rate is 1.2%." — Did the condition "if exchange rates soar" disappear, leaving only the figure?
- "The reproduction number (R) is 1.3." — Is the realistic limitation of "data aggregation delays" hidden behind this digit?
๐ To understand deeper: This question connects to the concept of 'Precision vs. Accuracy' in Post ④.
Question 2: “Are the assumptions public? Who holds the authority to modify them?
(Focus: Securing transparency and democracy)
A model's conclusion is ultimately a product of its Assumptions. If assumptions remain in a black box, verification, rebuttal, and modification become impossible. At that moment, the model becomes an authority outside the public sphere. It becomes a dictatorship.
Checkpoints:
Is the Structure (causality, delays, feedback) publicly available?
Are the Numbers (initial values, coefficients, delay times) publicly available?
Is the Boundary (what was excluded) clearly explained?
Case Study:
Behind the conclusion of a "teacher surplus for the next 10 years," does a rigid assumption hide: "the number of students per class will not change"?
Question 3: “What is deleted when translated into policy language?”
(Focus: Restoring context)
When a modeler's complex output is translated into a "one-line summary," critical information evaporates. We must bring these lost elements back to the table.
The Deletion List (What is often lost):
- Conditional Sentences: "If A, then B" becomes "It is B."
- Range of Uncertainty: Scenario variations are collapsed into a single average.
- Time Delays: Today’s effects get airtime; five-year side effects vanish.
- Feedback/Side Effects: The structure explaining "why it happens" is removed, leaving only "we must do it."
Case Study:
- Behind the one-line conclusion —“We expect an electricity shortage, so let’s build power plants” — has an alternative scenario—“efficiency policies could reduce demand”—been deleted?
๐ To understand deeper: How do we restore this deleted context? By monitoring through Externalization (Post ③) and Structure (Post ④).
[Epilogue] These three questions are not intended to neutralize models. Instead, they aim to dethrone models from their status as "mysterious prophets" and transform them into "useful tools" we can wield proactively. With these questions in mind, let us now examine the three standards that pierce the essence of modeling (Post ④) and the philosophy of assumptions (Post ③).

Comments
Post a Comment