CLAUDE.md@src/grove/core/notificationsA
CLAUDE.md@src/grove/core/notifications from bearlike/grove is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.
mdr add bearlike/grove/src/grove/core/notifications/CLAUDE.md@git:20260812.6377c5aPins git:20260812.6377c5a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- CLAUDE.md file
- Repository
- bearlike/grove
- Path
src/grove/core/notifications/CLAUDE.md- Versions recorded
- 3
- Latest version
- git:20260812.6377c5a, committed Aug 12, 2026
- First version recorded
- Jun 15, 2026
- Size
- 17,854 bytes
- Repository stars
- 8
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# grove.core.notifications — push on workspace edges > ↑ [grove.core](../CLAUDE.md) · [root](../../../../CLAUDE.md) Turns the existing activity stream into push notifications: *deliver a notification when a workspace crosses into a state that wants the human*. The broker decides; channels deliver. Off by default (`cfg.notifications`). One concern per type, no free functions and no module-level factories: `WorkspaceIdentity`, `NotificationReason` (the phrase + the urgency, together), `Notification`, `NotificationChannel` (the ABC contract), `NotificationBroker` (the edge engine + the one factory). ## The engine seam - **Reuse the activity bus; add NO status computation.** The broker subscribes via `bind(ActivityService.subscribe)` exactly like `_SseHub` and reads each session's already-blended `AgentActivityState`. A notification is an *edge* in what already flows past it — never a new status engine. `bind` takes the `subscribe` callable, not the service, so the broker depends only on the bus shape and tests drive it with a bare stub. - **`evaluate` is pure; `dispatch` is the I/O edge.** `evaluate(delta)` folds one …
Read the whole file at its exact version.
How to install
mdr add bearlike/grove/src/grove/core/notifications/CLAUDE.md@sha256:bffee52f8ce4c238The line at the top of this page pins the label git:20260812.6377c5a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nysefs5agasuai4p)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 15, 2026 and Aug 12, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260812.6377c5a latest | 2026-08-12 | 6377c5a | 17,854 B | A | view · diff |
| git:20260803.49581e6 | 2026-08-03 | 49581e6 | 13,286 B | A | view · diff |
| git:20260615.085726f | 2026-06-15 | 085726f | 5,001 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (17854 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bearlike/grove · 8 stars · license MIT · pushed 2026-10-02 · branch current
API
GET https://markdownregistry.com/api/v1/artifacts/art_nysefs5agasuai4p GET https://markdownregistry.com/api/v1/resolve?ref=bearlike/grove/src/grove/core/notifications/CLAUDE.md GET https://markdownregistry.com/api/v1/blob/bffee52f8ce4c238e6037e84d76638038ab63d6ab36ac43497ab4e992768b292
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what a CLAUDE.md file is · keeping AGENTS.md and CLAUDE.md in sync · which agent file does what.