前台场景
Experience layer
Frontstage scenarios
Generated and composed apps consume only governed adapters.
Citizen web appsFeishu surfacesDashboardsWorkflow consolesAgent-assisted workbenches
Layered architecture
Agentic enablement middle platform
AEP is the thick middle platform between frontstage app scenarios and backend systems of record. It orchestrates, governs, and assembles; backend systems keep data truth and transaction execution.
Agentic Enablement 中台 · 核心
Orchestration, governance, assembly
Agentic enablement platform
The middle platform owns catalog contracts, policy decisions, approvals, app templates, tool governance, release evidence, and audit trails.
Unified developer portal
Project context, visible capabilities, templates, approvals, and release evidence.
Six governed catalogs
API, MCP tools, business capabilities, data products, workflows, and app templates.
Agentic orchestration
App factory, agent orchestration, policy decisions, observability, and audit.
Release gates
Preview, approval, GitOps promotion, evidence bundle, rollback, and reconciliation.
sn_iam / OIDCVault / ESOAPISIX / MCP gatewayApproval and GitOps evidence
后台系统 / 数据
System of record layer
Backend systems and SOR boundary
Source platforms remain authoritative for data truth and transaction execution.
APISIX governed routesMCP tool gatewayEnterprise adaptersDataphin / isA_DataISA Model PlatformKafka / Flink / StarRocksERP / PLM / MES / SRMFinance / Commerce / PXM / IBP / MDM
Backend registration patterns
Backend systems are not exposed as naked APIs; they enter AEP through controlled patterns.
Read model
Data products and read-only APIs expose scoped consumption contracts.
Command write
Idempotent adapters require approval, SOR owner semantics, rollback, and compensation.
Event / CDC
Events enter the data platform; agents do not call source change streams directly.
Batch / file
File flows use checksum, validation, lake landing, and reconciliation evidence.
Hard governance boundaries
The frontend must make these limits visible before generated apps are released.
- Generated apps never call ERP, PLM, MES, or source databases directly.
- Agents can invoke only registered tools and policy-approved capabilities.
- Sensitive data and side-effecting tools require human review.
- Secrets stay in Vault/ESO references and never enter generated code.
- SOR owners retain transaction semantics, approvals, rollback, and audit accountability.