App Bundle Declaratives¶
App bundle declaratives are the files under an app workspace's active app root that describe an app without requiring changes to framework runtime code.
Purpose¶
Declarative files should describe durable app intent:
- what pages exist
- what workflows exist
- what module actions or backend actions are callable
- what events are emitted or handled
- what shell, theme, and admin defaults apply
Runtime code can then load and validate those files instead of relying on hardcoded app-specific branches.
Canonical Families¶
app/config/¶
Runtime-facing app configuration, including AI provider settings, shell config, admin config, and theme config.
app/ui/pages/¶
Schema-driven app pages rendered by the app UI surface.
app/workflows/¶
Declarative workflow definitions for agentic execution. A workflow owns its orchestrator config, agents, handoffs, tools, structured outputs, context variables, hooks, and optional UI artifacts.
Builder workflows may also exist in the shared generation core, but those are not app-owned bundle content.
app/modules/¶
Deterministic CRUD or action surfaces that support workflows and app pages. Modules are not AI workflows.
app/brand/¶
Brand assets, fonts, and theme inputs used by the shell.
Rules¶
- Keep one source of truth for each contract.
- Prefer explicit validation over runtime fallback branches.
- Do not encode app-specific behavior in core runtime modules.
- Do not treat app bundle files as compatibility shims for removed contracts.