Hermes — Infrastructure Status

Classification: Internal AAF system. Not an off-the-shelf service.

What Hermes is

Per constitutions/.../AAF_CONSTITUTION_V5-1.md and the Agent Z constitution: Hermes is current, curated, executive intelligence — mission, authority, KPIs, objectives, priorities, preferred patterns, known constraints, recent lessons, department health. Explicitly not chat history, prompt history, verbatim memory, or archive. The constitution defines Hermes as part of the "Shared AI Framework," deployed twice (Holdings plane and Platform-Runtime plane) with separate data boundaries — i.e. an architecture AAF builds and operates, not a public package to pull.

Ground truth on the box

• No hermes process, container, image, port, or CLI.
• repositories/aaf-holdings/src/hermes/ holds content only — executive profile YAML (executives/agent-z.yaml, real-estate-executive.yaml, shared-platform-executive.yaml) and empty managers/missions/executives/ departments/ dirs. This is Hermes content, not a running Hermes service.
• engineering/hermes/ is an empty placeholder.

Install method

None — there is nothing to install. Hermes is a system to be built under a future engineering mission, then populated from the curated YAML already present. Building it is out of scope for an infrastructure bring-up / additive-only pass.

HQ01 reachability

N/A until built. HQ01 already reads the executive profiles directly from the filesystem (lib/executives/*), which is the correct interim source of curated executive intelligence and requires no Hermes runtime.

Blocker

Hermes must be designed and built (a product-engineering mission), with the Holdings/Platform plane separation enforced. No env var or placeholder is needed yet; HQ01 does not depend on a Hermes runtime today.