Classical intelligence path
Specialist response and workflow execution
- Governed Bee model releases and tier routing
- Tenant-scoped retrieval, memory and citations
- Approved tools, structured workflows and streamed output
Architecture centre
A reviewable path from request to governed result.
Bee separates customer surfaces, identity and entitlement, specialist orchestration, execution, tenant data, and assurance evidence. These diagrams describe the public system contract; customer-specific Enclave controls are fixed in the deployment manifest and Order Form.
Bee reference architecture
One specialist-intelligence system. Clear execution boundaries.
Bee Specialist Intelligence System (BSIS) is the architecture that turns a request into a governed specialist response. It coordinates domain intelligence, current knowledge, tenant retrieval, tools, model execution, safety, evaluation and release control; the model is one component, not the whole product.
Customer and integration layer
One governed entry point across every Bee surface
Bee Workspace
API & SDKs
MCP & tools
Enterprise systems
Bee Specialist Intelligence System
The governed intelligence and orchestration core
01
Understand the task
Resolve intent, user context, entitlements and policy before execution.
02
Compose specialist intelligence
Select across 66 specialist domain families, permitted research, tenant retrieval and tools.
03
Route the right execution
Choose an eligible Bee tier, model release, workflow and deployment boundary.
04
Evaluate and control
Apply safety, quality, release evidence, metering, telemetry and rollback controls.
Explicit quantum-compute path
Governed access to real quantum hardware
- Local simulation before any hardware submission
- Entitlement, privacy, circuit and spend controls
- Reviewed real-QPU target with metered results and evidence
Security and evidence plane
Quantum-Native Security Infrastructure (QNSI)
HEOSSI’s security platform supplies post-quantum key, payload-protection and tamper-evident evidence paths using NIST-standardized cryptography, with the exact transport and deployment boundary fixed by the customer environment.
Ordinary AI requests stay on the classical inference path.
Quantum execution is explicit, bounded, entitled and budget-controlled.
Tenant knowledge is resolved inside the authenticated customer boundary.
Public transport uses TLS 1.3; post-quantum transport is separately scoped.
Knowledge stays governable
Current research and tenant material remain attributable and updateable without silently changing model weights.
Controls travel with the request
Identity, policy, data boundary, metering and evidence remain attached through routing and execution.
Quantum is a separate decision
A customer chooses a quantum workload explicitly; normal chat never incurs hardware execution or cost.
Execution contracts
Shared entitlement does not mean identical client powers.
Every surface resolves the active subscription before model capacity is provisioned. Bee Code and its CLI use the durable agent route. Workspace, mobile, and desktop use product chat routes, while SDK and MCP calls perform only the operation explicitly requested by their caller.
Durable Bee Code execution requires a matching client and production agent API release. A Marketplace listing page alone is not evidence of version parity; the current published client state is recorded on the download page.
| Surface | Execution path | Local effects |
|---|---|---|
| BEE Code · CLI | Durable manager, bounded specialists, verifier | Approved IDE or CLI tools |
| Workspace · mobile · desktop | Workspace chat and product workflows | Product-owned tools only |
| SDK · hosted MCP | Documented API or MCP operation | No customer-machine access implied |
Enterprise scenario flows
See where identity, data, execution, and evidence travel.
Each scenario follows the same architectural rule: authenticate first, authorise the capability and data boundary, execute through the eligible path, and retain evidence for the effects that actually occurred.
Governed coding in the IDE
A durable, subscription-bounded manager coordinates metered specialist work while the developer authorises each local effect.
- 1IDE context
- 2Bounded agent run
- 3Local approval
- 4Edit · verify · Git evidence
The client advertises only installed tools. External and MCP effects are revalidated and require fresh approval.
Bee Code clients Tenant-scoped knowledge
Authenticated retrieval adds permitted document evidence before a governed model response is composed.
- 1Tenant request
- 2Entitlement
- 3Scoped retrieval
- 4Cited response
Indexes, source passages, and citations remain attached to the authenticated tenant boundary.
Retrieval contract Explicit quantum reasoning
Quantum hardware is a separate, reviewed workload path; it is never an implicit side effect of ordinary chat.
- 1Bounded problem
- 2Local simulation
- 3Policy · spend review
- 4QPU result evidence
Hardware submission requires explicit entitlement, approved targets, limits, and metering.
Quantum boundary