Sources, contracts & boundaries.

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Agent sessions · tools

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 17 · Source 27

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Messages · threads · membership

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 17

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Live media · notes · assets

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 18

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Meetings · agenda · sources

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 19

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Author · build · host

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 15

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Definitions · versions · runs

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 16

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Discover · approve · pin

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 21

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

JS · cron · goals · heartbeat

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 16 · Source 27

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Evidence · views · private memory

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 2 · Source 24 · Source 25

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Priorities · briefings · feedback

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 4 · Source 7 · Source 10

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Data · panels · layouts · sharing

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 20

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Directory · hierarchy · work lens

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 22

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Platform · Knowledge · runtime

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 23

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Identity · subscriptions · usage

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 26

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

OAuth · secrets · artifacts

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 26 · Source 27

Technical owner

See the linked capability map for service ownership

Entry / contract

Open the focused map for API and transport boundaries.

State / output

Devices · approvals · notifications

Change considerations

Source presence is not proof of rollout or client parity.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 27 · Source 29 · Source 30

Technical owner

frontend/web

Entry / contract

Browser → Matrix client APIs (chat/rooms) → AIBot runtime; plus product/feature REST

State / output

Web experiences and client state; reaches the assistant and human chat through Matrix, plus product REST APIs.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

Messaging / calls

Source 3 · Source 8

Technical owner

frontend/mobile

Entry / contract

Same routing method and backend as web: Matrix → runtime, plus shared product REST

State / output

Native client that reuses the same routing method and backend contracts as web, including the shared Matrix path.

Change considerations

Mobile reuses the web routing method and backend contracts, including the shared Matrix path; feature-branch routes are not additional released parity.

Upstream

No incoming relationship drawn.

Downstream

Messaging / calls

Source 3 · Source 8 · Source 29

Technical owner

frontend/electron

Entry / contract

Electron shell → hosted web; inherits the web Matrix routing + native permissions

State / output

Loads the hosted web app and inherits its Matrix routing; supplies native desktop permissions.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

Messaging / calls

Source 3

Technical owner

External services + client integrations

Entry / contract

Matrix client APIs carry client↔assistant messages into the runtime; meeting record/Scribe REST; backend token → LiveKit

State / output

Matrix carries human chat and client↔assistant messages; rooms/events route into the AIBot runtime, with meeting/call paths beyond AIBot.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Web app, Mobile app, Desktop app

Downstream

AIBot runtime

Source 17 · Source 18 · Source 19

Technical owner

backend/gateway

Entry / contract

Consumes Matrix room/session events; gateway chat/session RPC, tool calls and event relay

State / output

Coordinates assistant work and gateway requests; executes tools and relays events.

Change considerations

AIBot is not the Bot Service Gateway or the model gateway.

Upstream

Messaging / calls

Downstream

Service bridge, Model gateway, Knowledge, Execution services

Source 3 · Source 13

Technical owner

BSG repository — not in workspace

Entry / contract

Bot JWT → derived identity → product-service calls + fronts durable stores (memory index, user-content/file history) for query

State / output

Verifies the runtime bot JWT, derives the acting user identity, brokers authorized product-service calls (Command Center, rooms/membership, directory), and fronts durable stores — the memory index and user-content/file history — for query.

Change considerations

Local clients establish the contract; the runtime authenticates to BSG with a bot JWT. The BSG server was not inspected.

Upstream

AIBot runtime

Downstream

Memory index, Command Center

Source 4 · Source 9

Technical owner

External gateway + each AI consumer

Entry / contract

Consumer-selected alias + endpoint + credentials → model routing

State / output

Routes authorized model requests. Also used independently by Knowledge and CC.

Change considerations

Alias/provider targets and environment configuration are not live-verified.

Upstream

AIBot runtime

Downstream

No outgoing relationship drawn.

Source 12 · Source 13

Technical owner

backend/knowledge-base

Entry / contract

Authorized evidence / Ask / view interfaces; hybrid semantic + FTS retrieval dependency

State / output

Evidence and view service backed by per-user workspaces and immutable search revisions; retrieval uses hybrid semantic + full-text search.

Change considerations

The arrow from AIBot is a logical retrieval dependency, not a claim about all routing hops. Ask/persona memory is self-only.

Upstream

AIBot runtime, Brain Data

Downstream

No outgoing relationship drawn.

Source 2 · Source 24 · Source 25

Technical owner

Postgres memory index (fronted by BSG) + runtime SQLite shadow

Entry / contract

Durable agent memory: Postgres index fronted by BSG + runtime SQLite shadow; embeddings + FTS hybrid recall

State / output

Durable agent memory: a dual-write index — Postgres read path fronted by BSG plus a best-effort SQLite shadow — over embeddings and full-text for hybrid recall.

Change considerations

High-level concept. BSG also fronts bot/user-content history for query; conversation history itself is read through the runtime message tools.

Upstream

Service bridge

Downstream

No outgoing relationship drawn.

Source 13

Technical owner

backend/command-center

Entry / contract

CC reads and actions via AIBot → BSG → Command Center

State / output

Own collection and insight pipeline; API results and user actions pass through BSG.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Service bridge, Connected work, Brain Data

Downstream

No outgoing relationship drawn.

Source 4 · Source 7 · Source 10

Technical owner

AIBot + external execution infrastructure

Entry / contract

Sandbox backend (Docker / AgentCore / MicroVM) + browser and app-builder execution, selected by task

State / output

AgentCore authoring, shared app runners and generic MicroVM execution are separate axes.

Change considerations

High-level grouping of documented execution paths; not one audited deployment.

Upstream

AIBot runtime

Downstream

No outgoing relationship drawn.

Source 13 · Source 15

Technical owner

External Brain Data service

Entry / contract

Immutable L0 source snapshots and ingestion handoff

State / output

Supplies validated raw-source snapshots to Knowledge. CC can optionally fetch Slack L0.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Connected work

Downstream

Knowledge, Command Center

Source 2 · Source 4 · Source 6

Technical owner

External work systems + connector owners

Entry / contract

Source-specific collectors and connector APIs; coverage differs by service

State / output

Knowledge and CC have different source coverage and acquisition paths.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

Brain Data, Command Center

Source 2 · Source 4

Technical owner

External identity / access / placement services

Entry / contract

UMS identity/hierarchy; Vault credentials; Orchestrator assignment/placement

State / output

Identity/hierarchy, per-user credentials and runtime placement support multiple services.

Change considerations

Shared support dependencies are grouped; not all calls are drawn.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 2 · Source 4 · Source 13

Technical owner

