App Architecture¶
App architecture docs define the generated app workspace contract: what lives in an app workspace, how app pages/modules/config/backend/brand and root workflows fit together, and how app-owned surfaces extend the platform.
Read these docs when changing app workspace structure, page/admin authoring, app manifests, app lifecycle, or app-owned service surfaces.
| Doc | Scope |
|---|---|
| Generated App Lifecycle | App lifecycle states and promotion model |
| Generated App Functional Acceptance | Deterministic checks that generated routes, actions, workflows, facades, and runtime load are coherent |
| Canonical App Structure | App workspace shape for config, backend, modules, pages, root workflows, and brand |
| App Manifest and Platform Targets | App manifest fields and platform target semantics |
| App Bundle Declaratives | Declarative app artifact families |
| Platform Authoring | Rules for app, page, admin, and platform authoring |
| Surface Model | Page, workflow, and module surface ownership |
| UI Surface and Layout Architecture | Shell, pages, workflow UI, and layout boundaries |
| App Dashboard Contract | Canonical Workspace/App Dashboard manifest, portal lanes, panels, and workflow-launch boundaries |
| Admin System | Admin surface ownership and contract |
| Platform Navigation Contract | Canonical ownership for Profile, Admin Portal, Studio, App Shell, Create, and resume |
| Account, Admin, and Platform Services | Account/admin/platform service boundaries |
| User Classes and Resource Relationships | Host-agnostic generated-app pattern for durable user classes, memberships, route authorization summaries, policy hooks, and resource relationships |
| Usage and Token Display | How AI token usage and wallet balance are surfaced to end users, app operators, and platform creators — and where the OSS/hosted boundary sits |