Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 11 additions & 15 deletions docs/ACCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,22 +55,17 @@ Only once you're past local development.

| To do this | You need | Ask |
|---|---|---|
| Push a branch, open a PR | GitHub write on `qiuethan/Misty` | <!-- FILL IN: who administers the repo --> |
| Push a branch, open a PR | GitHub write on `UTMIST/Misty` | @qiuethan (step 1 of [`ONBOARDING.md`](ONBOARDING.md)) |
| Run a **real** Discord bot (not the playground) | Your own bot token + client id | Nobody — [make your own app](https://discord.com/developers/applications). See below |
| Test slash commands in a shared server | Invite to the testing guild + its `DISCORD_GUILD_ID` | <!-- FILL IN --> |
| Exercise `/chat` or live transcription | AWS creds with **Bedrock** and **Transcribe** enabled | <!-- FILL IN: is there a shared UTMIST AWS account, or does each dev use their own? --> |
| Send real verification email | A Resend API key, or Gmail service-account JSON | <!-- FILL IN --> — rarely needed; `EMAIL_BACKEND=fake` covers local work |
| View logs, restart, or set variables on a deploy | Railway project member | <!-- FILL IN --> |
| Inspect or branch a database | Neon project member | <!-- FILL IN --> |
| Merge to `main` (production release) | Approval per [`RAILWAY-DEPLOYMENT.md`](RAILWAY-DEPLOYMENT.md) | <!-- FILL IN: who signs off on a prod promotion --> |

> [!NOTE]
> The `FILL IN` markers above are honest gaps, not placeholders left by
> accident. This file was added during an onboarding sweep by someone who could
> verify the *technical* answers by running the code, but not the
> *organizational* ones. If you know who grants one of these, please fill it in
> — a name or a Discord channel is enough, and it's the highest-value edit
> anyone can make to this page.
| Test slash commands in a shared server | Invite to the testing guild + its `DISCORD_GUILD_ID` | @qiuethan — he'll invite you and give you the guild id |
| Exercise `/chat` or live transcription | AWS creds with **Bedrock** and **Transcribe** enabled | @qiuethan — there's a shared UTMIST AWS account, and he issues scoped IAM credentials per dev. Expect to need this if you own the `services/llm` or `services/meeting` zone |
| Send real verification email | A Resend API key, or Gmail service-account JSON | @qiuethan — rarely needed; `EMAIL_BACKEND=fake` covers local work |
| View logs, restart, or set variables on a deploy | Railway project member | @qiuethan — added on request; say what you're debugging |
| Inspect or branch a database | Neon project member | @qiuethan — added on request; say what you're debugging |
| Merge to `main` (production release) | Approval per [`RAILWAY-DEPLOYMENT.md`](RAILWAY-DEPLOYMENT.md) | @qiuethan signs off on every `staging → main` promotion |

Yes, every row says @qiuethan. That's the current reality of a small org, not
a policy — as zones get owners, expect some of these to delegate.

### Making your own Discord app

Expand Down Expand Up @@ -133,6 +128,7 @@ routine offboarding step.

## See also

- [`ONBOARDING.md`](ONBOARDING.md) — joining the team: zones, getting work, PR norms
- [`DEVELOPMENT.md`](DEVELOPMENT.md) — what each variable does, and local setup
- [`RAILWAY-DEPLOYMENT.md`](RAILWAY-DEPLOYMENT.md) — the deploy/operate runbook
- [`DEPLOYMENT-HISTORY.md`](DEPLOYMENT-HISTORY.md) — why key storage differs per service
Loading