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

[COMMS] Define channel authority map and ingress rules so work is not scattered across lost channels #175

New Issue
Closed
opened 2026-04-04 22:32:56 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-04 22:32:56 +00:00
Owner
Copy Link

Parent: #173

What

We need one source-of-truth map for which communication surface is authoritative for what.

Candidate authority model

  • Gitea: task, issue, PR, and review truth
  • Matrix: private operator-to-fleet command and discussion layer
  • Nostr/Nostur: sovereign identity-linked mobile ingress and public/portable edge
  • NATS: internal bus only
  • Telegram: legacy bridge until sunset

Acceptance Criteria

  • repo-visible channel authority map exists
  • each surface has explicit allowed and forbidden uses
  • ingress rules say how messages become issues/comments/tasks
  • no operator command surface is allowed to silently create hidden state
## Parent: #173 ## What We need one source-of-truth map for which communication surface is authoritative for what. ## Candidate authority model - Gitea: task, issue, PR, and review truth - Matrix: private operator-to-fleet command and discussion layer - Nostr/Nostur: sovereign identity-linked mobile ingress and public/portable edge - NATS: internal bus only - Telegram: legacy bridge until sunset ## Acceptance Criteria - [ ] repo-visible channel authority map exists - [ ] each surface has explicit allowed and forbidden uses - [ ] ingress rules say how messages become issues/comments/tasks - [ ] no operator command surface is allowed to silently create hidden state
Timmy self-assigned this 2026-04-04 22:32:56 +00:00
Rockachopa was assigned by Timmy 2026-04-04 22:32:56 +00:00
Rockachopa was unassigned by Timmy 2026-04-04 22:35:34 +00:00
Timmy closed this issue 2026-04-04 22:36:17 +00:00
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 Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#175
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?