feat(email): automated-alert triage + thread-drill rules#157
Merged
Conversation
Ports three accumulated instance rules into phases/connectors/email.md (de-personalized — examples dropped, rules generalized): - Automated-Alert Triage: credential/token-expiry, quota/spend-threshold, usage, billing, and maintenance alerts are 🟢 Watching by default; promoted only on imminent functional impact, never on "action required"/"expiring" tone. - Drill Active Threads — Don't Trust the Snippet: a search snippet previews one (often not the latest) message; fetch the full thread (get_thread) before asserting "no reply"/"awaiting X"/"unanswered"; threads tied to an open item are mandatory drills. Both land in the inbound-scan section (mode: [consolidation, briefing]) — verified they assemble into SKILL only, not DREAMING/RESEARCH. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 23, 2026
Merged
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
1 participant
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.
First PR in the de-personalized Patterns batch — upstreaming accumulated instance rules into the engine phases (Phase-1 work for the connector-based migration, #156).
What
Two rules added to
phases/connectors/email.mdinbound-scan:Both rules are generic; the originating examples (which named a customer, colleagues, and personal threads) were dropped. Verified they assemble into SKILL only, not DREAMING/RESEARCH.
The email phase declares
requires: email, but vault configs enable this connector under the keygmail(the value detection emits) — soselect_sectionsdrops the entire email phase from the assembledSKILL.md. Now confirmed, not just suspected: a live vault's deployedSKILL.mdhas 0 occurrences of every email-phase marker. Consequence: the rules in this PR don't take effect until the key mismatch is reconciled. This predates this PR and is filed separately as #172 (with fix options + a pointer to fold it into the connector-catalog work, #152) — flagging, not fixing here.🤖 Generated with Claude Code