Platform Handbook
Versioned documentation of how OMS is built and operated. Decisions, architecture, conventions, playbooks, and lessons — written for the humans and AI agents who work on the system next.
Architecture
Platform Architecture
OMS is a single execution kernel: one router, one auth surface, one data plane. Brains are modules on that kernel, not separate apps.
AI Foundations — Triad, Four V's, Analytics Ladder
Every AI feature in OMS rests on three load-bearing ideas: the Algorithms + Data + Compute triad, the Four V's of data (with Veracity as the gate), and the Analytics Ladder from Descriptive to Prescriptive.
Decisions
Kernel Copilot Pattern
Instead of N admin panels, one endpoint fans out to every subsystem, summarises the state with AI, ranks prioritised actions, and answers grounded questions.
Kernel SLO Contract
The public /api/public/kernel/health endpoint is the single source of truth for system health. Its slo block is a stable contract external monitors can alarm on without re-deriving the logic.
Conventions
Route Definition of Done
A new public route is not shipped until it has SEO metadata, navigation entry points, sitemap presence, and error boundaries.
Documentation Conventions
Handbook entries capture durable decisions and mechanics. Roadmap holds priorities. Memory holds cross-session rules. Chat is not documentation.