External Matrix + web/mobile

Entry / contract

/_matrix/client/v3/createRoom; room events and membership

State / output

Matrix owns messages, threads/events and membership. A room is not an agent execution session.

Change considerations

Preserve room IDs, event schemas and access checks across clients.

Upstream

No incoming relationship drawn.

Downstream

Scribe change event

Source 17

Technical owner

External meeting service + LiveKit

Entry / contract

Backend SFU token path → LiveKit media

State / output

Live media and meeting records are distinct authorities.

Change considerations

Token scopes and media lifecycle are independent of assistant inference.

Upstream

No incoming relationship drawn.

Downstream

Meeting service

Source 18

Technical owner

Web CalendarPageClient + CC + meeting service

Entry / contract

useAgendaEventsQuery; listCalls / listMeetings

State / output

Calendar combines meeting records, CC agenda and caches. Calls redirects to Calendar.

Change considerations

Google Calendar source ≠ inferred agenda ≠ live meeting record; invalidate relevant caches.

Upstream

CC agenda, Meeting service

Downstream

No outgoing relationship drawn.

Source 19

Technical owner

backend/gateway + web session client

Entry / contract

chat / sessions RPC; useChatSessionGateway

State / output

Append-only JSONL keeps execution history; compaction does not delete that history.

Change considerations

Do not treat Matrix room IDs or Knowledge Ask session IDs as execution keys.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 17

Technical owner

External meeting service

Entry / contract

/meeting/v1/meetings/:id/scribe

State / output

Meeting processing is not owned by AIBot. Scribe serves legacy sections or block/markdown modes.

Change considerations

Keep response-mode compatibility, edit semantics and asset access.

Upstream

Live meetings

Downstream

Scribe, Calendar

Source 18

Technical owner

backend/command-center

Entry / contract

CC agenda via BSG / client queries

State / output

Meeting preparation and inferred planning are produced by CC stages.

Change considerations

A source calendar change need not immediately regenerate CC preparation.

Upstream

No incoming relationship drawn.

Downstream

Calendar

Source 7 · Source 19

Technical owner

Matrix event + web useMeetingScribe

Entry / contract

aic.meeting.scribe → refetch

State / output

Initial GET loads Scribe; Matrix version/change events trigger another GET. No polling.

Change considerations

Do not put the Scribe body contract on the event bus.

Upstream

Rooms

Downstream

Scribe

Source 18

Technical owner

Web Scribe UI + external meeting service

Entry / contract

GET/edit Scribe + assets

State / output

Meeting notes display after processing and update through event-triggered refetch.

Change considerations

aic-enable-scribe / meeting-series whitelist gate access.

Upstream

Meeting service, Scribe change event

Downstream

No outgoing relationship drawn.

Source 18

Technical owner

backend/knowledge-base

Entry / contract

Ask streaming + _index/ask-sessions/...

State / output

Ask has its own session bodies, metadata and leases; it is not a Matrix room or AIBot JSONL session.

Change considerations

Respect owner access and migration fallback.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 24

Technical owner

Web / mobile → main AIBot agent

Entry / contract

User intent → agent app-builder tool / CLI

State / output

The main agent delegates app planning, coding and troubleshooting.

Change considerations

Preserve user and tenant context across the authoring handoff.

Upstream

No incoming relationship drawn.

Downstream

AgentCore, Builder CLI

Source 15

Technical owner

External AgentCore + gateway app-builder

Entry / contract

aic-app-builder CLI → BSG

State / output

AgentCore authors app code; it is not the fleet that serves running apps.

Change considerations

Plan/coder/troubleshoot contracts can change separately from runtime hosting.

Upstream

App intent

Downstream

App control plane

Source 15

Technical owner

Web marketplace / Apps clients

Entry / contract

/marketplace/apps/owned; /aibot/api-proxy/apps/...

State / output

Clients list owned apps and call start/deploy operations.

Change considerations

Keep ownership, deployment status and start semantics distinct.

Upstream

No incoming relationship drawn.

Downstream

App control plane

Source 15

Technical owner

backend/gateway app-builder CLI

Entry / contract

User → main agent → aic-app-builder → BSG

State / output

CLI bridges builder workflows to service contracts.

Change considerations

Validate request, tenant identity and errors at the CLI/service boundary.

Upstream

App intent

Downstream

App control plane

Source 15

Technical owner

External BSG / app services

Entry / contract

App lifecycle APIs via BSG

State / output

Coordinates builds and placement on shared runners.

Change considerations

A build success is not proof of a running or publicly reachable deployment.

Upstream

AgentCore, Builder CLI, Owned apps

Downstream

Shared-runner fleet

Source 15

Technical owner

Gateway tools + external sandbox service

Entry / contract

Runtime sandbox/tool execution

State / output

Generic sandbox execution is a fourth, separate axis.

Change considerations

Do not migrate app-hosting assumptions into sandbox policies.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 13 · Source 15

Technical owner

External app platform / tenant storage

Entry / contract

apps/<appId>/; deployments/<appId>/

State / output

Tenant EFS retains app and deployment files.

Change considerations

Storage isolation, build artifacts and cleanup need independent checks.

Upstream

No incoming relationship drawn.

Downstream

Shared-runner fleet

Source 15

Technical owner

External app runtime fleet

Entry / contract

Build/place/start → runner

State / output

Shared runners host apps; AgentCore remains the authoring system.

Change considerations

Verify actual fleet placement, capacity and isolation in the owning service.

Upstream

App control plane, Tenant EFS

Downstream

Public app route

Source 15

Technical owner

External routing → BSG / runner

Entry / contract

/aibot/<env>/<app>

State / output

Public app routes front BSG/runner execution.

Change considerations

Route and access policy changes affect published app consumers.

Upstream

Shared-runner fleet

Downstream

No outgoing relationship drawn.

Source 15

Technical owner

Web routines client

Entry / contract

aic-enable-workflows; user-scoped aic-workflow-engine-v2

State / output

Feature flags select the workflow experience and engine.

Change considerations

Test both selected engine paths; source presence does not prove tenant enablement.

Upstream

No incoming relationship drawn.

Downstream

Workflow V2

Source 16

Technical owner

External workflow service

Entry / contract

/workflow/v2 via v2Rest / svcRest clients

State / output

Workflow service is the sole draft/list store for page-managed workflows.

Change considerations

Legacy and V2 contracts differ. V2 room install/actions are not equivalent to SVC support.

Upstream

Workflows page, Validate & push

Downstream

Runs & traces, Room actions

Source 16

Technical owner

External workflow service

Entry / contract

