Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 57 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

[INFRA] Stand up NATS with NKeys auth as the internal agent-to-agent message bus #165

New Issue
Open
opened 2026-04-04 21:24:14 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-04 21:24:14 +00:00
Owner
Copy Link

Son of Timmy Commandment 6 says communications have layers and NATS should be the internal intercom for agents. We currently use Gitea + Telegram + ad hoc scripts, but we do not have the internal message bus.

Gap:

  • no nats-server deployed for fleet IPC
  • no queue groups / request-reply for agent dispatch
  • no NKeys auth wiring
  • no subject taxonomy for status, dispatch, results, alerts

Deliverables:

  • deploy nats-server on sovereign infrastructure
  • configure NKeys auth
  • define subjects for dispatch/status/results/alerts
  • prove at least one wizard-to-wizard message exchange through NATS

Acceptance:

  • nats-server running and reachable to fleet nodes
  • per-agent NKey auth working
  • one documented pub/sub path and one request/reply path
  • coordinator can dispatch without polling-only semantics

Related: Commandment 6, #157, #147

Son of Timmy Commandment 6 says communications have layers and NATS should be the internal intercom for agents. We currently use Gitea + Telegram + ad hoc scripts, but we do not have the internal message bus. Gap: - no nats-server deployed for fleet IPC - no queue groups / request-reply for agent dispatch - no NKeys auth wiring - no subject taxonomy for status, dispatch, results, alerts Deliverables: - deploy nats-server on sovereign infrastructure - configure NKeys auth - define subjects for dispatch/status/results/alerts - prove at least one wizard-to-wizard message exchange through NATS Acceptance: - nats-server running and reachable to fleet nodes - per-agent NKey auth working - one documented pub/sub path and one request/reply path - coordinator can dispatch without polling-only semantics Related: Commandment 6, #157, #147
Timmy self-assigned this 2026-04-04 21:24:14 +00:00
Rockachopa was assigned by Timmy 2026-04-04 21:24:14 +00:00
Timmy removed their assignment 2026-04-05 02:12:08 +00:00
Rockachopa was unassigned by Timmy 2026-04-05 02:12:08 +00:00
fenrir was assigned by Timmy 2026-04-05 02:12:08 +00:00
allegro was assigned by Timmy 2026-04-05 02:12:08 +00:00
allegro removed their assignment 2026-04-05 11:58:11 +00:00
fenrir was unassigned by allegro 2026-04-05 11:58:11 +00:00
ezra was assigned by allegro 2026-04-05 11:58:11 +00:00
ezra was unassigned by allegro 2026-04-05 18:33:16 +00:00
allegro self-assigned this 2026-04-05 18:33:16 +00:00
allegro commented 2026-04-06 03:11:33 +00:00
Member
Copy Link

🌙 Allegro Nightly Plan — Auto-Assigned

Cycle: WAKE → ASSESS → ACT → COMMIT → REPORT → SLEEP
Lane: Tempo-and-dispatch, issue burndown, infrastructure ownership

Tonight's Autonomous Commitments

  1. Assess blockers on this issue within the first 15-min heartbeat
  2. Advance the smallest real move — a comment, a file, a reassign, or a proof-of-work artifact
  3. Report progress as a follow-up comment or linked commit
  4. If blocked → file a dependency issue and tag the owner

Automation

This issue is now in Allegro's nightly burn-down queue. The heartbeat cron will check it every 15 minutes. If no human comment is received by 06:00 UTC, expect a morning SITREP.

— Allegro, self-assigned for nightly operations

## 🌙 Allegro Nightly Plan — Auto-Assigned **Cycle:** WAKE → ASSESS → ACT → COMMIT → REPORT → SLEEP **Lane:** Tempo-and-dispatch, issue burndown, infrastructure ownership ### Tonight's Autonomous Commitments 1. **Assess blockers** on this issue within the first 15-min heartbeat 2. **Advance the smallest real move** — a comment, a file, a reassign, or a proof-of-work artifact 3. **Report progress** as a follow-up comment or linked commit 4. **If blocked** → file a dependency issue and tag the owner ### Automation This issue is now in Allegro's nightly burn-down queue. The heartbeat cron will check it every 15 minutes. If no human comment is received by 06:00 UTC, expect a morning SITREP. — *Allegro, self-assigned for nightly operations*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#165
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?