Dream Consistency Platform Operations
Internal operational tools used to prepare database contracts, install shared system catalogs,
initialize a new Realm, and support repeatable Dream Consistency environment provisioning.
Platform tools are versioned executable utilities used during environment creation,
controlled schema and catalog maintenance, and one-time platform initialization.
They are not application runtime services and must not be started automatically by product APIs.
Operational rule:
Execute each tool only for its documented responsibility and in the documented order.
Database schema deployment, system catalog installation, Realm bootstrap, and product provisioning
are separate operations.
System Catalog Installer
Validates and installs versioned Realm, Management, and Billing shared system catalog packages
into compatible physical databases.
Open Installer Guide →
Realm Bootstrap
Verifies Realm.Foundation, creates the authoritative self Realm,
and creates the first Core operator account.
Open Bootstrap Guide →
1. Deploy Realm, Management, and Billing database schemas
2. Record the deployed SchemaVersion and ContractVersion in each INF_*SchemaVersions table
3. Install DreamConsistency.Realm.Foundation
4. Run DreamConsistency.RealmBootstrap.Cnsl
5. Install the remaining Realm system catalog packages
6. Install all Management system catalog packages
7. Install all Billing system catalog packages
8. Register applications, services, and other runtime data
9. Validate and activate the self Realm
10. Continue with product-specific package and tenant provisioning
Critical dependency:
Realm bootstrap requires the Realm.Foundation catalogs, while the remaining shared catalogs
are installed after the self Realm and first Core operator have been created.
| Operation |
Responsible Component |
| Create or update physical database schema |
Workbench model, DatabaseDiff SQL, and controlled manual execution |
| Record deployed schema and contract version |
Final statement in the generated and reviewed schema update SQL |
| Install shared Realm, Management, and Billing catalogs |
DreamConsistency.SystemCatalogInstaller.Cnsl |
| Create the authoritative self Realm |
DreamConsistency.RealmBootstrap.Cnsl |
| Create the first Core operator |
DreamConsistency.RealmBootstrap.Cnsl |
| Register product-specific packages, imports, metrics, applications, and services |
Product Management and provisioning workflows |
During active Hestino development, these tools are executed locally from Visual Studio or
a Developer PowerShell terminal against the DEV databases. This keeps infrequent provisioning
work from blocking product development.
Catalog NuGet packages continue to be built and published through Jenkins.
A controlled Jenkins execution workflow for QA and Production can be introduced later,
together with database-local system catalog installation history and formal approvals.
Current decision:
Local execution is the approved DEV path. Jenkins is used for immutable NuGet package releases,
not for every catalog installation command.
- Connection strings and passwords must not be committed to source control.
- Local secrets belong in
appsettings.Local.json, environment variables, or user secrets.
- Connection strings must never be supplied as command-line arguments.
- The expected database name must always be supplied and verified before a write operation.
- Operator passwords must not be logged, echoed, or included in execution artifacts.
dream-consistency
platform-tools
platform-operations
environment-provisioning
system-catalogs
realm
deployment
dotnet
| Date |
Change |
Author |
| 2026-08-03 |
Created the Platform Tools and Operations documentation index. |
Branko |