World Blueprint

A WorldBlueprint is the provisioning recipe that turns a plan purchase plus a short signup form into a fully-shaped new World. Every World is provisioned from exactly one Blueprint.

The Blueprint says: which pwpacks to install, which starter Surfaces to materialise, which capabilities to pre-enable, and which entitlements the plan starts with. After provisioning the live World is independent — the Blueprint is a recipe, not a runtime parent.

Blueprint vs World

	Blueprint	World
Role	Provisioning recipe	Live, per-customer aggregate
Mutability	Template; new versions ship through the marketplace	Mutable — accepts Receipts, captures state
Cardinality	Many Worlds can share the same Blueprint	One World per customer (Enterprise: multiple)
Lifecycle	Authored, published, versioned	Created from a Blueprint, lives until cancellation

Anatomy

A Blueprint declares:

Identity scaffold — World name template, slug rules, default locale.
Plan binding — which billing plan(s) this Blueprint is valid for.
Pack bundle — pwpacks to install at provisioning (@pwpack/phiwebs/ui, @pwpack/phiwebs/data, …).
Starter Surfaces — Surfaces to materialise on day-one (typically a homepage, an intranet landing, a dashboard).
Default capabilities — capability configs pre-installed (e.g. platform/persistence with default data sources).
Default entities — entity definitions for the World’s data model.
Default settings — settings-registry values that override the platform default for this Blueprint.
AI charter — the persona prompt PhiCo and PhiSo inherit unless the customer overrides.

Built-in Blueprints

PhiWebs ships a small set of first-party Blueprints — one per launch vertical. Use one as a starting point or fork it through the marketplace.

Blueprint	Pack bundle	Starters
`landing-page`	core-ui + persistence	landing-page
`intranet`	core-ui + persistence + entities + interaction	intranet, employee-directory
`portfolio`	core-ui	portfolio
`sports-club`	core-ui + entities + interaction	sports-club, fixtures-board
`dashboard`	core-ui + data	dashboard

The canonical list is shipped by the first-party packs and surfaced in the marketplace.

Authoring a Blueprint

First-party Blueprints ship inside the pwpacks PhiWebs publishes — they are authored against the canonical Zod schema in @pwfabric/contracts/fabric/world-blueprint.ts and managed through the operator API. A public CLI for Blueprint authoring is planned alongside the broader marketplace authoring tools.

If you need a custom Blueprint for an Enterprise plan today, contact sales — Blueprints are provisioned for your World by PhiWebs staff.

Provisioning flow

account.phiwebs.com/signup
       │
       ▼  plan selected, blueprint chosen
   /api/blueprints/:id/provision
       │
       ▼
   Worlds.create(blueprint, customer)
       │
       ├── install pack bundle  → register atom set
       ├── materialise starters → first Surfaces + revisions
       ├── seed entities        → initial entity model
       ├── apply settings       → settings overrides
       └── mint entitlements    → capability entitlements
       │
       ▼
   World ready — first PhiCo session opens

The whole flow runs inside a single transaction. If any step fails the World is rolled back and the customer is returned to the plan picker.

API

Method	Endpoint	Purpose
`GET`	`/api/blueprints`	List blueprints available to the customer.
`GET`	`/api/blueprints/:id`	Read a specific Blueprint.
`POST`	`/api/blueprints/:id/provision`	Provision a new World from this Blueprint.