Honcho — Infrastructure Status

Classification: Real open-source software (Plastic Labs). Self-hostable. In AAF doctrine, Honcho is the reflection engine — observes, reflects, compresses, evaluates, promotes, archives, forgets; holds nothing itself; never executes work.

Ground truth on the box

• No honcho process, container, image, port, or CLI.
• No Postgres / pgvector container (Honcho's required datastore).
• engineering/honcho/ and src/honcho/ are empty placeholders.

Official install method (for reference — NOT yet executed)

Honcho self-hosting is a stateful, multi-component deployment:

1. Datastore: PostgreSQL with the pgvector extension.
2. Honcho server: the API/deriver service (Docker image / docker compose from the upstream repo).
3. LLM provider credentials: the deriver/reflection path calls a model provider (e.g. Anthropic/OpenAI) — an API key is mandatory for Honcho to be functional, not merely running.
4. Plane decision: the constitution requires a Holdings-plane Honcho deployment, separated at the deployment level from any Platform-Runtime Honcho (separate data boundaries, no shared memory/profiles). Which plane this box hosts, and the network/isolation boundary, is a governance decision.

This would live under infrastructure/compose/honcho/ as its own compose stack, mirroring the existing traefik/ and hq01/ pattern, with secrets kept out of git.

Why it was not installed this pass

This is an additive / no-credentials infrastructure pass. Standing up a stateful Postgres+Honcho stack that calls a paid LLM provider requires (a) a provider API key I do not hold, and (b) the plane/isolation decision above. Bringing it up half-configured would produce a service that runs but cannot reflect — i.e. a non-functional stub, which the "no mock services" constraint forbids. Reported as a blocker instead.

HQ01 reachability

Not reachable (not deployed). HQ01 has no Honcho dependency wired today, and per mission scope none should be wired yet. When deployed, the integration point is an internal API URL (e.g. HONCHO_BASE_URL) added to HQ01's environment — a placeholder env var should be introduced only at integration time, not now.

Blockers

1. LLM provider API key for the deriver (not held).
2. Holdings-vs-Platform plane decision + isolation boundary (governance).
3. Postgres+pgvector provisioning + backup/restore ownership (Infrastructure).