Oblive Overview
Understand the supported runtime, operating surfaces, and system boundaries.
Oblive is a local-first, self-hosted system for retaining organization context, coordinating agent profiles, and executing business work through durable tasks. The product separates conversation, work ownership, execution attempts, human decisions, and external effects so each state remains inspectable and recoverable.
Main Surfaces
| Surface | Purpose |
|---|---|
| Chat | Explore requests, clarify intent, and deliberately create durable work |
| Tasks | Track ownership, dependencies, execution attempts, blockers, and outcomes |
| Human Inbox | Answer structured questions, review actions, and reconcile uncertain effects |
| Context | Inspect retained sources, citations, health, evidence gaps, and revisions |
| Schedules | Review recurring context audits, learning work, and other durable triggers |
| Integrations | Grant selected profiles bounded access to organization-owned tools |
Runtime Shape
The supported local stack includes Docker Compose, PostgreSQL with pgvector, Redis,
Garage-compatible object storage, a backend, a frontend, a chat runtime, and task workers. Runtime
configuration is generated from the machine-local config/local-stack.json file.
Supported Profiles
- Operator: coordinates organization-wide work and delegates durable execution.
- Chat: handles responsive conversations and onboarding.
- Growth: owns acquisition, activation, retention, and experiments.
- Engineering: owns product delivery, reliability, and technical work.
- Support: owns customer issue analysis, responses, escalation, and follow-through.
Department profiles are optional, but Growth, Engineering, and Support are the currently supported department identities. Add capabilities to these profiles through skills and integrations unless a broader product change intentionally introduces another department.
Observable Boundaries
- Conversation does not become a task unless durable ownership and follow-through are required.
- Organization knowledge remains source-backed and inspectable through Context.
- Missing evidence and judgment return through typed Human Inbox items.
- Consequential external effects follow access, approval, execution, and reconciliation policy.
- Provider credentials stay behind the backend execution boundary.
- PostgreSQL and object storage own durable state; queues and live delivery are transport.
Continue
Read Operating Boundaries, then follow Getting Started to run Oblive locally.