Use this page to connect the genesis design pages to the first installation workflow. Genesis defines the first governed state of the platform; the deployment guide explains when to submit that state during installation.
| Step | Use this page | Result |
|---|---|---|
| Configure the genesis block | Genesis payload reference | A complete payload for the one-time Genesis API operation. |
| Bootstrap the initial domain model | Design your domains | Root domain, launch subdomains, governing strategy, and read access. |
| Create the first users | Plan your first users | Users and roles that can satisfy day-one policy workflows. |
| Bootstrap the initial policy model | Design your policies | Policies for administration, transactions, compliance, fallback, and recovery. |
| Run Genesis during installation | Installation and initialization | System state initialized and notary public keys returned. |
| Register the first vault | Register a vault in the UI or Register a vault with the API | Vault entity created after Genesis so accounts can be created. |
| Smoke test the deployment | Verify full installation | A test account confirms the core, notary, vault, indexer, and governance workflow. |
Keep infrastructure configuration in the deployment guide and Helm values. Keep governance state in the genesis payload.
The Genesis API operation creates the initial root domain, initial users, launch policies, and other state that must exist before normal governed changes can happen. After Genesis, use intents and approvals for changes to domains, users, policies, vaults, accounts, and transactions.