Publish / run / traces APIs

State / output

Published versions and runtime traces are distinct from local authoring state.

Change considerations

Verify execution semantics at the external service; do not infer them from CLI push.

Upstream

Workflow V2

Downstream

No outgoing relationship drawn.

Source 16

Technical owner

Gateway workflow-builder

Entry / contract

catalog → init / pull / edit

State / output

The builder uses catalog schemas to author compatible definitions.

Change considerations

Catalog/schema changes need authoring and validation regression checks.

Upstream

No incoming relationship drawn.

Downstream

Validate & push

Source 16

Technical owner

Gateway workflow-builder + workflow service

Entry / contract

validate → push

State / output

Push transfers a workflow definition; it is not publish or run.

Change considerations

Versioning, errors and remote draft ownership must remain compatible.

Upstream

Builder catalog

Downstream

Workflow V2

Source 16

Technical owner

Web / external workflow services

Entry / contract

V2 room install and action paths

State / output

Room integration varies by selected service implementation.

Change considerations

Do not assert SVC parity from V2 client support.

Upstream

Workflow V2

Downstream

No outgoing relationship drawn.

Source 16

Technical owner

backend/gateway automation tools

Entry / contract

JavaScript authoring / execution tool path

State / output

Agent-authored automation is separate from the page workflow service.

Change considerations

Apply sandbox, approval and credential policies for this execution path.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 16 · Source 27

Technical owner

backend/gateway scheduler/runtime

Entry / contract

Cron / heartbeat / goals runtime contracts

State / output

Scheduled agent turns are not workflow-service versions or runs.

Change considerations

Change timing, retry and delivery rules independently.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 27

Technical owner

backend/gateway goal tools

Entry / contract

Goal lifecycle / agent turns

State / output

Goals coordinate continuing assistant work.

Change considerations

Do not imply one shared durable job engine across all automation.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 27

Technical owner

Gateway marketplace discovery

Entry / contract

marketplace-skill-discovery feature flag

State / output

Discovery finds candidates; it does not install or authorize them.

Change considerations

Flag availability and catalog trust must be checked independently.

Upstream

No incoming relationship drawn.

Downstream

Trusted approval

Source 21

Technical owner

Gateway trusted approval path

Entry / contract

Explicit approval before installation

State / output

Only a trusted approval allows the installation path to proceed.

Change considerations

A model-supplied boolean must not be treated as authorization.

Upstream

Skill discovery

Downstream

Integrity checks

Source 21

Technical owner

Web marketplace + external services

Entry / contract

Owned items / share / revoke APIs

State / output

Marketplace covers more than skills: Apps, panels and sharing also exist.

Change considerations

Sharing and revocation need owner and consumer checks.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 15 · Source 20 · Source 21

Technical owner

Gateway marketplace installer

Entry / contract

Validate selected version and manifest/hash

State / output

Pinned, validated content is required before tenant installation.

Change considerations

Test malformed manifests, hash mismatches and version changes.

Upstream

Trusted approval

Downstream

Tenant-pinned skill

Source 21

Technical owner

Gateway skill installation

Entry / contract

skills/marketplace/<name>/SKILL.md

State / output

Validated skill instructions become tenant-pinned workspace content.

Change considerations

Track update, removal and tenant-isolation behavior.

Upstream

Integrity checks

Downstream

Agent runtime

Source 21

Technical owner

External Vault + connector owners

Entry / contract

OAuth consent and credential retrieval

State / output

Installing a skill does not grant access to an external connector.

Change considerations

Enforce connector scope and credential ownership separately.

Upstream

No incoming relationship drawn.

Downstream

Tool schemas

Source 21 · Source 26

Technical owner

backend/gateway core skills

Entry / contract

Runtime skill discovery

State / output

Core skills are not marketplace-installed content.

Change considerations

Bundled updates and tenant-pinned versions have different lifecycles.

Upstream

No incoming relationship drawn.

Downstream

Agent runtime

Source 21 · Source 27

Technical owner

backend/gateway agent runtime

Entry / contract

Runtime discovery of installed SKILL.md

State / output

Skill instructions guide the agent; executable tool schemas remain separate.

Change considerations

Instruction changes still need tool-policy and output checks.

Upstream

Tenant-pinned skill, Core skills

Downstream

Tool schemas

Source 21 · Source 27

Technical owner

backend/gateway tools/extensions

Entry / contract

Tool schema + policy + connector credentials

State / output

Tool calls are controlled by runtime policy and any required grants.

Change considerations

Extension inventory does not certify production enablement.

Upstream

Agent runtime, Connector grants

Downstream

No outgoing relationship drawn.

Source 21 · Source 27 · Source 30

Technical owner

Gateway dashboard-builder

Entry / contract

/aic_apps_api/dashboards/.../specs

State / output

Builder creates dashboard specifications and supporting data/layout assets.

Change considerations

Treat generated spec, data references and layout as separate contracts.

Upstream

No incoming relationship drawn.

Downstream

Dashboard specs

Source 20

Technical owner

Web marketplace clients + external APIs

Entry / contract

/marketplace/dashboard; specs / live panels / variable options

State / output

The dashboard surface has concrete API clients, not just a product vision.

Change considerations

Version specs and validate panel variables before changing the renderer.

Upstream

Dashboard Builder

Downstream

Dashboard surface

Source 20

Technical owner

Web customDashboard

Entry / contract

ECharts / markdown / grid editor

State / output

Web renders custom dashboards, edits layouts and applies cross-filters. Insights redirects here.

Change considerations

Check chart state, markdown rendering and variable interactions.

Upstream

Dashboard specs, Layout state

Downstream

Dashboard consumers

Source 20

Technical owner

Gateway universal_dashboard_viewer

Entry / contract

SQL runner / Databricks configuration

State / output

Dashboard viewers have data-source-specific execution paths.

Change considerations

Keep source credentials, SQL safety and refresh permissions isolated.

Upstream

No incoming relationship drawn.

Downstream

Universal viewer

Source 20

Technical owner

Gateway universal_dashboard_viewer

Entry / contract

Charts / refresh / migration tools

State / output

A separate viewer path owns saved config, queries, charts and migrations.

Change considerations

Not all dashboards share the same rendering engine or data API.

Upstream

Source engines

Downstream

No outgoing relationship drawn.

Source 20

Technical owner

Gateway Tableau integration

Entry / contract

Tableau tool / connector path

State / output

Tableau is an additional integration, not the universal dashboard backend.

Change considerations

Validate its own authentication and capabilities.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 20

Technical owner

Web dashboard clients + external API

