Batoi UIF and AIF
Batoi Press includes local Batoi UIF primitives for admin and installer screens, and Batoi AIF scaffolding for future governed intelligence features. AIF is disabled by default and makes no AI network calls unless a future provider is explicitly configured.
Bundled UIF
Batoi Press bundles UIF primitives locally for admin and installer screens.
Runtime files:
public_html/assets/uif/uif.css
public_html/assets/uif/uif.js
radpress/uif/manifest.json
radpress/uif/components/The admin console renders through Batoi\Press\Admin\AdminLayout, which loads the local UIF stylesheet and script. The public custom theme layer is independent: a theme may use UIF, but Batoi Press does not require public themes to be UIF-only.
UIF Usage In Admin
The current admin console uses UIF-backed primitives for:
- Grouped sidebar navigation.
- Topbar actions.
- Page headers.
- Stats cards.
- Structured tables.
- Editor panels.
- Status and role badges.
- Notices, empty states, and danger-zone actions.
AIF Boundary
Batoi AIF is optional and disabled by default.
Configuration:
radpress/config/aif.jsonDefault behavior:
enabledisfalse.- Provider is
disabled. - No AI network calls are made.
- Admin can view status at
/admin/aif. - Guarded content-assist actions at
/admin/aif/assistreturn a disabled response until configured. - The admin status screen shows provider availability, feature flags, workspace requirement, and network-call trust boundaries.
Future provider adapters can implement Batoi\Press\Aif\AifProvider. Future Batoi Platform workspace adapters can implement Batoi\Press\Aif\BatoiWorkspaceAifProvider.