Architecture
Radish is a layered platform. Different parts of the system operate at different levels of abstraction.
Layered Model
Intent Layer
↓
Blueprint Layer
↓
Architecture Generation Layer
↓
Application Layer
↓
Infrastructure / Operations Layer
Intent Layer
The process begins with an application idea or business need.
Examples:
- "A workflow tool for approving invoices"
- "An application for managing shipping statuses and approval timelines"
- "A blueprint library for storing prompt-to-architecture examples"
Blueprint Layer
The blueprint is the formal representation of application intent.
A blueprint can describe:
- entities
- fields
- relationships
- ownership
- roles and permissions
- metadata
- future route/page/layout structures
- future infrastructure intent
Blueprints are the primary source of truth for generation.
Architecture Generation Layer
Radish CLI compiles blueprints into generated architecture.
Today, the primary generated layer is the datalayer. It includes:
- contracts
- validation
- repositories
- services
- metadata APIs
- access-control-aware patterns
- documentation
- manifests
Application Layer
Developers and AI assistants build application behavior on top of the generated architecture.
This includes:
- UI code
- workflows
- integrations
- custom pages
- custom route behavior
- business-specific orchestration
Infrastructure / Operations Layer
Radish Hub and Radish Cloud operate above the generated application layer.
They manage concerns such as:
- blueprint lifecycle
- application orchestration
- deployment coordination
- version management
- environment organization
- hosted management