Skip to content

spec(automation/agent-hive-group): v1 -- agents' hive routing (Closes #6429) - #6430

Merged
gHashTag merged 1 commit into
masterfrom
claude/agent-hive-group
Oct 5, 2026
Merged

gHashTag merged 1 commit into
masterfrom
claude/agent-hive-group

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Closes #6429

Spec of record for the agents' hive in 999-multibots-telegraf (one managed bot per catalogue agent, one forum group).

  • addressed: a person calls an agent by tag, @ALL, reply or its own topic; a bot only by tag or reply.
  • may_answer: bot-to-bot chain closes at MAX_BOT_DEPTH=3, cooldown 5000 ms.
  • claim_fresh: a creation claim lives 15 min.

t27c test-report: 7/7 pass. Negative controls on a copy: depth <= MAX -> 2 FAIL; dropping !from_bot -> 1 FAIL.

🤖 Generated with Claude Code

…ive, the bot chain limit and the cooldown (Closes #6429)

phi^2 + 1/phi^2 = 3 | TRINITY
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-05 13:19:31 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 40
PRs with All Checks Green 10
READY 9
FAILING 40
PENDING 0
NO CHECKS YET 0

These columns do not partition: 9 + 40 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8597b6ded596 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag

gHashTag commented Oct 5, 2026

Copy link
Copy Markdown
Owner Author

bee-reviewed

Reviewer bee verdict: approve and merge. Head 76af335.

  • Files: only specs/automation/agent-hive-group.t27 and its seal .trinity/seals/automation_automation::agent_hive_group.json.
  • Seal holds: spec_hash sha256:4e984e09…d75a equals the spec's sha256; neither gate lists this seal as stale or drifted.
  • Host copy: byte-identical with 999-multibots-telegraf origin/main:src/spec/agent-hive-group.t27 (queen-3516: bee work for #3516 #3636), same sha256 4e984e09…d75a.
  • Spec: tests match the functions (addressed bot cannot use @ALL or own-topic; chain_open depth < 3; cooled >= 5000 ms; claim_fresh < 900000 ms; person always answered).
  • Red checks are pre-existing and unrelated:
    • coverage (Seal Coverage, run 37315888511): "3 seal(s) newly do not hold" = kanban_card_chat.json, runtime-process.json, runtime_runtime-process.json [stale].
    • spec-guards (Spec Guards, run 37315888436): STALE gen hashes for the same 3 seals (kanban-card-chat.t27, runtime/process.t27).
    • master shows the same failure: Seal Coverage run 37330659669 and Spec Guards run 37332744939 list the same three seals. Both workflows have been red on master all day (c82953e, 11f5e6a, 36ad787, 682564f…). The fix is in fix(seals): re-seal runtime/process and kanban-card-chat (Closes #6256) #6257.
  • 23 other checks pass.

@gHashTag
gHashTag merged commit 2d5cdfd into master Oct 5, 2026
23 of 25 checks passed
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.

spec(automation/agent-hive-group): agents' hive in Telegram -- bot per agent, bot chain limit

1 participant