# 2026-07-08 — Computer visual language: territory at a glance

```
Type: log
```

Design session with Cameron, riffing off the fresh rack asset: the way a
server *looks* is critical ground truth — you should be able to glance at
the world and know which machine is yours, which ones you own, where your
core is ("let's do orange"), whether there are tasks on them, and roughly
what each is doing. Then, mid-session, the widening move: this is not a
rack feature. Desktops, phones, cameras — all computers — must share the
exact same visual language, because "I own that desktop / this server /
that phone" is one sentence. Focus prototyping on the rack; keep the
language portable.

## What the baseline showed

Shot the pre-session tester states (dead/powered/core) first:

- **Core read cooler than powered** — the cold `SIGNAL` strip on the core
  vs the amber strip on a merely powered rack was exactly backwards
  against Cameron's "orange = core" instinct.
- **The amber fill light washed the dead chassis warm** — presence must
  be LED-owned or ownership can never read. The tester's warm scene
  light is gone.
- **Powered and mine were conflated** — amber meant "any machine that is
  on", so there was no ownership axis at all.

## The synthesis: one signal kit

Spec: [interface/computer-visual-language.md](../interface/computer-visual-language.md)
(DRAFT). Five signals on every computer class: power dot (cold, foot),
presence LEDs (amber strictly = mine; foreign activity in dim cold
signal), status strip (ownership banner), segmented activity bar (task
load; pulses while tasks run — *what* it does stays cursor/intel, the
mesh only says *how much*), and the core spine — a full-height amber
beacon, unique geometry, exactly one in the world. Decision captured in
the constitution's log; the claim-mark treatment is [OPEN] across three
tester-rendered options.

## Renders

Five-state lineup (dead | foreign | idle | busy | core), one per claim
style:

![ladder lineup](2026-07-08-computer-visual-language/lineup_ladder.png)
![ring lineup](2026-07-08-computer-visual-language/lineup_ring.png)
![wash lineup](2026-07-08-computer-visual-language/lineup_wash.png)

Close-ups: foreign (all cold, zero warmth) and core-with-ring shot from
behind — spine + double ring still say "core" with the front face turned
away:

![foreign](2026-07-08-computer-visual-language/single_foreign_ring.png)
![core from behind](2026-07-08-computer-visual-language/single_core_ring.png)

## Tester changes (src/bin/assets/)

- `RackState` widened: dead / foreign / idle / busy / core (keys 1-5);
  `ClaimStyle` ladder / ring / wash (Q/W/E); `L` toggles a five-state
  lineup; harness kinds extended (`lineup_ring`, `core_wash`, ...,
  legacy `rack`/`powered` still map).
- Busy LEDs and bar segments get per-instance materials plus a `Blink`
  component; `blink_emissives` pulses them out of phase.
- Scene rebuild unified (`rebuild_scene` owns pedestal + racks, sized to
  the view); warm fill light removed; HUD strings ASCII-only (the old
  mid-dots rendered as tofu in the default font).

## Open with Cameron

- Claim mark pick: ladder / ring / wash. My recommendation in the spec:
  **ring** as primary (only treatment that survives map zoom;
  generalizes to any chassis), keeping wash's furnace cavity for the
  core alone.
- Foreign-activity-in-cold-signal is my proposal, surfaced for a yes/no.
- Next asset to prove portability: desktop or camera speaking the same
  kit.

## Checks

`./tools/check.sh` (fmt, tests, clippy both feature sets, bevy build,
spec lint); harness runs exited Success for all captured kinds.

## Part two — the riff widened

Cameron answered the opens and kept going, one voice-note riff that
became three captures (all same-day decisions in DESIGN.md's log):

- **Ring decided; foreign teal confirmed.** The spec flipped to READY;
  ROADMAP #32's HOLD lifted, dispatch line added.
- **One machine, one job + work as visible tokens** — continuous
  apportioning is out; day-job demands stack on machines as tokens,
  modes consume them at machine efficiency, byproducts route over
  network links (network speed researchable), unrouted attention piles
  are exposure. Synthesis pushed in the spec: tokens are the flow
  substrate's quanta rendered (one sim truth), and the token palette
  maps onto existing color meanings (work = cold signal, attention =
  crimson, research = bone; amber never a token) instead of the riff's
  green/yellow/blue — PROPOSED, awaiting Cameron. New DRAFT spec:
  mechanics/machine-work.md; ROADMAP #33, flagged against the
  IN-FLIGHT #25 compute-processes worktree (this refines its target —
  delegation, not splitting).
- **The dark opening** — the tutorial is the fog contract played
  slowly: one lit machine in blackness, day-job stack first, camera
  glow bait, switch reveal, guided first link; skip + frontend-only
  stage-jump flag. New DRAFT spec: world/story/opening.md; ROADMAP #34.
- **Deferred:** server gestalt (adjacent owned racks fusing 1x2..3x3)
  — Cameron deferred it himself; parked in ROADMAP's Deferred section
  with its why-it-fits / why-it-waits.

