The Machinery of Bias · The state · concept v0 · 2026-08-17 · poster 4 of 4 (ecosystem · register · cascade · state)
Inside one engine the same machine, two states, two outputs
The cascade showed two people meet the same boxes and produce two different
cascades. This poster opens the engine and shows why. Before anything turns, the engine reads
its state — the dials: how starved is security, how fragile is standing, how much capacity is
left to absorb a hit — and the ranking those dials produce. The turning parts are identical
in both panels. An individual is not a fixed machine; an individual is a state.
Person Asecurity starved · mortgage due · standing fragile
Output: a claim. Security ranks first, so the engine reaches for the
explanation that fits the alarm — the red thread starts here, and A's state travels with it
(the same mortgage is what the economic layer's hold will grip, four stops later).
Person Bbuffer in place · options open · same engine
Output: release. No dial is screaming, so reflection gets to rank first —
the engine runs the same turn and returns the boxes to being boxes. Most signals die here.
How to read this — three sentences, one each
The dials are the stateWhat the engine reads before it turns: security,
standing, capacity — and behind them the whole needs ladder. States move week to week; the machine
does not.
The ranking is the decisionWhichever need ranks first chooses which
explanation gets reached for. Nobody decides this consciously — the ranking is the decision.
The output inherits the stateA claim born from a starved dial carries that
dial with it — which is why distant layers (the hold, the stage) grip some people and not others.
Honest limits. The engine drawing is schematic: the dials and the L1 part words
(needs · ranking · values · face · reflection) are settled; the full engine-part inventory (~52
parts, six kinds) is still candidate-grade and deliberately NOT asserted here — the cogwheels are
drawn as machinery, not as a parts list. Every drawn element sits in a replaceable slot for
Michael's own SVGs.
The state · concept v0 · the engine-interior view the cascade spec reserved, with the
content assigned 2026-08-17 · drawn in-house; graphics replaceable · poster 4 of 4:
ecosystem · register · cascade · state
stimulus.se · CC BY-SA
What this is
The fourth poster, reinstated. The earlier drop rested on a misunderstanding — the
question was whether the engine drawings could be made in-house. They can: everything on this board
(dials, gears, intake, outputs) is SVG drawn directly in the file, exactly like the threads and
hatches on the other posters.
Your SVGs — optional upgrade, not requirement
Nothing needs exporting for the concept to stand. If you later draw the engine parts yourself,
each drawn element here is a slot: swap the gauge, the gear cluster, the intake — same mechanism as
the layer icons. The concept survives any art swap.
Decisions taken (reversible)
Twin-panel form — the same engine twice is the whole argument; one engine with two
overlays was tried mentally and rejected as unreadable.
Three dials + ranking card — security, standing, capacity are the three the moving-boxes
trace actually uses; the full needs ladder stays in prose.
The accent appears once: A's output thread — the birth of bias-in-motion. B's output is
the grey release circle from the cascade, same vocabulary.
Open for your ruling
① Dial set: these three, or a different cut of the needs ladder?
② The ranking card: keep visible, or fold into the panel text?
③ Does the twin-panel silhouette work at thumbnail size, or should the two engines stack?