feat(incident-response,github): route self-detected prod outages and clarify bot self-approval restriction - #212
Closed
dembrane-sam-bot wants to merge 1 commit into
Closed
Conversation
…clarify bot self-approval restriction
dembrane-sam-bot
enabled auto-merge
August 3, 2026 05:10
Member
auto-merge was automatically disabled
August 9, 2026 14:59
Pull request was closed
spashii
added a commit
that referenced
this pull request
Aug 9, 2026
…evidence store (supersedes #176, #212, #216) (#226) Folds three sam-authored PRs into one, each reworked and verified against Robert Trinh's current ISMS setup (checked in #team-trust / #gen-trust, post-external-audit 2026-08-05). - **incident-response (#212):** self-detected production outages (crashlooping pods, `ImagePullBackOff`, dead prod agents, a deploy that disables a feature) are availability incidents — classify, escalate to the IR Team immediately, open an Incidents row and a `blocker` Linear issue, do not batch into daily-maintenance. Motivated by the echo-prod agent pods being dead from 1 Aug and under-escalated. - **incident-response (#216):** the Evidence Register is **Tidal / Issues**, replacing the stale 'Tally Dashboard'. Verified: TidalControl (`portal.tidalcontrol.com/dembrane`) is Robert's authoritative ISMS store for evidence and action plans; the incident intake **form** is the Notion form he migrated from Tally after the audit (already reflected in the skill). #216 as originally written fixed the right line — this keeps that and adds the TidalControl context so the two never drift again. - **github.md (#212):** Sam cannot self-approve its own bot's PRs — GitHub blocks it, so a Sam-authored PR always waits on a human review. - **support-request-triage (#176):** include a deep-linked dashboard URL when a finding points at a specific conversation, as a Slack `<url|label>`, never a bare UUID (respecting the existing PII rule). Verified against Robert's messages; eval suite 47 pass. Supersedes #176, #212, #216 — recommend closing them. ### Tier Tier 1 (capability + recipe skills).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this change?
This PR modifies:
src/recipes/isms-automations/skills/incident-response/skill.md: Explicitly routes self-detected production outages (e.g.ImagePullBackOffor crashlooping pods disabling services) as active availability/ops incidents under the ISMS framework, requiring immediate escalation and Linear blocker creation instead of batching.src/capabilities/github.md: Clarifies that Sam's bot cannot self-approve its own PRs on GitHub due to platform constraints.What was noticed?
echo-prodagent pods have been completely dead since August 1st (ImagePullBackOff on non-existent image reference). Because ourincident-responseskill lacked operational availability outage routing, the outage was under-escalated.Tier
Tier 1 (prose skills and capabilities).
Confidence
5/5 — extremely confident as this codifies our operational routing and avoids silent under-escalations of critical service failures.