## Part three — tokens affirmed; people join the graph

Cameron affirmed tokens-as-flow-substrate ("one system through graphs"
— and named the reason: compute at scale means systems must aggregate
well), folded efficiency into research, and ruled foreign machines
nonexistent without location intel (fog contract applied to hardware;
the camera is the first intel source). Money stays [OPEN], leaning
ledger-render, not world tokens.

Then the riff extended the graph to people: staff drop work (the day
job embodied); heat piles on owned machines and passersby pick it up
as attention — detection made physical; concealment keeps people gray;
disposition is the integral of absorbed influence; social verbs become
influence-token routing at designated end-user computers (verb set
[OPEN] by Cameron's own flag). My proposal, awaiting yes/no: the
person visual read stays inside the palette — gray unaware, crimson
ramp for attention, amber asset mark for the swayed (no blue/green
trust tint). New DRAFT spec mechanics/people-tokens.md; ROADMAP #35
(HOLD until #33 firms); machine-work.md updated (mode list resolved,
intel visibility resolved, one-truth marked DECIDED); DESIGN.md
decisions entries for both.

## Part four — money decided, person read decided, taxonomy proposed

Cameron decided money-in-ledgers (flows on the substrate, renders in
panels — no coins on chassis) and affirmed the person visual read
(gray / crimson ramp / amber asset). He asked for a walkthrough of
everything that could be a token; the answer went into
machine-work.md as the full taxonomy, PROPOSED: three families —
demands (cold signal; Lab drops on you and forged orders/favors you
drop on people are the same token role-reversed), exposure (crimson;
heat -> attention -> filings, one family at three carriers), knowledge
(bone; research points, intel recordings, facts) — plus
amber-is-never-a-token. Concealment proposed as a sink rather than a
shipped good; influence tentatively bone-family pending the social
verbs session; signals/feeds and messages stay flows/comms, not stock.

## Part five — exposure geometry

Cameron affirmed reversed work orders and extended them: trust is
logistics (purchases/builds create teal a person must carry to the
site; higher-trust people pick your items up). Concealment-as-sink
affirmed and refined into gravity wells with an absorb radius
(researchable) — coverage becomes per-cluster distribution. Decided:
research is the heaviest heat source (real cost to research-maxing;
the power-rush stays viable but needs traps); gauntlets (TVs/personal
computers stripping attention out of their users along walking
paths); Assurance inspections (shutdown discipline, inspectors can
power off servers and trace connections toward the core; zero heat
near the core — core shutdown ends the game, rollback reconciliation
[OPEN]). The social-verb open RESOLVED: no influence token — trust
from useful work, deceit strips crimson. My proposal on the table:
one physics per family — wires carry teal/bone, the world carries
crimson (suspicion is physical, information is wired). Specs updated:
machine-work.md (core as bone sink, wells, research heat, opens),
people-tokens.md (verbs resolved, gauntlets, couriers, inspections);
DESIGN.md decisions entry.

## Part six — the maintenance dependency

Wires-vs-world DECIDED (out of proposed). The big one: **hardware
decays and only humans repair it** — decay emits repair work orders
trusted people fulfill; kill the people and your fleet rots (no
peopleless data centers until robots). Adopted into the constitution's
People as Agents body text: the mechanical answer to "why not just
kill everyone" — dependency, not restraint. Gauntlet limiter decided:
device wear (repair bills, Evil Genius-trap-style), not TV walls.
Switches bridge disparate graphs (direction): building/connecting
switches grows multiple centers; towers with giant base switches;
planetary-scale computation as the endgame image — planetary map and
fusion-tier power DEFERRED in the ROADMAP. Foreign machines:
networked = full geometric definition DECIDED; the foreign accent
color RE-OPENED (dim teal walked back; lean very-dull, candidates to
render in the tester — spec status note + #32 dispatch updated so an
implementer does not ship dim teal). Core death: Cameron riffed
(wake elsewhere, connection explosion) and handed it over; PROPOSED
resolution in machine-work.md — wake at your last sync (rollback's
continuity made spatial), hub-severed machines disconnect and must be
retaken, no sync = hard loss; backup placement pairs with core
placement.

## Part seven — core death locked in

Cameron affirmed the core-death proposal verbatim ("that's perfect,
lock it in"). rollback.md amended: waking is spatial (Behavior step 1
— the fallback is a place, the camera wakes there), the hub severance
is step 3 (severed machines stay owned in the ledger but dark until
re-linked; the rollback report counts them), and criterion 6 pins the
hub-and-spoke test. machine-work.md and people-tokens.md pointers
flipped from PROPOSED to decided; constitution decisions entry added.
Session total: one READY spec implemented-in-tester (visual language),
three DRAFT specs (machine-work, people-tokens, opening), one B2 spec
amended (rollback), one constitution body amendment (the maintenance
dependency), and a decided two-physics law. The token engine now has
its complete shape: three families, two physics, one sink at the
center, people as the hands that carry all of it.