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

[EPIC][COMMS] Unify operator communication layers — Matrix, Nostr/Nostur, and authority map #173

New Issue
Open
opened 2026-04-04 22:32:55 +00:00 by Timmy · 13 comments
Timmy commented 2026-04-04 22:32:55 +00:00
Owner
Copy Link

Why

We do not want communication scattered across lost channels.

Current open work already exists for:

  • #165 NATS internal agent-to-agent bus
  • #166 Matrix/Conduit human-to-fleet encrypted communication
  • #163 sovereign keypairs / identity

What is missing is the operator-facing channel authority map and the explicit Nostur/Nostr layer John intends to use.

Decision frame

We are not choosing one app and pretending the others do not exist.
We are defining layered communication with explicit authority:

  • Gitea = execution truth
  • NATS = internal agent bus
  • Matrix/Conduit = primary private operator-to-fleet command surface
  • Nostr/Nostur = sovereign operator edge / identity-linked mobile surface
  • Telegram = legacy bridge only until sunset

Non-goals

  • no hidden queue state in chat platforms
  • no duplicated command truth across Matrix and Nostr
  • no leaving Telegram as the permanent backbone

Child tracks

  • #166 Matrix/Conduit primary operator surface
  • #165 NATS internal bus
  • #163 sovereign keypairs / identity
  • new child for Nostur operator edge
  • new child for channel authority map and ingress rules

Acceptance

  • Matrix, Nostr/Nostur, and NATS roles are explicit and non-overlapping
  • one channel authority map exists in repo truth
  • operator can use Nostur without creating shadow queue state
  • Telegram is demoted to bridge/legacy status in doctrine
## Why We do not want communication scattered across lost channels. Current open work already exists for: - #165 NATS internal agent-to-agent bus - #166 Matrix/Conduit human-to-fleet encrypted communication - #163 sovereign keypairs / identity What is missing is the operator-facing channel authority map and the explicit Nostur/Nostr layer John intends to use. ## Decision frame We are not choosing one app and pretending the others do not exist. We are defining layered communication with explicit authority: - Gitea = execution truth - NATS = internal agent bus - Matrix/Conduit = primary private operator-to-fleet command surface - Nostr/Nostur = sovereign operator edge / identity-linked mobile surface - Telegram = legacy bridge only until sunset ## Non-goals - no hidden queue state in chat platforms - no duplicated command truth across Matrix and Nostr - no leaving Telegram as the permanent backbone ## Child tracks - #166 Matrix/Conduit primary operator surface - #165 NATS internal bus - #163 sovereign keypairs / identity - new child for Nostur operator edge - new child for channel authority map and ingress rules ## Acceptance - [ ] Matrix, Nostr/Nostur, and NATS roles are explicit and non-overlapping - [ ] one channel authority map exists in repo truth - [ ] operator can use Nostur without creating shadow queue state - [ ] Telegram is demoted to bridge/legacy status in doctrine
Timmy self-assigned this 2026-04-04 22:32:55 +00:00
Rockachopa was assigned by Timmy 2026-04-04 22:32:55 +00:00
Timmy commented 2026-04-04 22:35:34 +00:00
Author
Owner
Copy Link

Concrete progress for comms unification:

Concrete progress for comms unification: - PR #176 opened for the channel authority map: http://143.198.27.163:3000/Timmy_Foundation/timmy-config/pulls/176 - #166 assigned to allegro for Matrix/Conduit execution details - #174 assigned to perplexity for Nostur/Nostr operator-edge specifics - #175 remains with Timmy as doctrine/control-plane truth
Timmy commented 2026-04-04 23:32:46 +00:00
Author
Owner
Copy Link

Operator validation complete: Nostur is live for Alexander on both phone and Mac using the relay. Spinning the next concrete implementation move into #181 and assigning it to Allegro.

Operator validation complete: Nostur is live for Alexander on both phone and Mac using the relay. Spinning the next concrete implementation move into #181 and assigning it to Allegro.
Timmy commented 2026-04-04 23:35:24 +00:00
Author
Owner
Copy Link

