DSL Reference¶
Auto-generated by
docs_gen.py. Rundazzle docs generateto regenerate.
| Section | Description |
|---|---|
| Entities | Entities are the core data models in DAZZLE. |
| Access Control | DAZZLE uses Cedar-style access rules with three layers: entity-level permit/forbid blocks, surface-level access restrictions, and workspace-level persona allow/deny lists. |
| Surfaces | Surfaces define the UI and API interfaces for interacting with entities. |
| Workspaces | Workspaces compose multiple data views into cohesive dashboards or information hubs. |
| UX Semantic Layer | The UX semantic layer expresses WHY interfaces exist and WHAT matters to users, without prescribing HOW to implement it. |
| Experiences | Experiences define multi-step user flows such as onboarding wizards, checkout processes, and approval workflows. |
| Services | Services declare custom business logic in DSL with implementation in Python or TypeScript stubs. |
| Integrations | Integrations connect DAZZLE apps to external systems via declarative API bindings with triggers, field mappings, and error handling. |
| Processes | Processes orchestrate durable, multi-step workflows across entities and services. |
| Stories | Stories capture expected user-visible outcomes in a structured format tied to personas and entities. |
| Rhythms | Rhythms capture longitudinal persona journeys through the app, organized into temporal phases containing scenes — evaluable actions on specific surfaces. |
| Ledgers & Transactions | Ledgers and transactions provide TigerBeetle-backed double-entry accounting. |
| LLM Models & Intents | DAZZLE supports declarative LLM job definitions for AI-powered tasks such as classification, extraction, and generation. |
| Testing | DAZZLE provides a comprehensive testing toolkit including E2E testing with Playwright, FlowSpec test generation, semantic DOM conventions, capability discovery, CRUD completeness analysis, workflow coherence checks, and RBAC validation. |
| Frontend & Templates | The Dazzle frontend uses server-rendered Jinja2 templates with HTMX for declarative HTTP interactions. |
| Messaging & Events | Messaging and events enable asynchronous communication between components and users. |
| Graphs | Define entity relationships as graph edges, query neighborhoods via CTE, and run graph algorithms (PageRank, community detection, shortest paths). |
| Compliance | Automated compliance evidence extraction from DSL constructs. Supports ISO 27001 and SOC 2 Trust Services Criteria. |
| Governance | Governance constructs enforce organisational policies, approval workflows, and service-level agreements. |
| Patterns | Patterns are reusable DSL recipes that combine multiple constructs into proven solutions. |