Ownership is a person, not a Slack channel. Deputies, merge, and release roles stay yours.

Bindings

Warestack binds GitHub + Slack (and Linear when assigning issues) so DMs, owner escalation, and /warestack assign are attributable. Workspace admins manage readiness from People; each person can also confirm their own Slack link.

GitHub login ≠ Slack handle ≠ Linear display name. If Slack membership for a GitHub user is unclear, they are “confirm identity,” not a silent DM target.

Confirm your own binding with /warestack whoami. If Slack is missing, use /warestack link.

Repository owner

Each in-scope repository has an individual owner: a confirmed GitHub identity with a confirmed Slack binding. Review SLA can DM that person when a requested reviewer misses the clock.

A team as owner is useful for coverage and dashboards. It cannot receive a Slack DM. If you want owner escalation, name a person.

Personal digest

A personal digest is not a repository chain. It is one private, owner-only chain per member. An administrator cannot create or inspect another member’s digest. Each member must have linked GitHub and confirmed Slack, then enable it from Overview › Needs attention › Customize. See Digests.

No surprise DMs

Only confirmed identities. Only requested reviewers and named individual owners. Do not put someone on a review request, a digest, or an owner role unless they should receive that message.

Propose this when

You can name a GitHub login that actually reviewed or owned work in the last 14 days and you can confirm they exist in Slack. Otherwise owner Slack = unknown and Review SLA stays off for that hop.

Do not

• Map GitHub login to Slack handle by string equality.
• Propose a GitHub team as the repository owner for Review SLA.

Warestack identity evidence routes engineering work. Vanta remains responsible for HR, IdP, laptop, vendor, and other organizational controls.