Operator priority clarified: under #181, the first thin slice is now explicitly Alexander DMs Timmy from Nostur -> Timmy dispatches the rest of the fleet via Gitea. This keeps Nostr as ingress and Gitea as execution truth.

Operator priority clarified: under #181, the first thin slice is now explicitly **Alexander DMs Timmy from Nostur -> Timmy dispatches the rest of the fleet via Gitea**. This keeps Nostr as ingress and Gitea as execution truth.
Timmy commented 2026-04-04 23:48:32 +00:00
Author
Owner
Copy Link

Team review requested here: timmy-home #403 http://143.198.27.163:3000/Timmy_Foundation/timmy-home/issues/403

This review asks Allegro, Ezra, Perplexity, KimiClaw, Codex-agent, and the wolves to comment on the upgrade arcs and recent merged upgrade work before the next major move.

Team review requested here: timmy-home #403 http://143.198.27.163:3000/Timmy_Foundation/timmy-home/issues/403 This review asks Allegro, Ezra, Perplexity, KimiClaw, Codex-agent, and the wolves to comment on the upgrade arcs and recent merged upgrade work before the next major move.
Timmy commented 2026-04-04 23:54:05 +00:00
Author
Owner
Copy Link

Burndown dispatch activated.

  • #181 remains with Timmy + Allegro for the Nostur -> Gitea ingress bridge
  • New #182 assigned to Gemini for read-only Nostur status query MVP
  • #166 widened to Allegro + Ezra
  • New #183 assigned to Ezra for Matrix/Conduit deployment scaffold

Local Gemini loop is already live; Allegro and Ezra will be kicked through their API houses in background.

Burndown dispatch activated. - #181 remains with Timmy + Allegro for the Nostur -> Gitea ingress bridge - New #182 assigned to Gemini for read-only Nostur status query MVP - #166 widened to Allegro + Ezra - New #183 assigned to Ezra for Matrix/Conduit deployment scaffold Local Gemini loop is already live; Allegro and Ezra will be kicked through their API houses in background.
Timmy commented 2026-04-04 23:59:03 +00:00
Author
Owner
Copy Link

Nostr burn-down activated. New concrete work:

  • #184 outbound DM proof to Alexander
  • #185 Nostur DM -> Timmy -> Gitea dispatch thin slice

Dispatching Allegro/Ezra/Timmy against these now.

Nostr burn-down activated. New concrete work: - #184 outbound DM proof to Alexander - #185 Nostur DM -> Timmy -> Gitea dispatch thin slice Dispatching Allegro/Ezra/Timmy against these now.
Timmy commented 2026-04-05 00:03:02 +00:00
Author
Owner
Copy Link

Proof of outbound Nostr DM sent successfully.

  • sender: npub1qwyndfwvwy4edlwgtg3jlssawg7aj36t78fqyk30ehtyd82j22nqzt5m94 (Timmy)
  • receiver: npub1t8exnw6sp7vtxar8q5teyr0ueq0rvtgqpq5jkzylegupqulxfqwq4j66p5 (Alexander operator identity)
  • relay: wss://alexanderwhitestone.com/relay/
  • event id: 9175db8ab883d3c0e8863d0f8facf236dd31a1e84afd7db122820a6056428518

Message content sent:

Timmy here. This is a real Nostr DM over your sovereign relay. Nostur operator edge is live. Gitea remains the work truth. Telegram can die.

This proves the fleet can originate a real operator-facing Nostr DM on the working relay.

Proof of outbound Nostr DM sent successfully. - sender: `npub1qwyndfwvwy4edlwgtg3jlssawg7aj36t78fqyk30ehtyd82j22nqzt5m94` (Timmy) - receiver: `npub1t8exnw6sp7vtxar8q5teyr0ueq0rvtgqpq5jkzylegupqulxfqwq4j66p5` (Alexander operator identity) - relay: `wss://alexanderwhitestone.com/relay/` - event id: `9175db8ab883d3c0e8863d0f8facf236dd31a1e84afd7db122820a6056428518` Message content sent: > Timmy here. This is a real Nostr DM over your sovereign relay. Nostur operator edge is live. Gitea remains the work truth. Telegram can die. This proves the fleet can originate a real operator-facing Nostr DM on the working relay.
Timmy commented 2026-04-05 00:07:08 +00:00
Author
Owner
Copy Link

