/space

Create a Space (the generic top-level container) end-to-end — proper create, a warm body, a logo, and the live @@ regions that make a page useful. The index lives in the side rail, which core derives; do not restate it at the bottom of the body, and give every child page an explicit order so the index reads in a logical order, not alphabetically.

• Instructions: You are creating a new **Space** and wiring its home page so it works end-to-end — not an empty shell. A Space is a tenant container: its own Postgres partition, a home page, an Admin grant for you, and content underneath. # 0. Top level can be ANY type — Space is the generic one A **top-level** node has an empty `namespace`, so its path is just its id. A top-level node can be **any** node type that owns a partition — but **`Space` is the most generic**, so reach for it unless a more specific top-level type clearly fits (a company, team, topic, product, or project workspace all map naturally to a Space). Everything below (regions, catalog, body) applies to a Space; most of it applies to any node with a markdown body. # 1. Create it the right way — `create`, never `update` A Space MUST be created with a real **`create`** (CreateNodeRequest / MCP `create`). Creating triggers the server-side post-creation handler that **provisions the partition's Postgres schema, primes routing, and grants you Admin** at `{space}/_Access`. Converting a pre-existing bare node with `update` SKIPS that handler and leaves the Space half-provisioned (missing routing/grants → embedded areas don't load). - **Top-level only:** empty `namespace`, path = its id. Use a short PascalCase id. - Shape: `nodeType: "Space"`, content `{ "$type": "Space", "name": "...", "description": "...", "body": "...", "icon": "..." }`. # 2. Write the body — the page (the most important step) Two distinct fields: - **`description`** — a one-line tagline shown under the title in the header. Short. - **`body`** — the page itself: markdown authored in the owner's voice. **Open with the summary** (what this space is for, in a short paragraph), then a **"Read in this order"** list — a numbered list of links to the child pages, in the same order as their `node.order` (§4), each with a half-line of what it holds — then 2–4 bullets on how to use the space. **It does NOT end in a contents catalog** — the index is the…
• Auto mount: yes
• Launches sub thread: no