Entry / contract

Layouts / grid GET + PUT

State / output

Layout writes are distinct from spec and data-query writes.

Change considerations

Test reload, edits and compatibility with existing grids.

Upstream

No incoming relationship drawn.

Downstream

Dashboard surface

Source 20

Technical owner

Web marketplace sharing clients

Entry / contract

Dashboard sharing / revocation APIs

State / output

Shared dashboard access is independent of panel refresh and layout state.

Change considerations

Do not infer query permission solely from a shared UI link.

Upstream

No incoming relationship drawn.

Downstream

Dashboard consumers

Source 20 · Source 21

Technical owner

Web marketplace / dashboard

Entry / contract

Dashboard view / variable selection

State / output

Consumers depend on specs, permissions, source availability and rendering behavior.

Change considerations

Change-impact reviews must cover all four dependencies.

Upstream

Sharing, Dashboard surface

Downstream

No outgoing relationship drawn.

Source 20

Technical owner

Web / Matrix user directory

Entry / contract

Matrix user_directory search

State / output

Directory identity answers who a person is; it is not a reporting graph.

Change considerations

Preserve Matrix identity mapping and directory visibility rules.

Upstream

No incoming relationship drawn.

Downstream

CC People lens

Source 22

Technical owner

External UMS

Entry / contract

/user/direct-reports; CC UMS enrichment/search

State / output

UMS supplies hierarchy and identity enrichment to multiple consumers.

Change considerations

Live hierarchy changes can change retrieval authorization.

Upstream

No incoming relationship drawn.

Downstream

Knowledge access, CC People lens

Source 22

Technical owner

Orchestrator + Vault → CC scheduler

Entry / contract

Orchestrator assignment list + Vault eligibility

State / output

Current scheduler eligibility is not a UMS user-enumeration loop.

Change considerations

Do not implement changes from stale UMS enumeration comments.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 22

Technical owner

backend/command-center

Entry / contract

CC people outputs + UMS enrichment

State / output

The People lens is synthesized work context, not the directory or hierarchy itself.

Change considerations

Trace source context, identity joins and story synthesis separately.

Upstream

People directory, UMS hierarchy

Downstream

No outgoing relationship drawn.

Source 7 · Source 22

Technical owner

backend/knowledge-base

Entry / contract

Authorized evidence retrieval; live UMS hierarchy

State / output

Owner and allowed reporting scopes govern evidence access.

Change considerations

Manager access to work evidence never grants access to a report’s private Ask persona.

Upstream

UMS hierarchy

Downstream

No outgoing relationship drawn.

Source 22 · Source 24

Technical owner

Web AdminConsoleGuard

Entry / contract

profile.admin_console_access

State / output

The web guard controls entry to an external admin iframe.

Change considerations

UI hiding is not a substitute for external server authorization.

Upstream

No incoming relationship drawn.

Downstream

Platform Admin

Source 23

Technical owner

External admin implementation + web host

Entry / contract

Runtime URL /aic/overview + user token

State / output

The external Admin Panel implementation is not in this workspace.

Change considerations

Verify token audience, iframe boundary and server permissions with its owner.

Upstream

Admin entitlement

Downstream

No outgoing relationship drawn.

Source 23

Technical owner

backend/knowledge-base admin

Entry / contract

Views / extraction / cleanup / retention controls

State / output

Knowledge Admin manages Knowledge jobs and lifecycle separately.

Change considerations

Retention and cleanup changes require data-lifecycle tests.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 23 · Source 25

Technical owner

Gateway / AIBot operations clients

Entry / contract

Operational reset/restart contracts

State / output

Runtime operational controls are not the Platform Admin console.

Change considerations

Validate destructive scope and tenant isolation.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 23 · Source 27

Technical owner

backend/gateway exec approvals

Entry / contract

requiresExecApproval → allow-once / allow-always / deny

State / output

A shell command missing the allowlist (or any command when ask=always) is blocked and forwarded to a human before it runs; elevated (“sudo”) mode is itself a gate — it needs tools.elevated.enabled + allowed + allowFrom.<provider>, else it is forced off.

Change considerations

Defaults security=deny, ask=on-miss, askFallback=deny — fails closed. ~2-min approval timeout; allow-always persists an allowlist entry. Skipped for allowlisted/safe builtins; only elevated-full bypasses. Forwarder is channel-agnostic (works off Matrix). A tool-result safety filter can still block secret-exfil / prompt-override in the output.

Upstream

No incoming relationship drawn.

Downstream

Agent-to-agent send

Source 27

Technical owner

backend/gateway ask_question tool

Entry / contract

ask_question card, destructive hint; blocks, never auto-selects

State / output

Delete / permanent-stop and any confirm-first action present a clickable card and wait; on the 3-minute timeout it returns no-answer and stops — it never auto-selects. Separately, in a group room a NON-owner using a Tier-2 tool triggers a real owner-approval card (5-min, per-room mutex) before it runs.

Change considerations

The ask_question tool is UNREGISTERED off Matrix (channel≠matrix or no room target ⇒ null), so on Slack/Telegram/Discord this and every confirm-first item degrade to prompt-only. Empty selection = no answer. The group owner-approval gate is inert in DMs, for the owner, and for Tier-1 read tools.

Upstream

No incoming relationship drawn.

Downstream

Invite / kick a person

Source 27

Technical owner

backend/gateway + app-builder + workflow

Entry / contract

One-time click token · owner Apply on diff · durable approval/choice/prompt

State / output

Marketplace install needs the user’s actual click (one-time ~5-min token); tenant-config needs an owner Apply on a diff (Matrix+owner+sender-bound, 5-min, optimistic-concurrency guard); workflows can park on approval()/choice()/prompt()/send(buttons). Publishing/sharing an app has its own server gates: a plugin needs an APPROVED version first, and only the app owner may share/update it.

Change considerations

All fail closed except choice(), which AUTO-SELECTS its first option on timeout. approval() = 10-min deny, supports a delegated assignee, and auto-denies off-pod (no HITL transport). Install rides ask_question, so it too is Matrix-only. BSG also 403s app-owner mismatches and the reserved system-skill-* namespace.

Upstream

No incoming relationship drawn.

Downstream

Blocked-outright actions

Source 21 · Source 16

Technical owner

backend/gateway sessions-send tool

Entry / contract

tools.agentToAgent.enabled + allow allowlist → else forbidden

State / output

Sending to another agent (or spawning A2A work) is refused unless agent-to-agent is enabled and the target is on the allowlist — a config gate, not a human ask. A cross-tenant target is always forbidden, and a sandboxed sub-agent can only reach sessions it spawned.

