Domain boundary
Owns the capability namespace, shared prompt behavior, linked collections, and enabled platform tools.
Platform architecture
A request architecture built around owned capabilities.
LiyaEngine separates the application-facing intent contract from retrieval, tools, model execution, policies, and evidence so each layer can evolve without breaking product integrations.
Request lifecycleFrom authenticated call to observable result
01 / INGRESSTenant + intent
02 / ASSEMBLEPrompt + context
03 / EXECUTEModel + tools
04 / RETURNValidate + trace
POST /v1/rundomainintentinputStable edgeApplications call a domain-owned intent contract rather than a provider SDK.
Composable runtimeGrounding, tools, models, memory, and policies are assembled from configuration.
Evidence by requestExecution context is available for debugging, evaluation, and cost review.
Core layers
Clear responsibilities from control plane to runtime.
The architecture keeps ownership and execution concerns separate while connecting them through the domain and intent model.
Request sequence
What happens when an intent is called.
Both the unified run endpoint and the domain/intent path resolve to an owned intent before runtime behavior begins.
01
Authenticate and resolve
Validate the tenant credential, domain, intent, and request contract.
02
Assemble execution context
Load shared behavior, schema, linked knowledge, memory, tools, and model settings.
03
Execute and govern
Run retrieval, model or agent work, and configured policy checks.
04
Return and record
Validate the response shape, return the result, and retain operational evidence.
Operating principles
Make the production boundary understandable.
Strong platform UX makes ownership, behavior, controls, and evidence visible to the people responsible for the capability.
01
Control plane
Dashboard and management APIs define domains, intents, knowledge links, tools, models, policies, and credentials.
02
Data plane
Authenticated runtime requests execute the selected intent using its current tenant configuration.
03
Ownership model
Collections are centrally managed and linked to domains; intents live inside domains; agent behavior is enabled within an intent when needed.
Questions
Useful context before you build.
Can an application call a domain without an intent?+
No. Runtime work resolves to an intent. The domain supplies ownership and shared configuration; the intent supplies the callable capability contract.
Which API shape should I use?+
LiyaEngine supports the unified POST /v1/run shape and an equivalent domain/intent path. Choose one convention and keep it consistent in the consuming application.
Where do workflows fit?+
Workflows coordinate platform actions and intent calls as an orchestration surface. They are not a replacement for the intent contract exposed to applications.
Design the boundary before choosing the model.
Start with the domain and intent contract, then attach the runtime behavior the capability requires.