Architecture

Security Model

Review the practical trust model behind local execution and controlled tooling.

Overview

Overseer is designed as a local control plane: conversations, workflows, tools, and run records live on your machine first, and external providers are optional dependencies rather than the center of the product.

Operator Note

Overseer works best when each layer stays explicit: the orchestrator routes, supervisors execute, tools return evidence, and traces show what actually happened.

Getting Started

Understand which parts are local state, which parts depend on model runtimes, and which parts are packaged application assets.

Configuration

When you change architecture assumptions, start by documenting runtime dependencies and storage locations for the team using the app.

Examples

runtime-notes.txt

local_db = overseer.db
trace_events = sqlite
workflow_runs = sqlite
local_models = ollama
public_downloads = overseer-releases

Next Steps

Continue with Application Settings or head back to the documentation home.