Learning Atlas / Working notes

Making complex systems legible.

A holding room for fields I am trying to understand deeply — not as trivia, but as operating systems of power, capital, physics, software, and taste.

ModeVisual first
PaceSlow maps
OutputField guides

Concept rooms

Each card opens a domain — a distilled ethos, a mental model, and a visual companion designed to make the terrain easier to revisit. Two rooms are open; more are queued.

Outputs

Where the working notes turn into deliverables. Each output is a self-contained case study — the work itself plus the way it was made.

How I’m learning

The goal is not to collect links. It is to build enough internal structure that new information has somewhere useful to land.

Step I

Map the stack

Start with the layers, dependencies, bottlenecks, and feedback loops. A domain becomes clearer when it has a visible skeleton.

Step II

Name the tensions

Every interesting system has constraints: cost, power, time, regulation, taste, trust, or physics. The constraints reveal the strategy.

Step III

Return visually

Convert notes into diagrams and cards so the knowledge is not just stored, but navigable — something you can re-enter quickly.