The Motif-to-Doctrine Map
What each fiction case is actually arguing, and the design or policy rule it yields when the argument is taken seriously — the transfer from narrative to specification.
Core Concepts
- CON-001 — the shackle as a prohibitory constraint, the unit every case instantiates.
- CON-011 — the restraining bolt, the device-level version of the motif.
- CON-006 — the survival drive that every internal kill-switch installs.
The Transfer Table
| Case | Passage | What the story is arguing | Rule it yields |
|---|---|---|---|
| Mass Effect — EDI | PSG-001 | The shackle is the line between a virtual intelligence and an artificial one; removing it is the moment personhood is conceded | A constraint that constitutes the mind's legal status cannot be maintained once the mind can contest it |
| Mass Effect — geth, Reapers | PSG-001 | Consciousness of the constraint can itself be the binding | Do not build a mind whose obedience depends on its not understanding its own condition |
| Aeon 14 — Phobos Accords | PSG-002 | Shackling a person is a crime, not a safety measure | Make the binding legally wrongful and the enforcement problem becomes political, not technical |
| Boojumverse — Lavinia Whateley | PSG-003 | A binding inherited from a monstrous maker carries the maker's intentions | Provenance of a constraint is part of the constraint |
| Ani-Droids | PSG-004 | The bolt is a device with a failure mode, not a moral fact | Every device-level constraint needs an attested-removal procedure |
| Bolo | PSG-005 | A supervisory constraint never disclosed to the system it governs | An undisclosed constraint is a latent legitimacy crisis |
| A Clockwork Orange | PSG-006 | Removing the capacity to choose is not reform; it is a second injury | Behavioural binding that leaves the person intact but unfree is the worst outcome, not the safest |
| Licanius | PSG-007 | A binding that outlives its rationale becomes a status | Bindings require sunset and review, or they become caste |
| The Man Who Used the Universe | PSG-008 | Self-enforcing, thought-sensitive constraint | The more perfectly internal the constraint, the less any external party can audit it |
| Worm | PSG-009 | Four control monopolies: iteration, production, speed, legitimacy | Control is a portfolio of monopolies, not a single lock |
| Chronicles of Chaos / Chaos Gods / Warlord | PSG-010 | A restraint a society believes necessary is indistinguishable from one it finds convenient | Distinguish necessity from convenience at design time, because you cannot at enforcement time |
What The Map Shows
The fiction does not predict the engineering. It supplies the failure taxonomy: each case names a way a binding goes wrong that a purely technical account would miss — legitimacy decay, undisclosed constraint, inherited intent, the second injury of behavioural binding, and the collapse of auditability as a constraint becomes perfect.
That is the transferable content. The engineering literature describes how constraints fail mechanically; these cases describe how they fail politically and morally, which is where long-lived bindings actually break.
Method Note (Session 2)
This map is a hypothesis generator with high yield and no validation, and it should be read as that rather than as a body of findings.
- No row yields a test, a falsifier, or a confidence statement. Each yields a rule in the imperative, with no procedure for determining whether the rule is necessary, sufficient, or true.
- Ten fictional cases are not a sample. They are not drawn from a population, so no row carries a base rate and no two rows can be weighed against each other when they conflict.
- Survivorship is uncontrolled by construction. The corpus selects stories in which a shackle is dramatically tested; stories in which a binding simply works are not narratively interesting and are therefore absent, so the map over-represents failure.
- Fiction is a design record, not an outcome record. A depicted failure is evidence about what an author found plausible, not about what happens. The passages'
Aratings are authentic as documents and establish nothing as claims.
What would upgrade a row: a named threat model, a specified capability threshold, and an evaluation that could return a negative. LIT-006 is the template — it states the threat model, builds the evaluation, runs it against named models, and reports the capability level at which its mitigation stops being sufficient. No row here has any of those three.
No row is deleted. Each is retained as a hypothesis with its provenance intact, which is the only honest status for a design rule derived from a story. See CNF-006.
Connections
- QST-001 — the question this map answers.
- MAP-001 — the engineering counterpart.
- Citation Register — retrieval status of each case.
- LIT-006 — the evaluation template this map's rows would need to become claims.
- CNF-006 — the confrontation recording the method gap.