Skip to content

DISCORD.md

Latest commit

 

History

History
30 lines (20 loc) · 1.62 KB

DISCORD.md

File metadata and controls

30 lines (20 loc) · 1.62 KB
Raw
Herald

Herald — Discord Channel Setup Guide

Field Value
Status PLANNED — HRD-NNN (later iteration)
Spec ref V3 §11 (later iteration)
Env vars (reserved) HERALD_DISCORD_BOT_TOKEN, HERALD_DISCORD_GUILD_ID, HERALD_DISCORD_CHANNEL_ID
Code (not yet implemented)

Discord is reserved for a later iteration. Uses Bot accounts on the Discord Developer Portal; per-server (guild) installation required.

This guide is a placeholder. When the Discord adapter lands as an HRD, this file will expand to the same step-by-step structure as TELEGRAM.md: obtain credentials → set env vars → verify HealthCheck → verify Send → optional Subscribe → troubleshooting.

What you can do now

  • Reserve the env-var names in your .env (commented out, per ../OPERATOR_CREDENTIALS.md).
  • Watch the HRD for status updates — it will move from open to code complete; awaiting live evidence to Fixed over its implementation lifecycle.
  • If you have an urgent need for the Discord channel, open an issue against the HRD asking for priority — operator-driven escalation is honored per the constitution.

Related

  • OPERATOR_CREDENTIALS.md — the umbrella credentials guide with reserved env-var blocks for every planned channel
  • TELEGRAM.md — the canonical live-channel guide shape (this file will mirror that structure when Discord lands)
  • Spec: V3 §11 (later iteration)