Skip to content
LightHouse Docsv0.8.0

Concepts

View as Markdown

LightHouse and the engine are built from a small set of ideas. Each has a page; this one shows how they fit.

 Your tenant  (https://<tenant id>.atlanticagenticlabs.com)        Atlantic's account
 ┌──────────────────────────────────────────────────────────────┐
 │ LightHouse: people, roles, keys, approvals, limits, billing  │
 │ API  ·  MCP  ·  portal                                       │
 └──────────────▲──────────────────────────────┬────────────────┘
                │ operational telemetry         │ signed commands
                │ (counts and timings)          │ (pause, approve, caps)
 ┌──────────────┴──────────────────────────────▼────────────────┐
 │ Your deployment: the Atlantic Agentic Engine                 │  Your account
 │ gateway ── models          orchestrator ── agents (cards)    │
 │ knowledge bases ── your sources     content reader           │
 └──────────────────────────────────────────────────────────────┘
  • Tenants. One client: its own address, its own people and keys, its data isolated by row-level security.
  • Agents. An agent is a card: its job, its tools, its budget, its effect and its autonomy. Its ID is <pack>:<card>.
  • Handlers. The people who pause agents, set caps, grant pre-approvals and decide on outputs.
  • Knowledge bases. Your sources, indexed in your account and read in place.
  • Evidence. What an answer was grounded in, and how strong that evidence is.
  • Approvals. A person signs off an output before it counts; never an agent, never a key.
  • Runs. One execution of a pack’s agents: its steps, calls, cost and outcome.
  • The gateway. The only thing that calls a model, where caps, the kill switch and the tool gate are enforced.
  • Deployment profiles. Ephemeral or always-on: whether the engine’s services sleep when nothing is asked of them.
  • The telemetry contract. What crosses from your account to LightHouse: counts and timings, never content.