# Setup packet

Report: chosen project/global mode; canonical repository and worktree mapping; record root; workspace UUID/code; writer and discovered tools; private-profile opt-in; excluded/never-copy sources; capabilities with verification level; unresolved owner steps.

When a user asks for guidance, also summarize their chosen explanation depth, optional custom answers, local-only/cloud choice, verified Git/remote status and selected librarian if any. Mark unset choices unknown. Show what personal information would be stored and its scope before creating a proposed memory. A fully local first-run UI is a product goal until independently verified on the installed version.

Verify by creating a labelled DOC, reading it back and checking its authoritative file. Keep the allocated ref/revision; do not use this document's examples as actual IDs.

File-only initialization request (pass to the bundled writer's init command):

```json
{"name":"Example project","code":"EX","repository":"<absolute-repository-directory>","mode":"project","mainBranch":"main"}
```

Example outcome: “Project-local records initialized and ignored; two worktrees resolve to the same repository. A welcome DOC was created/read. Provider discovery unavailable; model choice and real execution remain unconfigured.”

For companion adoption, stop the standalone writer, preserve a backup, select the same root/registry and rebuild with the companion. Compare UUIDs, links, history and next counters before trusting the import. Do not configure cloud sync merely because local adoption succeeds.