AGENTS.md@public/files/anarlog/crates/db-change agentsA
AGENTS.md@public/files/anarlog/crates/db-change is agent-read markdown (agents) from modem-dev/ossrules.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# `db-change` ## Use This Crate For - Commit-time table invalidation signals sourced from SQLite hooks. - Monotonic transaction sequencing shared by higher-level reactive consumers. ## Put Changes Elsewhere When - Pool ownership or connection open policy belongs in `db-core`. - Dependency analysis and subscription reruns belong in `db-reactive`. - Row-level or predicate-level invalidation is out of scope here. ## Hard Rules - Hooks must be installed through `SqlitePoolOptions::after_connect` before connections exist. Attaching later misses writes. - Signals are best-effort for writes executed through hooked pooled connections only. External writers and unhooked connections are invisible. - Emit only after commit. Rollback must clear pending state without broadcasting. - One committed transaction gets one monotonically increasing `seq`; every table event flushed from that transaction shares it. - Multiple writes to the same table inside one transaction coalesce. `TableChangeKind` is last-write metadata, not a full mutation history. - Consumers should treat `table + seq` as the invalidation signal. Do not build correctness on the exact `Insert`/`Update`/`Delete` mix. …
Read the whole file at its exact version.
How to install
mdr add modem-dev/ossrules/public/files/anarlog/crates/db-change/AGENTS.md@git:20260915.997c05bmdr add modem-dev/ossrules/public/files/anarlog/crates/db-change/AGENTS.md@sha256:3ac9f755ad507accPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qade4ijyy2ifcb64)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1402 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
modem-dev/ossrules · 52 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qade4ijyy2ifcb64 GET https://markdownregistry.com/api/v1/resolve?ref=modem-dev/ossrules/public/files/anarlog/crates/db-change/AGENTS.md GET https://markdownregistry.com/api/v1/blob/3ac9f755ad507acce8a9d3b12c8b6ac8ae066056c1903d1a49b5ea388404e14b
Your agent 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.