The Method.
Documentation is not what's left after the work. It's the surface the work runs on.
Both systems in this portfolio share one operating model: every project carries its own instructions, its own living state, and a vocabulary of verbs that both a person and an AI can execute. This page opens the hood. Real structure, real excerpts, the folder logic itself.
A system is only real when it works without its author in the room.
The workspace is self-describing.
Every project in the ecosystem is a citizen with the same three control files at its root. Open a folder, click any file, and read what a new collaborator (human or machine) would read on day one. These are lightly condensed excerpts of the real thing.
Verbs that execute.
The ecosystem speaks in compound verbs. Saying one triggers a documented multi-step workflow, not a vague intention. Humans use them to communicate intent; agents use them to self-check that every step ran. Precision of language is precision of operation.
Move a brand handoff downstream: diff the primitives, copy to each framework, open a pending review in every affected living state, log the trail.
Move requests upstream: sweep every framework's log for open questions to the brand source, transcribe them to its inbox, mark the originals as routed.
Close a token group against further additions, once all usage rules validate. Locked means buildable.
Graduate a component from draft to canonical: QA pass, overwrite source, delete draft, stamp the changelog. Nothing ships from a draft folder.
Raise a need the current project can't solve: note it inline, log it with a routing tag, send it through the orchestrator. Never patch upstream gaps locally.
Record a decision with its why, dated, in the project's decision log. A decision that isn't logged doesn't exist.
Trust is checked, not assumed.
Between every two layers of the system there is a gate. Nothing propagates on good intentions.
Thirty checks before brand primitives may propagate: files present, schema valid, values in parity, accessibility floors honored, rationale complete. Pass or go back.
Scripted validations from dangling aliases to scope leaks, each one born from a real incident that is now impossible to repeat.
Draft, visualizer, QA, promotion. A component earns each phase; the last one requires human eyes and a logged approval.
Exactly one, per ecosystem. Everything else is a projection that can be regenerated, audited, and swept.
The method, compiled into a tool.
Folder logic, gates and verbs govern the repo. This is what enforces them inside the design tool: an eight-tool Figma plugin, born inside Atlas and general by design, that keeps any token-governed file an exact mirror of its source. The launcher is washed pop-art: every tile rests desaturated and reveals its pure neon on hover. This is a faithful, working simulation of the real panel. Tap a tile, run the tool.
Atlas Toolkit
Design system · internal Figma pluginEvery tool is one of the gates, compiled: Sync is the one-way flow, Checkup is the parity gate, Sweep is the no-silent-drift rule. The plugin doesn't add policy; it enforces the policy the repo already wrote down.
The two ways to publish the system into Figma, Sync Tokens and Sync Components, anchor opposite corners in cyan and magenta. The supporting tools sit between them; the two full-width bands are for exploration.
Every tile's fill is the same desaturation of its signature hue. One mix ratio is the single dial for the launcher's entire vibrancy. The pure neon appears on hover, and the header keeps the one always-pure hue.
Results read as sentences with number chips, technical detail folds away, and nothing destructive runs without a preview and an explicit confirm. Designers keep agency; the system keeps truth.
The real plugin runs offline: the repo's knowledge is embedded at build time, so the file can never disagree with the source. It runs in production on Atlas today.
Built for the day the author isn't alone.
This method exists because AI collapsed the cost of producing and raised the cost of judging. Instructions, living state and executable verbs are how judgment gets transferred: to the next designer, to the dev team the contract already anticipates, to the agents that read the same files people do.
Meridian runs on it. Atlas runs on it. This portfolio runs on it too: brain file, living state, decision log, brandbook and tokens, all versioned in the same folder logic you just clicked through. The craft isn't only in the pixels. It's in the fact that everything here can explain itself.