Platform
A unified architecture for metadata, surfaces, navigation, and secure operations
This page explains the platform layer the way ServiceNow-style public sites explain their platform: one foundation that powers public discovery, authenticated admin work, and role-based portal experiences.
Platform outcomes
The real value is consistency: data, UI metadata, navigation, surfaces, and routing all follow one backend-owned contract.
- +Metadata-driven schema and UI layers
- +Security context plus ACL-aware read and launch paths
- +Public, backend, and portal surface split
Schema
Metadata-first
New tables and fields flow through sys_db_object and sys_dictionary.
UX
Composable
Pages, forms, lists, and shells reuse the same primitives.
Routing
Authoritative
Surface and landing decisions stay server-side.
Platform layers
Metadata
Schema and configuration backbone
Tables, fields, validation, and drift tracking are all managed through platform metadata rather than direct schema shortcuts.
Security
Trusted actor and access model
Roles, groups, landing policies, module visibility, and portal access all resolve through the same backend runtime.
Surface runtime
Public, backend, and portal shells
Each experience gets its own shell, routes, and theming while staying part of the same platform.
Build on the platform
Use one architecture to ship public, admin, and portal experiences
The value of the platform shows up in how quickly new pages, shells, and navigation paths can be added without rewriting access logic.