Change considerations

Fail-closed: disabled by default ⇒ forbidden. No human-approval step before spawning a sub-agent. Sub-agents also run a fixed tool-deny list (no gateway, sessions_send, install, memory, cron) and cannot spawn deeper.

Upstream

Shell command approval

Downstream

Send to anyone but you

Source 9 · Source 27

Technical owner

BSG → UMS → Synapse

Entry / contract

invite-precheck 403s · kick uses caller power level

State / output

Adding or removing someone runs as the acting human: BSG’s invite-precheck refuses (owner not in room, invitee not a person, not a group, owner cannot invite) and Synapse enforces the caller’s own power level on kick. Deleting a room needs the caller to be a live room admin (403 not_room_admin) — a distinct gate from kick.

Change considerations

Server-side refusal, not an ask. The bot can never exceed what its owner may do in the room; where PL is unreadable it defers to Synapse. Enterprise invite fan-out is also throttled by a per-server token bucket.

Upstream

Destructive confirmation

Downstream

Spend · external writes

Source 4 · Source 17

Technical owner

backend/gateway tool policy + exec + UMS auth

Entry / contract

Exec writing aibot.json throws · SAAS_MANDATORY_DENY (gateway, nodes) · banned/deleted user 403

State / output

Some actions are refused with no ask at all: a shell command that writes aibot.json is hard-blocked (use the config method), a mandatory deny (gateway, nodes) can never be re-enabled by a tenant, and every call made as a banned or marked-for-deletion user is 403/401’d server-side.

Change considerations

Tenants can only narrow tool policy, never widen; the mandatory deny is unioned in last. Protected/infrastructure config fields cannot be changed. Email send and other high-rate paths are also 429-throttled per bot. Using a stored secret is policy-governed, not a per-use ask.

Upstream

Install · config · workflow HITL

Downstream

Where gates do not fire

Source 27

Technical owner

backend/gateway messaging tools

Entry / contract

System-prompt confirm-first; recipient identity not code-gated

State / output

The prompt tells the model to confirm (show recipient + content, wait for a matching yes) before messaging, emailing, broadcasting or a calendar invite to anyone but the current user; WHO you message is not code-gated. But WHERE is: a code policy blocks sends outside the bound room/provider unless cross-context is explicitly allowed, and in a channel chat only the owner may act in other rooms.

Change considerations

The recipient confirm is model + ask_question no-auto-select only, so it is unenforced off Matrix; the cross-context / cross-room block is real code and always applies. Replying to the current user is never gated; file sharing is a separate multi-option confirm flow with a permanence warning.

Upstream

Agent-to-agent send

Downstream

No outgoing relationship drawn.

Source 9 · Source 27

Technical owner

backend/gateway tools

Entry / contract

Confirm-first; most spend prompt-only, but compute has a hard credit gate

State / output

Spending money, purchasing, publishing to a registry, or external writes (tickets, PRs, third-party APIs), and destructive ops like delete/force-push/DB changes are confirm-first instructions. One kind of spend IS code-enforced: provisioning a MicroVM runs a fail-closed credit check and refuses (402 credit-exhausted / 503) when the tenant is out of credit.

Change considerations

Purchase/payment writes have no dedicated code gate — prompt-only, hard-gated only if routed through the shell (exec), plus the uncertain/low-confidence rule tells the model to ask first. The MicroVM credit gate is real (flag-gated, re-checked at resolution to catch races).

Upstream

Invite / kick a person

Downstream

No outgoing relationship drawn.

Source 26

Technical owner

backend/gateway runtime

Entry / contract

Non-Matrix degrade · cron/goals bypass · non-asks

State / output

Off Matrix the ask tools are absent so confirm-first is prompt-only; autonomous turns (cron, goals, heartbeat) do not call ask_question and are gated only by session send-policy. Some things people expect to ask do not: replying to you, request_connection (your ask is the consent), device pairing (a human approves an inbound node). Secrets are their own model: in a group chat only pre-approved vault keys are usable, and any other key auto-requests approval.

Change considerations

Send-policy defaults to allow unless a deny rule is set. request_connection blocks ~5 min for the OAuth round-trip; pairing is owner-initiated, not a bot self-prompt. Node/device pairing requests expire after 5 min.

Upstream

Blocked-outright actions

Downstream

No outgoing relationship drawn.

Source 26 · Source 27

Technical owner

Brain Data

Entry / contract

Immutable L0 source records → changed-content selection

State / output

Raw connector material retained as source objects, not user-facing answers.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

L1 extraction

Source 2 · Source 6

Technical owner

Knowledge / workspace/l1-processing.ts

Entry / contract

Effective prompt/config + source hashes → durable L1 batches and validated citations

State / output

Conversation-aware L1 batches use capability-only Pi in the owner workspace, cumulative retries and exact citations. No generic shell/filesystem tools.

Change considerations

Prompt edits alone do not trigger historical re-extraction. Saved config can override the default prompt.

Upstream

Source records

Downstream

Published L1

Source 5 · Source 25

Technical owner

Knowledge / workspace revisions

Entry / contract

Validated evidence and search artifacts → CURRENT revision publication

State / output

Validated content and indexes become visible through CURRENT publication.

Change considerations

L1 owner scope and source attribution are enforced during retrieval.

Upstream

L1 extraction

Downstream

Views, Ask

Source 2 · Source 6

Technical owner

Knowledge / view-generation workflow

Entry / contract

Scheduled/on-demand generation over authorized evidence

State / output

Separate scheduled/on-demand generation over the owner and allowed report memory.

Change considerations

Publishing L1 does not mean every view is immediately regenerated.

Upstream

Published L1

Downstream

Ask

Source 2 · Source 6

Technical owner

Knowledge Ask + authorized memory consumers

Entry / contract

Authorized evidence and generated views → cited answers; self-only private memory

State / output

Retrieves allowed evidence and synthesizes answers. L1 can be retrieved without a generated view.

Change considerations

Private Ask memory/persona is self-only; manager retrieval must not expose report persona.

Upstream

Views, Published L1

Downstream

No outgoing relationship drawn.

Source 11 · Source 24

Technical owner

CC collectors

Entry / contract

Source-specific CC collectors; optional Brain Data Slack L0

State / output

Collects Slack, Gmail, calendar, Matrix and meeting data; selected Slack traffic can use Brain Data L0.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

Signals

Source 4

Technical owner

CC stage 1

Entry / contract

Stage-1 source extraction and open-work resolution checks

State / output

Source-specific model calls extract signals and check whether open work was resolved.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Collect

