What's running on the floor, who's running it, and what's leaving the building? The factory floor is an idea, not a visual, so here it is drawn eight ways on one fixture world: a floor plan, qmap, a pixel field, a production line, a loom, shift clocks, a pawn lineup and a control-room wall. Every control drives every form, every mark is one datum, and clicking a mark focuses it everywhere (on the real page it opens the thing).
Lens
Period
Scale
State
Who is working, and where? · lit = worked with that harness in the period · dim = installed, idle · dashed amber = detected only, no sensor · red = errored
200 people · 248 stations · 6 harnesses — 19 stations unseen, Hermes on 9, 2 sensitive exits
Form A
Floor plan
Strong at where, and who's dark — people and equipment in one place; ghosts and andon lamps sit in their zone; positions never move, so the eye learns the map. At 1,500 each desk drops to one dot (its strongest machine) and zones become density blocks.Weak at relationships — nothing says which providers a machine talks to, or what leaves.
worked in periodinstalled, idleerroreddetected only (no sensor)station (desk) · pips = its installsandon: errored / criticalandon: needs a humanzone area = stations · positions never re-sort
Form C
Pixel field
Strong at scale and calm — 1,500 installs still fit in a glance, the all-clear is a quiet field, trouble is spatial. Holds at 1,500 by shrinking pixels to 5px.Weak at what is running (harness identity lives in the hover) and anything about flows or exits.
Platform 45
Payments 38
ML Research 31
Mobile 33
Data Eng 23
Web 31
Support 16
Security 8
Sales Eng 14
Finance 6
Legal 0
Design 7
Unassigned 16
worked in periodinstalled, idleerroreddetected only (no sensor)one pixel = one install
Form D
Production line
Strong at who runs what and what leaves, in one image — teams → harnesses → providers → data classes on one width scale; Personal accounts is its own node.Weak at place — no stations, no people; hairball risk, so at 1,500 the long tail of teams folds into one node.
TeamsHarnessesProvidersData out
width = tokens in 30d, one scale across all four columnsordinary data / flowcustomer data · PIIsecrets & keysdetected only — drawn at floor width, tokens unknown
Form E
The loom (teams × harnesses)
Strong at who runs what, precisely — every thread segment is one team × harness cell; absence reads as a hairline, detected-only as a dashed amber thread.Weak at activity over time and the station view; at 41 teams columns get narrow and labels tilt.
vertical thread weight = people in the team · horizontal thread weight = tokens in the perioddotted hairline = the team doesn't use it (absence, not zero-width)detected only (floor weight)
Form F
Shift clock
Strong at when — each team's working day as a shape; late teams and night work jump out; small multiples compare shapes.Weak at the equipment (no harness or station at all), and lenses with no hourly series (violations, coverage).
The floor
2.6B · peak 14:00
Platform
628.8M · peak 14h
Payments
251.4M · peak 16h
ML Research
496.4M · peak 17h
Mobile
163.9M · peak 15h
Data Eng
135.3M · peak 12h
Web
348.2M · peak 11h
Support
101.7M · peak 16h
Security
35.1M · peak 20h
Sales Eng
54.3M · peak 12h
Finance
37.0M · peak 15h
Legal
quiet
Design
149.9M · peak 21h
Unassigned
204.2M · peak 14h
petal = one hour of the day (org-local, 00 at the top) · length = tokens in that hour across 30d · each dial on its own scale — shape is when, the number under it is how much
Form G
Pawn lineup
Strong at life and personality — the mascot moment; awake vs asleep is instant; the harness badge names the machine.Weak at scale: 268 pawns is already a crowd, and at 1,500 only the installs that need someone stand up. No per-harness pawn art, and errored shares the awake body.
Platform40 lit · 4 idle · 1 errored
Payments25 lit · 10 idle · 3 detected only
ML Research23 lit · 0 idle · 7 detected only · 1 errored
one pawn = one install · awake = worked in 30d · asleep = idle · badge = harness · plate under the pawn = the lens mark? = detected onlyerrored pawns share the awake body (no per-state art with decorations off) — the red plate carries it
Form H
Control-room wall
Strong at comparing teams at wall distance — a fixed grid of mini-monitors, each lamp a count, each sparkbar its own shift. Holds at 1,500 as 41 small monitors.Weak at the whole as one image; drifts toward "a dashboard of cards".
Platform28 ppl
40/45machines lit
40 working1 red2 need you1 unseen
Payments23 ppl
25/38machines lit
25 working2 red3 unseen
ML Research17 ppl
23/31machines lit
23 working2 red1 need you5 unseen
Mobile19 ppl
29/33machines lit
29 working2 need you
Data Eng16 ppl
14/23machines lit
14 working7 unseen
Web21 ppl
30/31machines lit
30 working1 unseen
Support17 ppl
10/16machines lit
10 working1 unseen
Security8 ppl
8/8machines lit
8 working
Sales Eng14 ppl
4/14machines lit
4 working4 red7 unseen
Finance8 ppl
6/6machines lit
6 working1 unseen
Legal6 ppl
0/0machines lit
1 unseen
Design10 ppl
6/7machines lit
6 working1 unseen
Unassigned13 ppl
14/16machines lit
14 working2 unseen
one monitor = one team, in a fixed position · big number = the lens · bars = the team's 24h shift (own scale) · each lamp is a count, never the team's colour
Read
My read
Pick A for the hero, D for the second block
The floor plan is the only form that shows people and equipment in one place, which is the page's reason to exist, and it keeps ghosts and lamps in their zone. The production line answers the other half — who runs what and what leaves — in one image. Together they are the /fleet page; everything else is a supporting block or a different surface.
C is the Home exhibit
The pixel field is the calmest all-clear and the only form that stays a glance at 1,500 without folding anything. It loses harness identity, which Home doesn't need. It could be the compact floor block in Home's H6 slot.
E and F become the supporting blocks
The loom is an honest matrix with weight; as a table (F2 on the supporting page) it carries the Claude Code lens better. The shift clock reads well for a few teams, but the team × hour strip (F3) compares 40 teams better than 40 dials.
B, G and H are other surfaces
qmap is the showroom and should wait for c101's pawns; judge its layout, not its marks. The pawn lineup is delightful at 20 and a crowd at 200 — keep it for the team detail page or the "needs you" strip. The control-room wall is A's wall mode by another name; I'd fold its lamps-as-counts into A's zone headers rather than ship it separately.
Judge
What to try, and what to look for
Flip the scale to 1,500
A drops to one dot per desk, C shrinks pixels, D folds the tail, G stands up only what needs someone, B folds people to one per team. Which still reads as a floor rather than noise?
Flip the state to All clear
No ghosts, no lamps, no amber. Does A look like a finished room and C a calm field? D should lose its amber ribbons and the Personal accounts door entirely.
Flip the state to First run
Every station stands in one Unassigned room. A shows one big zone with a Map-teams door; H shows one monitor. Is that a designed state or an empty one?
Walk the lenses on A and C
Activity → Coverage → Violations: positions stay put and only the ink changes. The ghosts should stay dashed amber under every lens — unseen is structural, not a lens value.
Pick Harness → Claude Code
A lights Claude Code machines inside every desk; D lights one ribbon family through to the providers; E lights one thread. Which one answers "how far has it spread"?
Change the period to 24h
Most machines go dim. The floor plan and pawns show "who is on shift today"; the shift clocks shrink to today's shape. Try wall mode at 24h — that's the NOC screen.