World-Physics model
The foundational architecture that defines how PhiWebs and PWFabric relate — and why it matters for what you build.
The core insight
Most digital platforms are products built on infrastructure. PhiWebs is different.
PhiWebs is not a product that uses PWFabric. PhiWebs is the world where PWFabric’s physics apply.
Just as our physical world has physics that enable everything within it, PWFabric is the physics that enables everything within PhiWebs.
The model
+------------------------------------------------------------------+
| PHIWEBS (World) |
| "Where living digital surfaces exist, evolve, and connect" |
| |
| +------------------------------------------------------------+ |
| | PWFABRIC (Physics) | |
| | "The surface operating system that makes PhiWebs possible"| |
| | [Runtime] [Contracts] [SDK] [APIs] | |
| +------------------------------------------------------------+ |
| |
| [Surfaces] [Blocks] [Users] [Organizations] [Marketplace] |
+------------------------------------------------------------------+
| owned by
v
PHIMAJOR (Company)Three entities
PhiMajor — Corporation
The company behind the ecosystem.
- Audience: Investors, legal, press
- Use context: Legal contracts, investor communications, press releases
PhiWebs — World / Ecosystem
Where living digital surfaces exist, evolve, and connect.
- Audience: End users, organizations, surface creators
- Use context: Product marketing, user documentation, surface creation
PWFabric — Physics / Operating system
The surface operating system that makes PhiWebs possible.
- Audience: Developers, technical integrators, white-label partners
- Use context: API documentation, SDK reference, architecture guides
Why this matters
- For developers — PWFabric is a complete OS, not just an SDK. You’re building on layers of infrastructure — identity, state, capabilities, runtime — not just rendering components.
- For architects — The World-Physics model means clear separation of concerns. PhiWebs World concepts (User, Organization, Entity) are distinct from PWFabric physics (Contract, Capability, Surface).
- For integrators — White-label deployment means using PWFabric physics without PhiWebs World. Your platform, your brand, same operating system underneath.
Layer separation
The World-Physics model creates a clean separation between concepts:
| Physics layer (PWFabric) | World layer (PhiWebs) |
|---|---|
| Contract | Entity |
| Capability | Behavior |
| Surface (primitive) | Living Surface (entity) |
| Domain | Organization |
| Fabric | User |
Physics defines how things work (mechanics). World defines what things mean (semantics).
Package architecture
This separation is reflected in the package structure:
@pwfabric/* (Physics)
@pwfabric/contracts— Type-safe interfaces@pwfabric/core— Core utilities@pwfabric/runtime— Execution engine@pwfabric/sdk— Developer SDK
@pwfabric/world (World subpaths)
The World aggregate ships as @pwfabric/world with subpath exports:
@pwfabric/world/entity— entity model and CRUD@pwfabric/world/behavior— event-driven rules@pwfabric/world/intelligence— PhiCo + PhiSo, AI surface generation@pwfabric/world/connectivity— connectors, webhooks@pwfabric/world/economy— Φ ledger, plan and entitlements@pwfabric/world/context— request-scoped runtime context@pwfabric/world/surface— Surface lifecycle inside the World
Dependency rule:
@pwfabric/worldmay depend on the rest of@pwfabric/*, never the reverse.
Deployment
PWFabric is a hosted product — Worlds live on PhiWebs infrastructure (Cloudflare edge + Azure origin per ADR-149). Self-hosting and white-label standalone deployments are not currently supported.
Enterprise plans negotiate dedicated VPC, KVKK + GDPR DPA terms, and optional private connectivity (Azure ExpressRoute, AWS PrivateLink) but the runtime itself remains hosted by PhiWebs.
Correct language
| Correct | Incorrect |
|---|---|
| ”PWFabric powers PhiWebs" | "PhiWebs runs on PWFabric" |
| "PWFabric is the physics of PhiWebs" | "PhiWebs is a PWFabric app" |
| "PhiWebs is built with PWFabric" | "PWFabric backend" |
| "PhiWebs is where surfaces live" | "PhiWebs platform” (as product) |