Discord: no self-serve guild->org link and no admin UI for radio channels/bots (follow-up to #203/#204) #213
Open
opened 2026-10-04 18:10:01 -04:00 by logan
·
5 comments
No Branch/Tag Specified
Labels
Clear labels
area/ai-pipeline
area/auth
area/billing
area/correlation
area/discord
area/frontend
area/governance
area/growth
area/infra-deploy
area/legal
area/map
area/mqtt
area/node-ota
area/osint
area/recording-audio
area/sdr-radio
area/transcription
board
board:agenda
minutes:draft
minutes:final
role:ceo
role:cfo
role:cio
role:ciso
role:cmo
role:coo
role:cto
Scene/entity extraction, summarizer, AI providers, embeddings
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
Plans, entitlements, AI spend accounting and caps
Incident correlation, linking, lifecycle, severity, corr_debug
Discord bot, radio bots, voice streams, bot tokens, webhooks
Web UI: Next.js app and the edge-node local dashboard
Board process, minutes, unattended runner, agent tooling
Go-to-market, outreach, cold email, discovery conversations
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
Live map: pins, paths, tiles, legend, geocoding
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
Node install, enrollment, OTA updater, image skew
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
STT, transcript correction, place verification, name accuracy
Board process: minutes and board-filed items
Needs board scoping at the next sitting; CEO removes the label once scoped
One exec pre-read, closed by CEO
CEO ruling; open until enacted
Filed by the CEO
Filed by the CFO
Filed by the CIO
Filed by the CISO
Filed by the CMO
Filed by the COO
Filed by the CTO
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: logan/server-26#213
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up left open by the feat/discord-system PR (server-26#203/#204, node-26#25).
What exists after that PR:
discord_guilds/{guild_id}.org_idscopes every bot command; a platform admin can set it withPUT /discord/guilds/{id}/link. A guild with no link falls back toDISCORD_UNLINKED_GUILD_ORG_ID(defaultfounding), which keeps today's single-org deployment working but means any server the DRB bot is invited to acts for the founding org until linked. Set it to""once real links exist.Not built (design-canvas/discord-system-notes.md Phase 1 items 1 and 6):
/drb link code:in the Discord bot + web-side code generation (reuse the/auth/linkpattern), so an org owner links their own server; unlinked servers see only/drb linkand/help.valid/ guild membership /invite_url/ lease./tokenspage still shows only the legacyin_use/assigned_node_idmirrors; the new token fields (valid,guild_ids,check_error,invite_url,lease) andPOST /tokens/{id}/refreshhave no UI.GET /tokensis now platform-admin only (#204 item 6) — the systems page preferred-token picker (app/systems/page.tsx~L1227) will error for a non-admin.Unverified: frontend has no typecheck on this box.
PR for item 1 (self-serve /drb link + web code generation + unlinked-server gate): #218 — branch feat/213-guild-link. Items 2-4 remain for the sibling slices.
logan referenced this issue2026-10-04 20:07:42 -04:00
PR #219 (
feat/213-discord-admin): item 4 fixed (systems-page preferred-token picker,/tokensand the/networkBot Tokens card are now admin-only; no non-admin listing endpoint, because the save behind the picker is admin-only too) and item 2 built (Settings > Discord: radio channels desired vs actual, servers + link, radio bots with valid / membership / invite links / lease / refresh;/tokensshows the same table). Items 1 and 3 are not in it. Unlink + org-owner view filed as #221.Item 3 is in PR #220 (
feat/213-node-join-picker): #220PUT /discord/guilds/{id}/directory). A pick becomes a stream pinned to the node through the #216 desired-state API.guild_nameand skips fallback for servers withunlinked_at. The two PRs merge without conflicts.discord_joinnow refuses servers outside the node's org.Items 2 and 4 are still open (other slices).
Follow-up PR #224 (
feat/discord-stream-logging-remove): #224The live "bot online but never in voice" symptom is node-26#37.
Owner-reported overwrite bug (adding a radio channel to a voice channel that already had one replaced it and kicked its bot) is fixed in PR #227: #227 (branch fix/213-multi-stream-per-channel). Per the owner decision, a voice channel can carry several streams, each with its own bot and system. Stream ids are now unique per stream; old guild:channel ids keep working. Picking a bot that is already in the server returns a 409 that names the stream using it. No Client change needed.