TOAST: routing optimization through conversation
How TOAST connects a supervisor, specialist agents, and the routing engine, with implementation notes by Juni Lee and co-authors.
Read storyEngineering · Engineering
OIP: the foundation for running operational intelligence
How shared identity, permissions, deployment, and observability connect optimization capabilities to business applications.
From an optimization result to a working service
A solver can calculate a plan. An application must also know who requested it, which organization’s data it may use, and how to follow an execution when something goes wrong. These concerns recur across routing, scheduling, and other operational decisions.
OIP - Operational Intelligence Platform - is the common infrastructure layer in Omelet’s architecture. Its role is to bring identity, permissions, deployment, observability, and audit into the operation of OCP services and business applications.
Three responsibilities, one connected system
Business applicationsWorkflows, user interaction, and domain data
OCP & optimization servicesProblem meaning, constraints, and computation
OIP · shared operational foundationIdentity · Permissions · Deployment · Observability · Audit
Applications express the work people need to do. OCP services connect that work to domain-specific optimization capabilities. OIP provides the common operating foundation around them. This separation lets a domain team focus on problem formulation and solution quality while sharing operational infrastructure.
Identity and context belong in the execution path
A request needs more than a prompt. The platform design must carry an authenticated identity and an authorized organizational context through the service boundary. Access to a tool and access to its underlying data are related decisions; both matter when several teams use the same capabilities.
Observe the work, not just the answer
For a long-running optimization task, a useful operating view connects the request, execution state, and resulting output. Traces help investigate failures and delays. Audit records help explain which action was taken and under whose authority. These are engineering concerns alongside the quality of the computed solution.
Keep building and operating distinct
Designing and validating an application is one activity; deploying and operating it in an organization is another. OIP gives that second activity a shared architectural home. The aim is to reuse operational capabilities across applications while keeping each application’s workflow and optimization logic explicit.
This article introduces OIP’s architectural role. It is not a release note or a statement that every integration is available in a deployed environment.