Engineering Pillars Connected to Accountable Controls
RAD structures application execution, UIF structures interfaces, and AIF structures AI orchestration. Identity, Integrations, Govern, Guard, and evidence contracts supply the scoped authority and controls around them.
From platform architecture to public engineering work
Engineering Foundations explains the platform architecture. Open Source Initiatives lists public frameworks and tools. Documentation helps developers adopt them.
Three Engineering Concerns, Shared Control Contracts
RAD, UIF, and AIF separate application execution, interface systems, and AI orchestration. They consume scoped identity, integration, policy, security, evidence, and deployment contracts rather than owning those control planes.
Batoi RAD
Application execution foundation for governed RAD applications, route structure, workflow behavior, and API-facing delivery.
Flow and API capabilities are part of the RAD foundation.
View foundation contextBatoi UIF
Interface framework for layout, interaction patterns, UI primitives, accessibility, and consistent product surfaces.
Current public source entry point for the framework family.
View Batoi UIF pageBatoi AIF
AI orchestration framework for provider abstraction, prompt governance, tool mediation, evaluation, evidence, and application integration.
Standalone PHP framework with RAD and UIF integration profiles.
View Batoi AIF pageSecurity and assurance around the foundations
Some open source projects are not framework pillars, but they are strategically important because they help teams use the foundations safely.
MCP Audit
Security auditing and policy checks for MCP servers, agent tooling, exposed tools, SBOMs, SARIF, and CI evidence.
Supporting project for AI integration security and assurance, not a fourth framework pillar.
Why the Foundation Is Split This Way
The split follows the way governed systems are built: applications need runtime structure, users need consistent interfaces, and AI needs accountable orchestration.
- RAD provides the governed runtime model for routes, application structure, workflow behavior, data boundaries, and API-facing delivery.
- UIF keeps interface systems consistent across public pages, product surfaces, workspaces, and future real-time interaction models.
- AIF structures agents, model routing, evaluations, and mediated tool execution without granting providers implicit platform authority.
- Shared control-plane contracts bind Identity, Integrations, Govern decisions, Guard blockers, enforcement evidence, and deployment context to the engineering stack.
How the Foundations Fit Together
The framework stack supports both Batoi products and customer-built systems without splitting governance, auditability, or deployment discipline.
Open Source Status
Public source is available for UIF, AIF, and the supporting MCP Audit project. RAD remains an application execution foundation within Batoi Platform.
| Framework | Source State |
|---|---|
| Batoi UIF | Public source available |
| Batoi AIF | Public source available |
| MCP Audit | Public supporting project |
From Architecture to Engineering Practice
Start with the architecture, then explore the public framework source and documentation available today.