Skip to content

Land 113-node Hermes digest — production still 31-node; feat branch has PLACEHOLDER_WILL_FAIL #16

Description

@manutej

Adversarial verdict (2026-09-06)

The ingest is not comprehensive and is not reflected in the live lattice.

Production (what the preview actually serves)

  • https://stalks-and-sections.vercel.app/?g=hermes-agent
  • docs/examples/hermes-agent.json on main SHA 247340f5 = 31 nodes / 29 edges / 2423 files
  • Deep link hydrates, intro skipped, 4 layers, 0 LCEL titles — but the waist is the old compact ids (prompt-builder, session-db, profile-isolation)

Feature branch hazard

  • feat/hermes-94-land @ 0ac2509 overwrote docs/examples/hermes-agent.json with the literal string PLACEHOLDER_WILL_FAIL
  • Do not merge that branch until the blob is a real SheafGraph

What a complete ingest would mean

Live NousResearch/hermes-agent@df4c786: 3387 eligible py/md files.

  • agent/ 204 py — architecture.md says the loop lives in conversation_loop.py + turn_*.py
  • hermes_cli/ 455 py
  • tools/ 283
  • plugins/platforms 22 adapters
  • 21 hermes_state_* siblings

A 1:1 AST exceeds the 120-node playable cap. The correct artifact is a hierarchical pool.

Candidate ready locally (not on GitHub)

113 nodes / 112 edges / dim 12 / 8 pinned L0 / 10 terracotta.
Adds: agent-turn-pool, display, trajectory, model_metadata, compression_facade, state fts/wal/gateway/compression, commands/setup/doctor/models, gateway-hooks, web_tools, code_exec, process_registry, platforms long-tail, bootstrap.

Honest remaining pools: hermes_cli mixins, agent billing/credential siblings, evals/docker/nix.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions