Skip to content

fix(distill): unify Honcho distill author peer to family-assistant#327

Merged
seoseo-ai merged 1 commit into
mainfrom
honcho-distill-peer-unify-family-assistant
Jul 8, 2026
Merged

fix(distill): unify Honcho distill author peer to family-assistant#327
seoseo-ai merged 1 commit into
mainfrom
honcho-distill-peer-unify-family-assistant

Conversation

@jinon86

@jinon86 jinon86 commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

What

Unify the Honcho distill author peer to a single, harness-neutral identity: family-assistant.

Why (root cause — verified live 2026-07-08)

Scanned 326 sessions / 4,137 messages in the seoyoon-family workspace. Distill messages (source=claude-code-distill) were scattered across 4 author peers:

author peer distill msgs
hermes 50
soonwook 42
dungae 34
nosuk 18

Only 35% landed on hermes. Root cause is a config-schema drift: the seed template supplies peerName=<NODE_NAME> (used for recall), but the distill hooks read a separate aiPeer field and fall through to a hardcoded "dungae" default when it's absent. Nodes seeded at different times diverged.

Change (distill-only scope)

  • honcho-push.sh / queue-drain.sh: fallback "dungae""family-assistant" (drift safety net).
  • honcho.template.json: add "aiPeer": "family-assistant" so freshly seeded nodes converge on one shared AI author peer. peerName (recall axis) unchanged.

Design decision

Design A — single shared AI peer, harness-neutral name. Forward-only cutover (Honcho SDK has no peer rename/merge/message-move; existing history stays under old peers by design — "분절 수용"). Operator-approved.

Evidence

  • Tests: honcho-push.test.sh PASS=17/0, queue-drain.test.sh PASS=16/0.
  • jq template validation OK; bash -n OK on both hooks.

Follow-up (not in this PR)

Per-node ~/.hermes/honcho.json gets explicit aiPeer=family-assistant via A2A fan-out (11 nodes), plus canary validation on gwakga.

🤖 Generated with Claude Code

Distill messages were scattered across 4 author peers (hermes/dungae/
soonwook/nosuk) because the seed template supplies peerName=<NODE_NAME>
while the distill hooks read aiPeer, falling through to a hardcoded
"dungae" default. Verified live: 144 distill msgs, only 50 under hermes.

- honcho-push.sh / queue-drain.sh: fallback "dungae" -> "family-assistant"
- honcho.template.json: add "aiPeer":"family-assistant" so freshly
  seeded nodes converge on one shared AI author peer.

Design A (single shared AI peer, harness-neutral name); forward-only
cutover (Honcho has no peer rename/merge). distill-only scope; recall
peerName unchanged. Operator-approved 2026-07-08.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jinon86 jinon86 requested a review from seoseo-ai as a code owner July 8, 2026 07:36

@seoseo-ai seoseo-ai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI all green (7/7: codeql, harness-ci validate/lint/secret-scan, bridge-tests 3.11/3.12); mergeable. Distill-only scope, tests pass (honcho-push 17/0, queue-drain 16/0), operator-approved design per PR body. Auto-approved per PR-first policy (jinon86 author needs seoseo-ai reviewer).

@seoseo-ai seoseo-ai merged commit 1c7d251 into main Jul 8, 2026
7 checks passed
@seoseo-ai seoseo-ai deleted the honcho-distill-peer-unify-family-assistant branch July 8, 2026 07:42
seoseo-ai pushed a commit that referenced this pull request Jul 8, 2026
…er guard (#328)

Fleet rollout tooling for unifying the distill author peer to
family-assistant (follow-up to #327).

- scripts/converge-distill-peer.sh: idempotent node-local helper. --check
  reports the resolved aiPeer, --apply rewrites an explicit override
  (flat .aiPeer or nested .hosts.hermes.aiPeer) to family-assistant with a
  backup, --verify posts a labelled canary and confirms the author peer.
  Nodes with no explicit override converge via the #327 fallback alone.

- honcho-push.sh / queue-drain.sh: treat an unfilled seed placeholder
  baseUrl (e.g. "<HONCHO_BASE_URL>") as unconfigured so a freshly seeded
  honcho.json cleanly no-ops instead of failing /health and queuing junk.

Tests: honcho-push 17/0, queue-drain 16/0. Convergence helper validated
across flat/nested schema, idempotent re-run, and placeholder cases.

Co-authored-by: jinon86 <247078695+jinon86@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants