Skip to content

docs(may-agent): 90-risk-log — 7 risks with severity matrix, mitigations, and escalation triggers - #21

Merged
Fearvox merged 7 commits into
mainfrom
sleep-iter-16-risk-log
May 20, 2026
Merged

Fearvox merged 7 commits into
mainfrom
sleep-iter-16-risk-log

Conversation

@Fearvox

@Fearvox Fearvox commented May 13, 2026

Copy link
Copy Markdown
Owner

Summary

  • 7 risks identified across cultural, technical, organizational, and deadline dimensions
  • Each risk has severity, likelihood, owner, status, detailed mitigation steps, and escalation triggers
  • Risk heatmap and weekly review cadence (W1 May 13-17 through W3 May 25-31)
  • Covers: Rust team buy-in, Hermes upstream churn, 邓Sir bandwidth, Python GIL, cross-platform sandbox, May 31 deadline, Hermes community reaction

Test plan

  • All risks have mitigation steps
  • All risks have escalation triggers
  • Heatmap correctly maps severity/likelihood
  • Weekly cadence aligns with May 31 deadline

🤖 Generated with Claude Code

Fearvox and others added 7 commits May 13, 2026 01:25
…lack mirror sync

Adds two issue templates under .github/ISSUE_TEMPLATE/ for long-lived,
auditable mirrors of in-flight upstream PRs:

- pr_tracker.yml: general PR mirror (scope, evidence, decision log, closure)
- security_tracker.yml: high-priority variant (CWE, severity, reachability,
  verification, disclosure hygiene)

Both carry a `pr-mirror` label so the Linear evermind-dash project and the
Slack #bots channel can subscribe by label. Bilingual EN + 中文.
…tream

Runs every 6 hours via cron + manual workflow_dispatch.
- Rebases fork main onto upstream/main (preserves fork-only commits like
  the issue templates)
- Force-pushes with --force-with-lease for safety
- Opens a tracking issue on conflict instead of failing silently

Uses default GITHUB_TOKEN — no PAT needed since we only push to fork.
Triggers on issues.opened and issues.labeled. When pr-mirror label is
present, creates a corresponding Linear issue in the EverMind-Dash
project via Linear GraphQL API. Comments back on GitHub with the
EVE-id link.

Idempotency: skips if a '🔗 Linear:' marker comment already exists.
Priority: 'urgent' label -> Linear urgent (1); otherwise medium (3).
On API failure: applies 'sync-failed' label for triage.

Requires (configured separately):
  Secret:   LINEAR_API_KEY    (Linear Personal API key, lin_api_*)
  Vars:     LINEAR_TEAM_ID    (EverMind team UUID)
            LINEAR_PROJECT_ID (EverMind-Dash project UUID)
…nnel

Update the disclosure-hygiene checkbox to reference #p-evermind-dash
(the actual Slack channel linked to the EverMind-Dash Linear project)
instead of the placeholder #bots.
…ents

Two compounding fixes to avoid creating multiple Linear issues from a
single GitHub issue creation:

1. concurrency group keyed on issue.number with cancel-in-progress=false
   serializes runs per issue. Second run will see the first run's
   comment and skip via existing idempotency check.

2. Tighten 'labeled' event filter to only fire when the added label is
   pr-mirror itself, not any other label. Eliminates the four extra
   runs that gh issue create --label A --label B ... triggers (one
   issues.opened + four issues.labeled = 5 events for a 4-label create).

Reproduction: gh issue create with 4 labels including pr-mirror was
firing the workflow 5 times concurrently. Idempotency check has a
~5s race window before the first run posts its bot comment, so 2-3
runs created duplicate Linear issues before the rest skipped.

Verified via Issue #4 sync producing both EVE-3 and EVE-4.
Adds the fork overnight patrol workflow, Linear-aware tracking issue creation, and docs guard support for coming-soon use-case placeholders. Verified with local script checks and passing Docs CI.
…n triggers

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 13, 2026 07:20

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a May 31–focused risk log document under .planning/may-agent to track major delivery derailers, with mitigations, escalation triggers, and a weekly review cadence.

Changes:

  • Introduces a 7-item risk register with severity/likelihood, owners, mitigations, and escalation triggers.
  • Adds a simple risk heatmap plus a W1–W3 weekly review cadence aligned to the May 31 deadline.
  • Provides a references section intended to link supporting planning docs.
Comments suppressed due to low confidence (1)

.planning/may-agent/90-risk-log.md:215

  • The References section includes 00-vision.md and CLAUDE_DESKTOP_SANDBOX_SOURCE_TRUTH.md, but neither file exists in the repository. Add these docs or replace with valid in-repo links so the references remain actionable.
## References

- 00-vision.md — success criteria and risk log (top 5)
- `CLAUDE_DESKTOP_SANDBOX_SOURCE_TRUTH.md` — macOS sandbox forensics

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


**Status**: Draft
**Date**: 2026-05-13
**Depends on**: 00-vision.md
Comment on lines +128 to +129
2. **macOS native sandbox**: use `sandbox_init` from libsystem (documented in
`CLAUDE_DESKTOP_SANDBOX_SOURCE_TRUTH.md`). Lower priority than seccomp.

- 00-vision.md — success criteria and risk log (top 5)
- `CLAUDE_DESKTOP_SANDBOX_SOURCE_TRUTH.md` — macOS sandbox forensics
- `~/.claude/projects/.../memory/project_evermind_2026_05.md` — team context
@Fearvox
Fearvox marked this pull request as draft May 13, 2026 09:23
@Fearvox Fearvox added pr-mirror Long-lived mirror of an upstream PR for Linear/Slack tracking tracking Issue tracks a long-lived workflow labels May 13, 2026
@Fearvox
Fearvox marked this pull request as ready for review May 20, 2026 13:01
@Fearvox
Fearvox merged commit 28dd0ca into main May 20, 2026
5 checks passed
@Fearvox
Fearvox deleted the sleep-iter-16-risk-log branch May 20, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-mirror Long-lived mirror of an upstream PR for Linear/Slack tracking tracking Issue tracks a long-lived workflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants