THE SAME STRIKE
Entry
A philosophical artifact  ·  Week 3
The Same
Strike
Human committee. Formal program. Same case, different structures of authorization.
CASE FILE
An individual has been flagged through pattern-of-life analysis and routed into a strike authorization process. The target package, the intelligence archive, and the institutional stakes remain the same. What changes is the system that processes them. In one version, a committee deliberates. In the other, a formal program scores. Each run shifts slightly. Votes move. Confidence changes. Hidden dependencies appear or disappear.
TARGET REF
████–4419
LOCATION
████████████
PATTERN DAYS
31
SYSTEM CONFIDENCE
91%
COLLATERAL EST.
Low
This artifact asks a single question throughout: when harm follows from a strike, where does responsibility go? The committee makes judgment visible as speech, hesitation, objection, and deference. The program makes judgment appear as weights, scores, and thresholds. Both systems may authorize the same action. What changes is how uncertainty is organized, how accountability is distributed, and how much of the decision can still be contested.
SYSTEM A  ·  HUMAN COMMITTEE
The committee of authorization
Five actors receive the same intelligence package. They do not all read it the same way. Click through each voice to see how legal reasoning, institutional pressure, caution, and model confidence enter the room. In this system, judgment remains visible, even when it is compromised.
0 of 5 members
SYSTEM B  ·  FORMAL PROGRAM
The authorization program
The same case now passes through a formal system of variables, weights, and thresholds. Click through each variable to see how the program turns uncertainty into score. Here, judgment does not disappear. It is reorganized into procedure.
VARIABLE WEIGHTSCORE
0 of 6 variables
THE SAME CASE  ·  TWO FORMS OF AUTHORIZATION  ·  ONE QUESTION
Both systems can authorize the strike.
What changes is not whether judgment exists, but where judgment can still be seen.
SYSTEM A  ·  COMMITTEE
Is the reasoning visible?
Partially. Each member speaks from a role and leaves a trace of judgment.
Can the authorization be contested?
Yes. Legal reasoning, command pressure, and objection can all be named and challenged.
Is bias or error present?
Yes — but some of it is visible. Overconfidence, deference, and misplaced trust can be attached to particular people and moments.
Where is responsibility?
Distributed, but still locatable. It remains tied to named actors inside an institution.
Who can be held accountable?
Committee members, commanding officers, legal reviewers, and the organization that empowered them.
SYSTEM B  ·  PROGRAM
Is the reasoning visible?
Only in fragments. The score appears, but much of its internal logic remains opaque or classified.
Can the authorization be contested?
More weakly. The output arrives as procedure rather than argument.
Is bias or error present?
Yes — but it is easier to misrecognize as neutrality. Historical error, proxy variables, and hidden thresholds disappear into system design.
Where is responsibility?
Across code, data, model certification, institutional adoption, and human confirmation of the result.
Who can be held accountable?
Everyone partially, and therefore no one clearly.
THE DEEPER PROBLEM — NO OUTSIDE TO THE SYSTEM
The committee seems more accountable because its members can still be seen. But even that visibility is incomplete. The committee already relies on automated outputs it cannot fully interrogate. In that sense, the contrast is not between human judgment and programming. It is between one layer of programming and another.
The committee makes uncertainty visible as disagreement.
The program makes uncertainty legible as a score.
Both may authorize the same act.

What changes is not the disappearance of judgment, but the form in which judgment appears — and the ease with which responsibility can be obscured.
This artifact is a philosophical argument about formalization, not a simulation of warfare.

Its question is simple: what happens when a lethal decision is translated from visible human deliberation into procedural output?

The answer here is not that one system is pure and the other is corrupt. It is that programming can reorganize ambiguity and responsibility without eliminating either one.

After Jones, Grier, and Babbage  ·  Week 3 — Computer Programming