Skip to content

Declare the inbound Slack events endpoint on the capability ratchet #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
satvikOS merged 1 commit into from
Aug 21, 2026
Merged

Declare the inbound Slack events endpoint on the capability ratchet #132

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions apps/web/src/lib/capability-registry/surfaces.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,8 @@ export const API_PENDING_BINDING: Readonly<Record<string, string>> = {
"/api/auth/[...nextauth]":
"sign-in transport — a capability gate here would make a tenant unable to authenticate its way to being told why",
"/api/health": "load-balancer health check — has no tenant and no session",
"/api/integrations/slack/events":
"inbound webhook — Slack is the caller and the signature over the raw bytes is the authentication, so there is no session; and one delivery resolves through teamId to every institution that connected that workspace, so there is no single tenant to ask about",
"/api/jobs/reminders": "scheduled job — runs for every institution at once, with no tenant asking",
"/api/notifications": "per-user shell, like /notifications — not per-tenant-capability",
"/api/org-image/[orgId]": "image bytes for the club spine",
Expand Down
Loading