Island Reclamation (Adding a Personality Island)

An Island is one of the personality islands in the user's head — Hockey Island, in the film. It stays above water only as long as memories keep coming to visit it: a domain of responsibility or interest that has to be maintained, not a task that ends when it is finished. Name it too narrowly and you will rename it the day the tools change, breaking every link; name it too broadly and it becomes a junk drawer; mistake a Project for an Island and it can never be closed. And a standing island still has to be lived in — when nobody visits, it cracks apart and slides into the sea, exactly as in the film. In this vault that collapse has a name: memorb-forgetter sweeping the pages into memorbs/Dump/. Hence the iron rule of this workflow: stages 1-3 are conversation only. Create no file and no folder until the user has confirmed.

Order of operations

Stage 1: Agree on what the Island is (talk only)

An Island is a domain of responsibility or interest whose standard must be maintained indefinitely — not a product, not a tool, not a goal with a finish line. Converge with the user on three questions:

1. Island or Project? If it has a definable finished state (pass the certification, ship the system) it is a Project: open it under memorbs/Long-Term/Projects/ and link it back to the relevant Island. Only something maintained without end — health, finances, a standing responsibility, a lasting interest — is an Island.
2. What level to name it at. Too narrow (a specific instrument, tool, or platform: 台指期, Notion) and the name expires the moment the tool does. Too broad (人生, 理財) and everything ends up inside it. Find the middle by asking: "will this name still hold in five years?" and "what standard am I actually maintaining here?"
   • Worked example: the user wants to trade TAIEX futures. The Island lands on 主動交易與投資 — the craft transfers, the instrument is only today's choice, and passive investing is deliberately left out.
3. How it relates to existing Islands. Run ls "$VAULT/memorbs/Islands" first and check for overlap. If a domain already covers it, extend that Island rather than opening a new one.

Stage 2: Decide the structure (talk only)

Lay out the options and give a recommendation. Judge on expected note volume, whether the domain will spawn projects, and how much structure the user likes.