Downstream

Stories

Source 7

Technical owner

CC stage 2

Entry / contract

Stage-2 synthesis using signals, active work and stored CC preferences

State / output

Synthesizes work stories and people context, incorporating existing active work and CC preferences.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Signals, Feedback & preferences

Downstream

Priorities, Briefings

Source 7 · Source 10

Technical owner

CC priority pipeline

Entry / contract

stage2-priorities.md executed inside run_stage3

State / output

Uses stories plus previous groups and feedback to build and assign priority groups.

Change considerations

The stage2-priorities prompt is executed inside run_stage3.

Upstream

Stories, Feedback & preferences

Downstream

Deliver

Source 7 · Source 10

Technical owner

CC stage 3 / calendar stage 4

Entry / contract

Parallel stage-3 narrative/agent outputs and calendar preparation

State / output

Separate narrative/agent outputs and calendar preparation use story and calendar context.

Change considerations

The map groups two output stages. Same-run narrative does not consume the new priority output; draft generation is disabled in the inspected caller.

Upstream

Stories

Downstream

Deliver

Source 7

Technical owner

CC → BSG → AIBot → clients

Entry / contract

Persisted CC results → BSG → AIBot → client product surfaces

State / output

Persisted output is returned to product surfaces. Partial runs can retain usable results.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

Priorities, Briefings

Downstream

Feedback & preferences

Source 4 · Source 7

Technical owner

CC actions + dream pipeline

Entry / contract

Rating reason → recent context / consolidation → future CC preferences

State / output

Recent feedback influences future priority groups; consolidation writes CC preferences that influence future stories.

Change considerations

Not model-weight training. Rating, resolving and unrating are distinct operations.

Upstream

Deliver

Downstream

Stories, Priorities

Source 8 · Source 9 · Source 10

Technical owner

Brain Data → Knowledge

Entry / contract

Immutable source snapshots / ingestion handoff

State / output

Unchanged source-content hashes are no-ops even after a prompt edit.

Change considerations

Historical prompt changes require explicit reprocessing; do not promise automatic backfill.

Upstream

No incoming relationship drawn.

Downstream

Durable L1 batches

Source 2 · Source 5 · Source 25

Technical owner

Knowledge bounded ingestion workers

Entry / contract

Capability-only Pi; durable cumulative retries

State / output

Extraction uses owner workspace capabilities, not generic shell/filesystem tools. GitHub commits batch by repo/UTC day with exact citations.

Change considerations

Review effective prompts, batch identity, retries and source attribution together.

Upstream

L0 source inputs

Downstream

Published evidence

Source 25

Technical owner

Knowledge shared workspace runtime

Entry / contract

CURRENT revisions; reusable search/embedding artifacts

State / output

Published revisions expose attributed evidence and reusable search artifacts.

Change considerations

Embedding changes can require compatible index rebuilds; publication ≠ view regeneration.

Upstream

Durable L1 batches

Downstream

Ask & retrieval

Source 2 · Source 6 · Source 25

Technical owner

Knowledge view workflows

Entry / contract

Authorized owner/report evidence → generated document

State / output

Views are derived documents with a separate generation lifecycle.

Change considerations

Reprocess L0, regenerate a view and retrieve an answer are different actions.

Upstream

No incoming relationship drawn.

Downstream

Ask & retrieval

Source 2 · Source 6

Technical owner

Knowledge Ask + live UMS authorization

Entry / contract

Ask streaming; evidence retrieval + citations

State / output

Ask retrieves authorized work evidence. Persona is guidance, never performance evidence.

Change considerations

Check citations, owner access and manager/report privacy independently.

Upstream

Published evidence, Generated views, Private Ask memory

Downstream

DBOS + control DB

Source 11 · Source 22 · Source 24

Technical owner

Knowledge assistant memory

Entry / contract

assistant-memory/CURRENT; journals / persona

State / output

Memory and persona are self-only. A manager cannot retrieve a report’s persona.

Change considerations

Explicit mutation waits; automatic turn capture is asynchronous.

Upstream

No incoming relationship drawn.

Downstream

Ask & retrieval

Source 24

Technical owner

Knowledge Ask session store

Entry / contract

_index/ask-sessions/...; historical migration fallback

State / output

Bodies live in workspace storage; Postgres stores metadata/leases.

Change considerations

Keep session migration fallback and metadata/body consistency.

Upstream

DBOS + control DB

Downstream

No outgoing relationship drawn.

Source 24

Technical owner

Knowledge Postgres + DBOS workers

Entry / contract

Bounded worker ingestion + separate scheduler queue

State / output

Durable execution and publication commits use Knowledge control-plane state.

Change considerations

Do not transfer DBOS retry assumptions to CC single-attempt pipeline jobs.

Upstream

Ask & retrieval

Downstream

Ask session bodies

Source 14 · Source 24 · Source 25

Technical owner

Knowledge lifecycle workers/admin

Entry / contract

Durable derived cleanup; database retention

State / output

Workspace-derived cleanup and database retention are distinct lifecycle work.

Change considerations

Test retries, references, leases and retained records before deleting data.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 23 · Source 25

Technical owner

Feature owner / reviewer

Entry / contract

Entry point → transport → service owner

State / output

Start with the affected surface, selected engine/flag and technical authority.

Change considerations

Check upstream requests and downstream consumers; arrow direction is not a complete impact analysis.

Upstream

No incoming relationship drawn.

Downstream

2 · Follow the contract

Source 3 · Source 16 · Source 30

Technical owner

Cross-service owners

Entry / contract

Request / event / persisted representation

State / output

Inspect each boundary for validation, authorization, defaults and saved state.

Change considerations

An external service with consumer evidence still needs owner-side verification.

Upstream

1 · Define the change

Downstream

3 · Verify the rollout

Source 4 · Source 9 · Source 15 · Source 23

Technical owner

Implementers + release owners

Entry / contract

Tests / flags / backfill / observability

State / output

Plan compatibility tests and any data replay or cache invalidation explicitly.

Change considerations

No diagram certifies deployed versions or organizational ownership.

Upstream

2 · Follow the contract

Downstream

No outgoing relationship drawn.

Source 5 · Source 11 · Source 16 · Source 25

Technical owner

Knowledge prompt/config owner

Entry / contract

Default extraction prompt + saved override

State / output

Saved configuration may override the default; changing the file alone may not change the effective prompt.

Change considerations

Verify selected prompt/model and extraction schema.

Upstream

No incoming relationship drawn.

Downstream

Explicit reprocessing

Source 5 · Source 12

Technical owner

