Legal & compliance
Review documents against owned policies, return structured findings, and retain execution evidence.
Production patterns
Start with the work your team needs AI to do.
Use LiyaEngine to turn business-owned workflows into named, testable capabilities. These patterns are starting points, not a fixed catalog of supported domains.
Pattern mapOne operating model across every domain
01 / OWNDomain boundary
02 / DEFINEIntent contract
03 / GROUNDManaged context
04 / OPERATETrace evidence
POST /v1/rundomainintentinputTenant-ownedTeams create the domains and capabilities that match their organization.
ComposableKnowledge, tools, models, and controls are attached where the work needs them.
ObservableEach request retains the evidence needed to test and improve behavior.
Common starting points
Patterns for teams shipping real AI features.
Begin with an outcome, then adapt the domain, schema, knowledge, and policy configuration to your product.
Education
Build curriculum-aware review, tutoring, feedback, and content workflows with controlled outputs.
Healthcare operations
Support administrative workflows with scoped knowledge and explicit policy boundaries.
Financial operations
Classify, extract, reconcile, and explain operational data using schema-bound responses.
From requirement to runtime
Keep ownership intact as the capability matures.
The same lifecycle works whether the first use case is a product API, an internal agent, or a governed workflow.
01
Model the domain
Define the team or product boundary that owns the capability.
02
Design the intent
Specify input, output, instructions, and runtime behavior.
03
Connect context
Link knowledge and approved tools without duplicating ownership.
04
Test and operate
Exercise the contract, inspect traces, and improve with 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
No fixed vertical catalog
Your tenant creates its own domains, intents, agents, workflows, and knowledge model.
02
One contract per capability
Application code calls a named intent instead of embedding provider-specific prompt logic.
03
Controls travel with execution
Retrieval, guardrails, routing, tools, and tracing remain part of the operating path.
Questions
Useful context before you build.
Are these the only supported use cases?+
No. They are examples of production patterns. LiyaEngine tenants create custom domains and capabilities for their own work.
Do I need a separate stack for each domain?+
No. Domains provide ownership boundaries inside the same platform operating model.
Can a domain serve both APIs and agent behavior?+
Yes. Intents expose the callable contract, and agent behavior can be enabled when a capability needs approved tools or multi-step execution.
Model the first capability your team owns.
Create a tenant workspace, define a domain, and turn the outcome into a callable intent.