You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The accounts, keys and Discord application Prompter needs that belong to Cratis rather than to a person. Full walkthrough with every click: Planning/ORG_SETUP.md.
About 30 minutes for steps 1–3, and nothing else can start until they exist.
1 · Voyage API key — dash.voyageai.com, signed in as Cratis. Free tier; unblocks indexing the docs
2 · Anthropic API key — console.anthropic.com on the Cratis org. If your plan has Workspaces, make one for Prompter with a monthly cap
3a · A Discord Team named Cratis, with Sindre added
3b · The application created inside that Team (not "Personal")
3c · Bot tab — Public Bot off, Message Content Intent on, copy the token
3d · Permissions — exactly: View Channels, Send Messages, Send Messages in Threads, Create Public Threads, Embed Links, Read Message History
3e · A private test server, bot installed, one text channel and one forum channel, ids copied
5 · Hand over the two keys, the bot token and the two channel ids through the password manager
Why this is an owner's job rather than anyone's
Durability, not process. An API key on a personal card and a Discord app owned by an individual account are both single points of failure: the day that account is unavailable, the bot cannot be recovered and its token cannot be rotated by anyone else. Hence two rules — keys on the org account, and the Discord application inside a Team that can have several owners.
The permission list is also deliberately six items long. A documentation bot that can manage a server is a bad trade for nobody's benefit; if the generated invite URL asks for more, something was ticked by accident.
Later, not now
PULUMI_CONFIG_PASSPHRASE and UPCLOUD_TOKEN (stage B1), the DNS record (B3), and the issue-filing token (C2) are all listed in the same document against the stage that needs them. They can wait.
The accounts, keys and Discord application Prompter needs that belong to Cratis rather than to a person. Full walkthrough with every click:
Planning/ORG_SETUP.md.About 30 minutes for steps 1–3, and nothing else can start until they exist.
Why this is an owner's job rather than anyone's
Durability, not process. An API key on a personal card and a Discord app owned by an individual account are both single points of failure: the day that account is unavailable, the bot cannot be recovered and its token cannot be rotated by anyone else. Hence two rules — keys on the org account, and the Discord application inside a Team that can have several owners.
The permission list is also deliberately six items long. A documentation bot that can manage a server is a bad trade for nobody's benefit; if the generated invite URL asks for more, something was ticked by accident.
Later, not now
PULUMI_CONFIG_PASSPHRASEandUPCLOUD_TOKEN(stage B1), the DNS record (B3), and the issue-filing token (C2) are all listed in the same document against the stage that needs them. They can wait.Unblocks #6.