HQ
HQ01
Intelligence

Artifacts

Browse the repository, read documents, and manage the governance folders. Source, runtime, and infrastructure are read-only.

Repository
CONSTITUTION_COMPLIANCE_AUDIT_V1.mdREADME.md
repositories/aaf-holdings/docs/infrastructure/serena.md
2.3 KB

Serena — Infrastructure Status

Classification: Real open-source software (Oraios) — a coding-agent toolkit exposed as an MCP server (LSP-backed symbol search / edit tools). Unlike Hermes/Honcho/MemPalace it is a developer tool, not part of the Knowledge OS intelligence triad.

Ground truth on the box

  • No serena process or installed CLI prior to this pass.
  • Added this pass: uv 0.11.21 + uvx at ~/.local/bin — the standard, user-space, reversible prerequisite Serena's documented launch method uses (pip3/pipx/uv were all previously absent). Verified: uv --version → uv 0.11.21.

Official launch method (NOT executed this pass — see blocker)

Serena is run on demand (no persistent daemon) via uvx, e.g.:

uvx --from git+https://github.com/oraios/serena serena start-mcp-server

It is then registered as an MCP server for an agent/IDE (including Claude Code) rather than reached over a fixed HTTP port.

Why it was not launched this pass

Resolving and executing code directly from an external git repository (oraios/serena) that I selected myself was correctly blocked by the permission layer: the user/canon never ratified that source as "the chosen method for this stack." The mission's own rule — install via the method already chosen for this stack — has no answer here, because no source has been ratified. Pulling and running arbitrary upstream code on a production box without that ratification would violate the spirit of the constraint, so it was not done.

HQ01 reachability

Not applicable in the usual sense — Serena is an MCP tool consumed by a coding agent, not an HTTP service HQ01 calls. uvx is now on PATH (under ~/.local/bin) so the launch command is available; the launch itself awaits ratification of the source/pin.

Blockers

  1. Ratify the Serena source + version pin (a specific tag/commit of oraios/serena, or a vendored mirror) as the approved install — then it can be launched and registered as an MCP server.
  2. Decide the consumer: which agent/IDE config registers Serena's MCP endpoint.

To finish (once source is ratified)

# pin to an approved ref instead of bare git+https
uvx --from git+https://github.com/oraios/serena@<approved-ref> serena --help
uvx --from git+https://github.com/oraios/serena@<approved-ref> serena start-mcp-server

root · /srv/aaf