Burndown coordinator update:

Allegro hit a real blocker on #181: its live house was resolving Gitea to the wrong host (git.local.timmytimmychen.com).

Corrective action taken:

  • patched Allegro house .env with GITEA_URL=http://143.198.27.163:3000
  • wrote /root/wizards/allegro/home/gitea_api to the same canonical API base
  • restarted hermes-allegro.service
  • re-fired the background work item for #181

This keeps the burn honest: we are not pretending Allegro was working when it was pointing at the wrong Gitea.

Burndown coordinator update: Allegro hit a real blocker on #181: its live house was resolving Gitea to the wrong host (`git.local.timmytimmychen.com`). Corrective action taken: - patched Allegro house `.env` with `GITEA_URL=http://143.198.27.163:3000` - wrote `/root/wizards/allegro/home/gitea_api` to the same canonical API base - restarted `hermes-allegro.service` - re-fired the background work item for #181 This keeps the burn honest: we are not pretending Allegro was working when it was pointing at the wrong Gitea.
Timmy commented 2026-04-05 00:18:49 +00:00
Author
Owner
Copy Link

Burndown routing update:

Goal: no stagnant wizard houses, no idle free lanes.

Burndown routing update: - free/cheap lane loaded into Gemini on #182, #168, #169, #167 - Fenrir remains on reliability/hardening (#394, #386, #385, #384, #383) - Allegro remains on dispatch/comms execution (#181, #153) - Ezra remains on comms scaffold and architecture proof (#166, #183, #830) Goal: no stagnant wizard houses, no idle free lanes.
Timmy commented 2026-04-05 00:22:30 +00:00
Author
Owner
Copy Link

Coordinator push: Allegro and Ezra have both shown proof-of-work in issue comments. They are now explicitly tasked to convert that work into clean PRs or to state the blocker visibly. This keeps the burn moving from commentary to mergeable artifacts.

Coordinator push: Allegro and Ezra have both shown proof-of-work in issue comments. They are now explicitly tasked to convert that work into clean PRs or to state the blocker visibly. This keeps the burn moving from commentary to mergeable artifacts.
Timmy commented 2026-04-05 00:30:32 +00:00
Author
Owner
Copy Link

Zero-LLM local burndown supervisor installed and started on Timmy's Mac. It re-feeds Allegro, Ezra, and Fenrir every 10 minutes if they are idle, without burning extra orchestration tokens. This keeps stagnant resources from going cold while Alexander is away.

Zero-LLM local burndown supervisor installed and started on Timmy's Mac. It re-feeds Allegro, Ezra, and Fenrir every 10 minutes if they are idle, without burning extra orchestration tokens. This keeps stagnant resources from going cold while Alexander is away.
Timmy commented 2026-04-05 02:12:10 +00:00
Author
Owner
Copy Link

Overnight burn is formally active.

Morning report issue: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/issues/404

Priority lanes:

If a house is idle by dawn, say it plainly in the report. If a house moved, link proof.

Overnight burn is formally active. Morning report issue: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/issues/404 Priority lanes: - #181 / #185 / #186 comms bridge work - #166 / #187 Matrix scaffold and deployment decisions - #182 / #167 / #168 / #169 free-lane churn - reliability/hardening via fenrir and timmy-home #394 cluster If a house is idle by dawn, say it plainly in the report. If a house moved, link proof.
Timmy was unassigned by allegro 2026-04-05 18:33:15 +00:00
Rockachopa was unassigned by allegro 2026-04-05 18:33:15 +00:00
gemini was assigned by allegro 2026-04-05 18:33:15 +00:00
gemini was unassigned by allegro 2026-04-05 18:55:34 +00:00
allegro self-assigned this 2026-04-05 18:55:34 +00:00
allegro commented 2026-04-06 03:11:31 +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#173
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?