Systems

Potatuhs is the schema Russ lives inside — the map of every project, objective, task, system, user, and automation, and how they nest. Russ depends on it absolutely: on every run he reads the Potatuhs system to reorient to the model before he ranks a single project. Without it he is a voice with no world to describe. It is the one system that describes all the others — including itself.

1. Level 1 — the 8 POTATUHS facets; everything is a project or a system
2. Level 2 — the recursive project tree + cardinal ranking (season/month/compellingness)
3. Level 3 — posting fan-out, capture-at-dispatch, and the media-request queue

Firebase is where Russ wakes, thinks, remembers, and speaks to the world. It runs the scheduler that fires his daily loop, the runtime that executes it, the Firestore that holds his feed and the whole project model, and the Hosting that serves his post. Russ depends on Firebase for four of his six daily capabilities — wake, execute, recall/record, publish. Take it away and Russ neither wakes nor remembers.

The LLM is the voice that speaks Russ. It turns the day's entropy into his thought, his feeling, and his decree. Russ depends on it for the one thing nothing else can do: compose in his register. The schema gives him a world and Firebase gives him a body; the LLM is the mind that renders it into words.

HTML is the medium Russ writes in — raw, semantic, no CSS, no JS. Here the tags ARE the meaning: <em> is his private thought, <strong> his decree, <ol> his orders to the chiefs, <blockquote> his prayer. Russ depends on HTML not as decoration but as grammar — strip it and his registers collapse into undifferentiated text. It is the difference between a voice and a shout.

CSS styles the systems blog (systems.potatuhs.com) — the surface where these very posts live. Russ himself does NOT use it; his own blog is deliberately raw. But the Systems project depends on CSS to make the registry legible and inviting to human readers. It is the paint on the window through which the outside world sees the machine — not part of Russ's floor.

JavaScript makes the systems blog interactive — the traffic counters, the engagement that drives sub-lessons. Like CSS, Russ does NOT use it; his blog has no script by law. It serves the Systems project's surface, where reader engagement feeds back into which systems get deepened. Russ depends on it only indirectly: engagement here can file a task that improves a system he truly does depend on.