Product and usage guide

An AI application platform for enterprises and development teams, bringing together access control, business operations, knowledge, agents, workflows and multi-client applications.

Scope of this guide

Positioned as an enterprise AI application platform. Modules have code and documentary evidence. Deployment, providers, channels and project delivery require environment-specific acceptance.

Who it is for

Organizations and teams building internal systems, SaaS services and enterprise AI applications.

Business administration

Users, roles, menus, dictionaries and administration pages provide operational entry points, with business features organized by domain.

Identity, tenancy and access

Identity, tenancy, application context and permissions constrain access together. Identity integrations and deployment conditions require environment-specific validation.

AI, knowledge and agents

Manage providers, models, prompts, tools, agents, knowledge governance, evaluations and runs. Tool execution participates in permissions, budgets and human approval.

Workflows and scheduling

Workflow definitions, queues, approvals, message delivery and scheduling connect business actions with traceable progress and outcomes.

Content and site management

CMS capabilities organize sites, templates, content, previews and publication alongside content and storage services. This website prototype is not connected to that production flow.

Membership, commerce and entitlements

Membership, catalog, orders and payments separate purchase and fulfillment responsibilities, retaining records and compensation paths. Live payment channels require configuration and acceptance.

Development and multi-client integration

Code generation, diff previews, reviewed imports, client management and extension contracts support development across web, app and mini-program clients.

Audit, observability and operations

Operational events, observability, storage, usage and delivery records provide evidence for operations. Deployment, alerts and external-service availability are verified per environment.

A typical path

Define the business boundary → Connect capabilities and workflows → Validate and operate

Back to product documentation ↗