greentic-runner
主要的生产运行时,负责托管和执行 flows、管理 sessions,并协调所有平台服务。
Greentic 采用分层架构,并对关注点进行清晰分离:
┌─────────────────────────────────────────────────────────┐│ Messaging Channels ││ (Slack, Teams, Telegram, WhatsApp, WebChat) │└─────────────────────────────────────────────────────────┘ │ ▼┌─────────────────────────────────────────────────────────┐│ Gateway (HTTP/NATS) ││ Public Endpoint Router │└─────────────────────────────────────────────────────────┘ │ ▼┌─────────────────────────────────────────────────────────┐│ greentic-runner ││ (Production Runtime Host) ││ ┌─────────────────────────────────────────────────┐ ││ │ Flow Executor │ ││ │ (Wasmtime Component Model) │ ││ └─────────────────────────────────────────────────┘ ││ ┌─────────────────────────────────────────────────┐ ││ │ Session Manager │ ││ │ (Memory / Redis) │ ││ └─────────────────────────────────────────────────┘ │└─────────────────────────────────────────────────────────┘ │ ▼┌─────────────────────────────────────────────────────────┐│ WASM Components ││ (Flows, Providers, MCP Tools, Custom Components) │└─────────────────────────────────────────────────────────┘greentic-runner
主要的生产运行时,负责托管和执行 flows、管理 sessions,并协调所有平台服务。
greentic-flow
用于 .ygtc 文件的 flow schema 定义、中间表示(IR)、加载器与校验器。
greentic-pack
Pack 构建 CLI,用于创建已签名的 .gtpack 归档,其中包含 flows、components 和 assets。
greentic-component
用于构建 WASM components 的组件编写 CLI 与运行时工具集。
| 层级 | 技术 | 用途 |
|---|---|---|
| WASM Runtime | Wasmtime v41 | Component model 执行 |
| Async Runtime | Tokio v1 | 异步 I/O、任务调度 |
| HTTP Server | Axum v0.8 | REST API、webhooks |
| Message Bus | NATS | 事件分发、发布/订阅 |
| Session Store | Memory/Redis | Flow 状态持久化 |
| Secrets | AWS/Azure/GCP/Vault | 凭证管理 |
1. External Message (e.g., Slack) │2. Webhook Handler (Provider Ingress) │3. NATS: greentic.messaging.ingress.{env}.{tenant}.{team}.{channel} │4. Flow Router (tenant/team resolution) │5. Flow Executor (WASM component execution) │6. Session State Update │7. Reply/Action Nodes │8. NATS: greentic.messaging.egress.{env}.{tenant}.{team}.{channel} │9. Provider Egress → External Service1. Bundle Configuration (greentic.demo.yaml) │2. Pack Resolver (local/OCI registry) │3. Signature Verification (ed25519-dalek) │4. CBOR Metadata Parsing │5. WASM Component Instantiation │6. WIT Interface Binding │7. Runtime RegistrationGreentic 在每一层都实现了租户隔离:
Tenant └── Environment (prod, staging, dev) └── Team └── Channel (messaging provider instance) └── Session (user conversation state)TenantCtx 结构体会贯穿所有操作:
pub struct TenantCtx { pub tenant_id: String, pub env_id: String, pub team_id: Option<String>,}Greentic 使用 WebAssembly Interface Types (WIT) 规范来定义组件接口:
package greentic:component;
interface types { record message { id: string, content: string, sender: string, timestamp: u64, }
record outcome { success: bool, data: option<string>, error: option<string>, }}
world component { import types; export execute: func(input: types.message) -> types.outcome;}greentic-types ─────────────────────────── (foundation) ↑greentic-telemetrygreentic-interfaces ← greentic-typesgreentic-config ← greentic-types ↑greentic-session ← greentic-typesgreentic-state ← greentic-types + greentic-interfacesgreentic-flow ← greentic-interfaces + greentic-types ↑greentic-pack ← greentic-flow + greentic-typesgreentic-component ← greentic-interfaces + greentic-typesgreentic-mcp ← greentic-interfaces + greentic-types ↑greentic-runner ← ALL of the aboveGreentic 使用 OpenTelemetry 实现分布式追踪与指标采集: