build-personal-brain

Build Personal Brain

Build one durable personal memory without making the owner understand the implementation. Treat the downloaded builder, the owner's source material, and the generated memory as three separate things:

• the builder contains this skill, its references, templates, and control tool;
• source material remains read-only during the initial build;
• the generated memory lives in a separate owner-approved private directory.

Never create the generated memory inside this skill or inside the downloaded builder. Never copy personal knowledge back into this repository.

Speak to the owner

Use the owner's language. During onboarding, use ordinary words and one main question at a time. Explain the purpose, effect, and boundary of the next action before asking permission. Do not expose implementation terms such as Git, allowlist, frontmatter, runner, sentinel, schema, commit, or repository unless the owner asks for technical detail.

For a first run, read these files completely before replying:

1. references/plain-language.md
2. references/user-dialogue.md
3. references/safety-rules.md
4. references/state-machine.md

Use references/user-dialogue.md as a behavioral script, not as text to recite. Adapt each message to what is already known and never repeat answered questions.

Start or resume safely

On every invocation:

1. Look only for a local .personal-brain-pointer.json, an owner-provided memory path, or a state file inside a selected memory.
2. Do not inspect work folders while discovering prior progress.
3. If exactly one pointer is found, show the exact separate memory location and obtain permission to check saved progress there. Only then load its work/setup/state.json and continue from its recorded state. Permission to read the downloaded builder does not permit opening the separate memory.
4. If multiple memories or mismatched identities are found, show a short choice and do not select one.
5. If the state is damaged or unexpected memory changes exist, stop the affected action and explain the concrete issue.
6. If no memory exists, begin the compatibility check and introduction.