Skip to main content
Batoi AIF Docs

RAD Integration

Connect AIF to Batoi RAD without making AIF core RAD-dependent.

Version Foundation release Early foundation work Reviewed Jul 21, 2026 Next review Sep 21, 2026
Start Reading Open AIF GitHub Report documentation issue

Owner: Batoi Engineering Reviewed by: Batoi AIF Maintainers Source revision: cd680e8

Start SafelyEvaluate AIF and learn the development and governed runtime boundary. Human ReviewPause operations before side effects and resume with replay-protected approval. Governed RAGApply workspace and ACL filters before ranking and retain citation evidence. RAD IntegrationUse the included PDO persistence, review, policy, queue, and context adapters.
AIF is the public engineering framework. For the managed intelligence capability used across supported Platform and Flex workflows, see Batoi Intelligence.
Browse Batoi AIF Documentation RAD Integration
On this page

RAD Integration

Batoi AIF includes a RAD integration profile under src/Rad/, forward and rollback migrations, schema validation, and MySQL integration coverage.

Included RAD Adapters

  • RadArrayContextResolver and RadRunDataContextResolver
  • RadRolePermissionChecker
  • RadPdoProviderCatalog
  • RadPdoPromptRegistry
  • RadPdoPolicyEngine
  • RadPdoAuditLog
  • RadPdoReviewRepository
  • RadPdoQueueAdapter
  • RadAifService, RadApiGatewayService, and code-assist integration services

Persistence Profile

The migration creates RAD application tables for workspace-scoped provider configuration, prompt versions, policy rules, immutable call logs, review requests, and durable queue jobs. Database triggers protect call-log immutability.

Use the migration and its matching rollback from database/migrations/rad/. Run aif-rad-schema-check.php against the configured schema before enabling governed runtime.

Deployment Boundary

RAD installations may load AIF through Composer or place a verified release at rad/vendor/batoi/aif. RAD routes should resolve trusted workspace context and call RadAifService, AifGateway, or AifApi; they should not invoke provider adapters directly.

RAD-specific behavior remains in the RAD profile so the framework core stays portable.