Skip to content

Operations Overview

Last Updated: 2026-03-12 Purpose: Operating surface summary for the Jorvis and OpenClaw platform.

What This Covers

  • The public-facing runtime surfaces that matter to users and reviewers
  • The difference between application runtime, OpenClaw runtime, and observability
  • The categories of health checks used after significant changes

Runtime Surfaces

  • Open WebUI is the primary browser-facing chat surface.
  • Jorvis API owns application contracts, backend routing, and document processing (including Google Docs/Drive ingestion and file format processing).
  • OpenClaw runs as the assistant/copilot runtime behind the bridge path.
  • Observability is a separate operational surface used to confirm service health and diagnose failures.

Operating Principles

  • Public documentation should describe the operating model without exposing internal dashboard URLs, credentials, or task-governance ledgers.
  • Persisted Open WebUI bridge updates remain a manual operational step when the bridge function changes.
  • Post-change verification needs both backend/runtime health and user-path checks; a single 200 response is not enough on its own.