Notebook execution components
Platform documentation defines supported behavior. Implementation detail stays with the owning repositories and upstream runtime projects.
| Component | Responsibility | Source baseline |
|---|---|---|
| Oqullus | Notebook tabs, editing, execution presentation, kernel controls, save state, and recovery UX | sparqd/oqullus at 363355f968fe |
| BFF API | Authenticated Jupyter HTTP proxy, kernel-channel bridge, and Workspace file upload facade | sparqd/bff-api at 93ea18e72414 |
| Workspace file management backend | Canonical notebook objects, versions, history, diff, and revert | sparqd/workspace-file-management-backend at a6c5eb793e6b |
| Platform stacks | JupyterHub, Enterprise Gateway, Spark runtime, persistence, profiles, and lifecycle deployment policy | sparqd/platform-stacks at a71390d12463 |
| JupyterHub | Authenticated per-user Jupyter Server lifecycle and routing | JupyterHub technical overview |
| Jupyter Server | Notebook session identity and kernel API | Jupyter Server architecture |
| Enterprise Gateway | Remote-kernel lifecycle, persisted connection metadata, and reconnection | Enterprise Gateway availability |
| Spark Operator and Kubernetes | SparkApplication lifecycle and driver/executor scheduling | Deployment-owned runtime services |
See the canonical Notebook execution assessment for behavior and the architecture for cross-component state ownership.