Knowledge ingestion owner

Entry / contract

L0 hashes → durable L1 ingestion

State / output

Unchanged content is skipped; historical re-extraction needs an explicit plan.

Change considerations

Test retries, exact citations, publication and evaluation before broad replay.

Upstream

Effective L1 prompt

Downstream

Regenerate & evaluate

Source 5 · Source 6 · Source 25

Technical owner

Knowledge serving owner

Entry / contract

Published L1 → views and evidence retrieval

State / output

Downstream views may need regeneration; Ask can retrieve evidence directly.

Change considerations

Do not include CC as a proven L1 downstream consumer.

Upstream

Explicit reprocessing

Downstream

No outgoing relationship drawn.

Source 6 · Source 11 · Source 25

Technical owner

Web / mobile CC clients

Entry / contract

First selected tag → underscore-separated reason

State / output

Only the first negative tag is sent today, even if the UI selects more.

Change considerations

A multi-reason feature is a larger contract change than one new reason.

Upstream

No incoming relationship drawn.

Downstream

Closed allowlists

Source 8

Technical owner

Gateway CC actions + CC API

Entry / contract

Accepted reason enum / allowlists; TEXT column

State / output

Both server layers validate reason values. UI-only additions are rejected.

Change considerations

One new reason does not inherently require a DB migration; update both validators.

Upstream

Client reason picker

Downstream

Future preferences

Source 9

Technical owner

CC feedback + dream pipeline

Entry / contract

Feedback → recent priority context / consolidation

State / output

Recent feedback affects priority grouping; consolidated CC preferences influence future stories.

Change considerations

This is neither model-weight training nor Knowledge private memory.

Upstream

Closed allowlists

Downstream

No outgoing relationship drawn.

Source 10

Technical owner

AIBot runtime

Entry / contract

Conversation + routing + tool policy + skills → dynamic inference loop

State / output

Combines conversation context, routing, tool policies and skills; can choose model paths dynamically.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

LiteLLM gateway

Source 13

Technical owner

Knowledge AI feature configuration

Entry / contract

Per-feature model/effort config for extraction, compose, Ask, retrieval, embeddings

State / output

Separate model/effort settings for L1 extraction, compose, Ask, retrieval and embeddings.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

No incoming relationship drawn.

Downstream

LiteLLM gateway

Source 12

Technical owner

CC config + stage assembly

Entry / contract

Per-substage model/effort and per-user LiteLLM credentials

State / output

Separate prompts and per-substage model/effort settings; per-user LiteLLM credentials.

Change considerations

aibot/cc-usage is a configured alias, not a verified concrete model.

Upstream

No incoming relationship drawn.

Downstream

LiteLLM gateway

Source 7 · Source 12

Technical owner

Each service / feature

Entry / contract

Feature instructions + output schemas; conceptual control, not a service

State / output

There is no single universal platform prompt. Prompt contracts and output validation live with their consumers.

Change considerations

This is a conceptual control, not an additional deployed service.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 5 · Source 7 · Source 12

Technical owner

External model gateway

Entry / contract

Authorized model request with effective alias / endpoint / credentials

State / output

Routes requests using the effective alias, endpoint and credentials supplied by the consumer.

Change considerations

A shared gateway does not mean a shared default model, shared prompt, or shared tenant context.

Upstream

Assistant, Knowledge, Command Center

Downstream

Text & reasoning, Embedding models, Media models

Source 12 · Source 13

Technical owner

Runtime + service identity boundaries

Entry / contract

Tenant/user identity + task policy; cross-cutting control, not a universal service

State / output

Model access must retain the correct tenant/user credentials and task permissions.

Change considerations

This is a cross-cutting control, not one universal access-control service.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 12 · Source 13

Technical owner

Configured model/provider routes

Entry / contract

Environment-selected text/reasoning provider routes

State / output

Model families used for inference. Exact effective models require environment verification.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

LiteLLM gateway

Downstream

No outgoing relationship drawn.

Source 12 · Source 13

Technical owner

Knowledge / runtime search consumers

Entry / contract

Content/query embeddings with model-compatible index dimensions

State / output

Represent saved content and queries for search. They are distinct from chat models.

Change considerations

Changing embedding model/dimensions may require rebuilding compatible indexes.

Upstream

LiteLLM gateway

Downstream

No outgoing relationship drawn.

Source 12 · Source 13

Technical owner

Tool-specific runtime configuration

Entry / contract

Tool-specific image/audio/provider paths; not one universal model gateway path

State / output

Documented runtime tools use their own provider/model paths. This is not a claim that every media call uses one route.

Change considerations

Verify tenant authorization, request/output compatibility and the owning service before changing this boundary.

Upstream

LiteLLM gateway

Downstream

No outgoing relationship drawn.

Source 13

Technical owner

Frontend delivery surfaces

Entry / contract

Browser/native clients → service entry points

State / output

Clients access hosted web/product services and assistant channels.

Change considerations

Verify deployed configuration, credentials, lifecycle and actual placement with the infrastructure owner; source manifests are not live inventory.

Upstream

No incoming relationship drawn.

Downstream

Access / routing

Source 3

Technical owner

Ingress / service gateways — deployment dependent

Entry / contract

Logical ingress boundary; DNS, load balancers and live routes not audited

State / output

Logical access boundary. Exact production ingress, load balancers, DNS and route placement were not audited.

Change considerations

Verify deployed configuration, credentials, lifecycle and actual placement with the infrastructure owner; source manifests are not live inventory.

Upstream

User devices

Downstream

Web workload, AIBot runtime

Source 3 · Source 4

Technical owner

frontend/web / helm

Entry / contract

Repository Helm service/workload templates for Next.js

State / output

Helm service/workload templates exist for hosting the web application.

Change considerations

This is not proof of a specific live replica count or ingress topology.

Upstream

Access / routing

Downstream

No outgoing relationship drawn.

Source 14

Technical owner

AIBot + external Orchestrator

Entry / contract

Documented gateway runtime + external Orchestrator placement

State / output

Runtime placement and tenant contexts are coordinated with external orchestration.

Change considerations

Runtime workload shown from documented architecture; no live pod placement was checked.

Upstream

Access / routing

Downstream

Core services, External execution, Knowledge API

Source 3 · Source 13

Technical owner

Knowledge API workload

Entry / contract

Authorized workspace content APIs and Knowledge control-plane access

State / output

Serves workspace content and authorized APIs. Separate DBOS-worker deployment templates are present.

Change considerations

Verify deployed configuration, credentials, lifecycle and actual placement with the infrastructure owner; source manifests are not live inventory.

