KDCube architecture
The interactive explorer needs JavaScript. This static map preserves the same boundaries; open the documentation hub for details. Components marked [gate] are governance checkpoints.
Your app & SDK
- App package — trusted async code, version, properties/secrets, storage, tests, and optional surfaces;
bundle remains the runtime identifier.
- Provider surfaces — reactive turns, REST, MCP, widgets/main views, jobs/cron, Data Bus, named services, and public content.
- Consumer surfaces — MCP service registry plus per-agent tools, MCP tools, named-service operations/actions, skills, models, subagents, and scene components.
- Tools — administrator inventory, conversation-scoped narrowing, runtime traits, and concrete operation fences [gate].
- Skills and instruction profiles — server-side instruction content selected by bounded IDs.
- Named services — provider-owned typed domains with discovery, schema, operations, block production, and pull policy.
- Economics & accounting SDK — covered model, embedding, web-search, and participating custom calls.
Experiences & clients
- Streaming chat, multiple widgets and main views, host scenes, Telegram Mini Apps, and public content.
- MCP provider and consumer paths for Claude, IDEs, external agents, and hosted agents; modern 2026-07-28 discovery and legacy initialize share one stateless server adapter.
- Provider integrations — Telegram, email/Gmail, Slack, LinkedIn, Google Sheets, and Google Docs.
- Payments & subscriptions — Stripe, wallets, plans, budgets, and settlement.
Governance gates
- Authority registry and request identity — Cognito/multi-Cognito, SimpleIDP for development, and app bundle-session authorities [authentication].
- Connection Hub — Delegated by KDCube grants for clients/agents and Delegated to KDCube connected provider accounts remain separate; provider tokens stay server-side [delegated authority].
- Admission, roles/grants and operation CSRF, optional upload scanning, economics reservation, tool policy, and generated-code isolation apply at their own boundaries.
Edge & classical runtime fabric
- Web proxy terminates TLS and routes authenticated/public surfaces; ingress owns live SSE/Socket.IO connections and event inception.
- Tenant/project-scoped ready/inflight queues, ordered conversation event lanes, relay pub/sub, Data Bus streams, job streams, cron locks, and worker discovery coordinate the processor fleet.
- Processor workers run trusted operator-approved app code, claim turns/jobs, reconcile cron, stream results, and emit accounting/telemetry.
Apps & agent frameworks
- Shared Agent Harness — framework-neutral event/ref resolution,
conv.timeline.v1, TurnLog/turn views, conv:fi: refs, distributed workspaces, and WorkspaceArtifact. It is not ReAct and not the Event Bus.
- ReAct adapter — a fresh runtime object per turn over durable state; descriptor-selected v2/v3, ANNOUNCE, cache policy, live event folding, round governance, tools, compaction, budgets, and optional fair-scheduled subagents.
- Hosted framework adapters — preserve LangGraph or another existing loop and its working memory behind a thin async host, stream adapter, bound state scope, accounted services, and shared conversation record.
- Claude Code — a hosted coding agent with bound workspaces, sessions, identity, and participating-call accounting.
Runtime fabric & execution
- In-process and
@venv paths run trusted app/tool code. Local subprocess mode is crash containment, not a security sandbox.
- Split Docker is the reference generated-code profile: a trusted supervisor and separate networkless executor with no platform/provider credentials or real-project mount [isolation boundary].
- Generated code may compute freely in its disposable workspace and request existing governed tools through
tool_call(tool_id, params); the supervisor supplies identity and credentials and checks the concrete operation.
- Legacy combined Docker and distributed Fargate execution have different documented boundaries and must not be described as equivalent to split Docker.
Infrastructure & operations
- PostgreSQL/pgvector, Redis/ElastiCache, and local/shared/object storage are logically scoped to the deployment's effective tenant/project.
- Deployment secrets, user-scoped connected-account credentials, ConnectionStore metadata, and Redis GrantStore state are distinct storage families.
- Six descriptors:
assembly.yaml, gateway.yaml, economics.yaml, secrets.yaml, bundles.yaml, and bundles.secrets.yaml. Runtime YAML and Redis caches are derived views.
- Deployment paths — CLI-managed local Docker Compose, Kubernetes/Helm, and an operator-maintained private ECS/Fargate Terraform path.
- Operational evidence — health, logs, telemetry, metrics, accounting, and OPEX; not automatically immutable audit or compliance evidence.
Recent changes
See the full changelog.
- August 1–2, 2026 (
main) — delegated authority hardening, operation CSRF, Google Docs workflows, and the sixth descriptor.
- July 27–30, 2026 — modern MCP, Google Workspace named services, and authority/delivery fixes.
- July 20–25, 2026 — per-account agent grants, governed agent configuration, SimpleIDP authority, and true cost reports.
- July 15–20, 2026 — app surface model, Shared Agent Harness, ReAct round governance, and delegated hosted agents.
