Canonical Stack

ArgoBox is currently hardening one supported stack first:

ArgoBox
Hermes
OpenClaw
Home Assistant

This is the stack the public docs, quickstart, and product framing should assume.

Layer Roles

ArgoBox

ArgoBox is the control plane.

Responsibilities:

approval queue
audit trail
capability gating
operator surfaces
infrastructure adapter boundaries

Hermes

Hermes is the operator-facing routing layer.

Responsibilities:

intake of operator requests
routing to the right subsystem
separating read-only work from privileged work
preserving a human-visible execution path

OpenClaw

OpenClaw is the agent runtime.

Responsibilities:

reasoning over requests
asking ArgoBox for actions
staying inside the capability and approval model

Home Assistant

Home Assistant is the home automation substrate.

Responsibilities:

device and automation integration
practical smart-home control
ecosystem leverage for the homelab wedge

ArgoBox wraps Home Assistant rather than replacing it.

Why This Stack First

This stack is the shortest path to a credible public story:

homelabbers get one installable system
developers get clearer boundaries and reusable seams later
AI operators get a concrete trust model instead of vague autonomy promises

The alternative is marketing the whole repo at once, which creates confusion about whether ArgoBox is a framework, a dashboard, an AI shell, or a personal lab archive.

What Is Deliberately De-Emphasized

The repo contains many other modules, tools, and experiments. They may remain useful, but they are not the lead public promise during this hardening phase.

Specifically de-emphasized:

side projects that do not strengthen the canonical stack
public copy that treats module count as the main value proposition
platform claims that assume the framework is already exportable

What “Done” Looks Like

The stack is behaving correctly when:

an agent asks ArgoBox for a privileged action
Hermes routes the request through the intended operator path
the action requires approval before mutation
the execution is logged and reviewable afterward
Home Assistant can participate as a first-class automation target

That is the core proof this stack is meant to produce.