Skip to main content
Batoi RAD Docs

Architecture

Understand the public application boundaries and request flow in Batoi RAD.

Version 1.x Active framework documentation Reviewed Jul 21, 2026 Next review Oct 21, 2026
Start Reading Open Batoi RAD GitHub Report documentation issue

Owner: Batoi Engineering Reviewed by: Batoi RAD Maintainers Source revision: bb9902c

Browse Batoi RAD Documentation Architecture
On this page

Architecture

Batoi RAD separates the public web root, application runtime, reusable framework services, and application-owned features. This boundary keeps public assets intentionally publishable while configuration, data, logs, and application logic remain outside direct web access.

Request Flow

Public requestHTTPS boundaryRouteLoad and authorizeServicesRules and dataResponseUI or API

Routes should coordinate a request, not absorb an entire feature. Reusable business rules belong in focused application classes. Rendering stays in page templates, while data access and policy checks remain server-side.

Design Principles

  • Expose only deliberate public assets and entry points.
  • Keep identity, authorization, and workspace context explicit.
  • Validate input before business rules or persistence.
  • Keep framework services reusable and application features independently maintainable.
  • Treat audit evidence, errors, and operational signals as part of the application contract.