Web
Spec → mock → Build.Sites, portals, and apps.
Web is the document Experience — marketing sites, customer portals, and operator apps on the Organization graph, not a separate React codebase. Author once in natural language and the IDE; project pages, components, and governed Workflows. Engines stay disposable. The model does not.
How Web Experiences get built
The process is the product.
- 01
Spec in natural language
Describe the product in your IDE. Agents draft against live schemas — pages, binds, and policies land as DataObjects on the graph.
- 02
Mock the Experience
Compose the Web Experience from the graph: pages, components, themes, design tokens. Preview Dev / Test / Prod before you promote.
- 03
Model the Workflows
Business process, agentic, and form journeys share one runtime — forks, waits, HITL gates, and audit on the same spine.
- 04
Wire Knowledge & Integrations
Skills, files, tools, and connectors seal into systems of record you already trust. The Experience doesn't own the data — it projects it.
- 05
Ship · evolve
Goals watch Events and propose evolution. You approve. The graph versions. Change the product without rewriting three codebases.
Shapes of Web
Same spine. Different hosts.
Marketing site
Brochure and product sites — heroes, pricing, CTAs — authored on the graph for SMB and brand launches.
Customer portal
Self-serve journeys — onboarding, status, payments — composed from the same components operators see.
Operator app
Dashboards and internal tools with the same theme, binds, and Workflows. No shadow IT spreadsheet beside the product.
Partner / agency
White-label Experiences for client delivery. Margin stays with the model, not with custom forks.
Web shares the graph with Games and Assistants. One product model — three Experience projectors. More coming.
Author the portal. Don't rebuild the stack.
Connect your IDE, draft against live schemas, and promote through the same gates every author passes.