Upstream

AIBot runtime

Downstream

Shared workspace, Knowledge control DB

Source 14 · Source 2

Technical owner

Knowledge DBOS worker deployment

Entry / contract

Configurable DBOS worker deployment; durable workspace jobs

State / output

Runs checkpointed ingestion/view workflows and reads/writes shared workspace revisions.

Change considerations

Worker deployment is independently configurable; current live replica layout is unverified.

Upstream

Brain Data

Downstream

Shared workspace, Knowledge control DB

Source 6 · Source 14

Technical owner

Command Center process

Entry / contract

FastAPI + scheduler + bounded workers in one process; Postgres job queue

State / output

HTTP API, scheduler and bounded worker loops run in the same process; jobs are persisted in Postgres.

Change considerations

A failed production pipeline job is not automatically requeued; later triggers create a new run.

Upstream

Core services

Downstream

Command Center DB

Source 4 · Source 14

Technical owner

External service repositories

Entry / contract

BSG service identity/routing; UMS hierarchy; Vault credentials

State / output

Service identity, organization hierarchy, credentials and Orchestrator dependencies support the workloads.

Change considerations

Not placed inside a specific network/cluster boundary because their deployment was not audited.

Upstream

AIBot runtime

Downstream

CC workload

Source 4 · Source 13

Technical owner

External model and execution services

Entry / contract

LiteLLM / AgentCore / shared runners / MicroVM; app tenant EFS

State / output

Separate LiteLLM model access, AgentCore authoring, shared-runner app hosting and MicroVM tool execution. App source/deployments use tenant EFS.

Change considerations

Verify deployed configuration, credentials, lifecycle and actual placement with the infrastructure owner; source manifests are not live inventory.

Upstream

AIBot runtime

Downstream

No outgoing relationship drawn.

Source 13 · Source 15

Technical owner

External Brain Data deployment

Entry / contract

Source snapshots → shared workspace; ingestion handoff → Knowledge

State / output

Produces source snapshots in the shared workspace and hands off ingestion to Knowledge.

Change considerations

Verify deployed configuration, credentials, lifecycle and actual placement with the infrastructure owner; source manifests are not live inventory.

Upstream

No incoming relationship drawn.

Downstream

DBOS workers, Shared workspace

Source 2 · Source 6

Technical owner

Brain Data sources + Knowledge memory/views

Entry / contract

Owner folders, published CURRENT revisions, evidence/views/Ask bodies

State / output

Canonical workspace content includes evidence, views, private assistant memory and Ask session bodies; search artifacts support serving.

Change considerations

Volume technology, backups and physical storage topology are not asserted by this diagram.

Upstream

Knowledge API, DBOS workers, Brain Data

Downstream

No outgoing relationship drawn.

Source 2 · Source 24 · Source 25

Technical owner

Knowledge control plane

Entry / contract

Postgres metadata/leases and DBOS workflow state; not canonical content bodies

State / output

Knowledge control/run metadata, Ask metadata/leases and DBOS state; canonical Ask bodies stay in the workspace.

Change considerations

Shown as a logical database boundary. No physical server separation is implied.

Upstream

Knowledge API, DBOS workers

Downstream

No outgoing relationship drawn.

Source 14 · Source 24 · Source 25

Technical owner

Command Center

Entry / contract

Postgres source projections, durable queue, results and feedback

State / output

CC source projections, run outputs, durable job queue and feedback state.

Change considerations

Shown separately to communicate ownership, not verified hosting separation.

Upstream

CC workload

Downstream

No outgoing relationship drawn.

Source 4 · Source 14

Technical owner

Web/mobile clients + external account APIs

Entry / contract

Account / session / onboarding / deletion clients

State / output

Account flows establish user context and lifecycle boundaries.

Change considerations

Deletion requires owner-by-owner retention review; no global deletion guarantee is inferred.

Upstream

No incoming relationship drawn.

Downstream

Billing & usage

Source 26

Technical owner

Clients + external billing services

Entry / contract

Subscription / payment / topup API clients

State / output

Commercial state and usage visibility have distinct service contracts.

Change considerations

Verify entitlements and payment-side idempotency with the external owner.

Upstream

Account lifecycle

Downstream

No outgoing relationship drawn.

Source 26

Technical owner

External Vault + connector integrations

Entry / contract

OAuth consent / connector credentials

State / output

Per-user secrets and grants support authorized integrations.

Change considerations

A UI connection or installed skill does not imply every tool can use the credential.

Upstream

No incoming relationship drawn.

Downstream

Research & media

Source 26 · Source 27

Technical owner

Client file surfaces + gateway tools

Entry / contract

File / artifact tool and client paths

State / output

File attachments and generated artifacts participate in assistant work.

Change considerations

Check tenant scope, content access, URLs and retention for each storage path.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 27 · Source 30

Technical owner

Web/mobile clients + Electron shell

Entry / contract

Notification/unread clients and native integration

State / output

Clients differ in delivery and permission behavior; Electron loads hosted web.

Change considerations

Test native permissions and unread synchronization separately from web behavior.

Upstream

Native clients

Downstream

No outgoing relationship drawn.

Source 26 · Source 29 · Source 30

Technical owner

frontend/mobile + frontend/electron

Entry / contract

Expo / React Native; Electron hosted web

State / output

Mobile main is the baseline; design-revamp routes are secondary branch evidence only.

Change considerations

Do not label additional feature routes as shipped mobile parity.

Upstream

No incoming relationship drawn.

Downstream

Notifications

Source 29 · Source 30

Technical owner

Gateway tools / extensions + providers

Entry / contract

Deep research / browser / voice / TTS paths

State / output

Tools have provider-specific execution paths and capabilities.

Change considerations

Extension presence is not production enablement; verify permissions and model routes.

Upstream

Vault & connections, Execution controls

Downstream

No outgoing relationship drawn.

Source 27 · Source 30

Technical owner

Gateway runtime / nodes

Entry / contract

Approval / tenant-agent / device-node contracts

State / output

Approval, tenant agent routing and device execution define additional trust boundaries.

Change considerations

Verify authorization before executing tools or acting through devices.

Upstream

No incoming relationship drawn.

Downstream

Research & media

Source 27

Technical owner

Gateway operations / service owners

Entry / contract

Usage / health / log APIs

State / output

Operational diagnostics help inspect runtime behavior and failures.

Change considerations

Live deployment topology, provider mappings and enabled extensions remain unaudited.

Upstream

No incoming relationship drawn.

Downstream

No outgoing relationship drawn.

Source 27 · Source 30