# Palace Provisioning

When a master signs up, a palace is created for them. This is provisioning.

## What Happens

1. Master submits mastername, password, palace name, butler name
2. A row is inserted into `masters` and `palaces` in Postgres
3. `palaces/modelpalace/` is copied to `palaces/<palace-name>/` on the server
4. The butler is ready — the master lands in their palace

## The Model Palace

`palaces/modelpalace/` is the canonical template. It contains the full directory scaffold every palace needs — app data folders, secretariat memory structure, notebook — all empty. When provisioning, copy it wholesale. The butler populates identity on first conversation.

Any new app added to the platform must add its data directory to modelpalace so new palaces get it automatically.

## The Server

**palacestableserver** (5.78.153.101) is the beta server. All early palaces are hosted here. It runs Postgres for auth and the palace filesystems for data. Domain: `stable.palacering.com`.

When Palace Ring grows beyond beta, provisioning will move to a scalable deployment system. For now, manual provisioning on palacestableserver is correct.