Structure Beats Magic
← All concepts
System architecture

Connect & Dispatch

Capture anywhere, dispatch to where the power is, commit back to the one vault.

Connect & Dispatch
Devices are doors, not homes. Capture on whatever's in your hand, dispatch the work to wherever the power actually is — AI to reason, a database to scale, code to execute — and commit the result back to the one versioned vault. The loop at the bottom is the point: everything returns to the single thing that's yours.

Capture anywhere, dispatch the work to where the power is, and commit back to the one vault — the devices are doors; the versioned markdown is what's yours.

The trap is treating devices as places. Once a phone is somewhere your notes live, you have as many partial truths as you have gadgets, and you're back to reconciling. The fix is a demotion: a device is a door, not a location.

So the loop is: capture wherever you happen to be (a phone is a fine door), dispatch the actual work to wherever the power is (a real machine, a real model, real tools), and commit the result back to the one place that's authoritative.

What's yours in that loop is never the app — it's the versioned markdown at the end of it. Doors change every few years; the thing behind them shouldn't have to.

Related concepts