One-Way Publishing

One place is authoritative (the vault); everything else — Google Tasks, Projects, a mobile subset, PDF exports — is a one-directional, never-back view generated from it. The vault always wins; downstream targets are disposable and regenerable. Bidirectional sync is the most common way a personal system decays; one-way publishing makes drift structurally impossible.

The word doing the work is structurally. Plenty of people intend to keep one source authoritative — and then edit the copy once, because it was open, because it was faster. Intent doesn't survive convenience. What survives is an arrangement where the wrong thing is impossible rather than merely discouraged: if nothing downstream can write back, there is nothing to reconcile.

Sync sounds like the more generous design, and that's the trap. Two-way means two places can both be right, which means eventually they disagree, which means a merge — and merges of knowledge have no clean resolution. Which version of a note is correct? The system can't know, and by the time you notice, neither can you.

The freeing consequence is that downstream becomes disposable. A published surface holds nothing you'd mourn: delete it, regenerate it, and it's identical. That's what lets you publish generously — to a phone, a share link, a Notion page, a client — without adding a single thing you now have to keep in sync.