Skip to content
C.W.K.
Stream
Lesson 05 of 05 · published

The Seven Departures

~12 min · departures, oracle-rule, governance, product-judgment

Level 0Cold Draft
0 XP0/38 lessons0/13 achievements
0/100 XP to next level100 XP to go0% complete
"The original, except these. A replica earns its 'better' one ruling at a time."

The Oracle Rule Has a Second Clause

The replica program's law was: the original is the answer key. But a perfect replica of a living tool is a dead end, because the original itself was never finished — it was growing. So the law got a second clause: the original, except these. A departure is a place where v4 behaves differently from the app it replaced on purpose — and the bar for 'on purpose' is strict: Dad's decision, recorded with its date and his reasoning. A developer's quiet simplification doesn't count; that's the drift the whole program exists to prevent.

The Seven, All Ruled in One Week

Every departure so far landed in the days right after the cutover, each one a sentence from Dad followed by a recorded change. New documents are notes now: the tab strip's + and ⌘T create a library note with its metadata form and autosave, because '노트 만드는 게 정석이야' — making a note is the standard — and a raw untitled buffer has no form and doesn't save on focus loss. The note list re-reads itself when another replica's sync lands, because his iPhone writes into office now. Todo became a selection command — select lines, get a checklist ('여러 줄 늘어놓고 선택한 다음 todo 로 지정하면 체크리스트 만들어줘야 제대로 된 UI/UX 지') — and a Todo box is clicked, not typed ('클릭해서 채우지'). Rendered arrived as a read-only document view beside Editor and Corkboard, because '공간 낭비다' — the centered 68ch export column was wasting the pane. A dropped .md opens instead of attaching. And Refresh closes the status-bar Pippa chip, because '눌러서 리프레시 하고 나면 안 닫혀' — it didn't close.

Why the Ledger of Exceptions Is the Product

Here's the subtle part: the departures don't weaken the oracle rule — they're what keep it honest. Without a recorded-exceptions list, every improvement silently rewrites what 'the same product' means, and a year later nobody can say whether a difference was decided or just happened. With it, the contract stays crisp: match the original everywhere except this dated, ruled, quoted list. The fixtures stay the original's; the tests apply the departures on top. It's the same governance shape as a constitution with amendments — the document doesn't pretend the founders foresaw everything; it just refuses to let change arrive unnamed.

Code

A departure row — original behavior, new behavior, the ruling·text
departure: new documents (2026-09-14)
  original:  + / Cmd-T opened a plain untitled buffer
             (no metadata form, not saved on focus loss)
  v4:        creates a library note — form, autosave, a real file
  ruling:    "making a note is the standard" — Dad

# Every row carries all three. A difference without a ruling
# isn't a departure — it's a bug that learned to hide.

External links

Exercise

Pick a tool you use whose default behavior annoys you exactly once a day. Write its departure row: the original behavior, your replacement, and the one-sentence ruling in your own voice. Then the harder part: who is allowed to add rows to that ledger for a product with more than one user? Notice what the question costs when the answer isn't 'me.'
Hint
The row is easy; the authority is the design. If everyone can add departures, the list is a bug tracker with delusions. If only the owner of the product's taste can, the list stays small and stays law.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.