AGENTS.mdA
AGENTS.md from bloom-directory/bloom is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add bloom-directory/bloom/AGENTS.md@git:20261102.402b028Pins git:20261102.402b028 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- bloom-directory/bloom
- Path
AGENTS.md- Versions recorded
- 4
- Latest version
- git:20261102.402b028, committed Nov 2, 2026
- First version recorded
- Sep 14, 2026
- Size
- 4,468 bytes
- Repository stars
- 26
- 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
# Bloom contributor and agent guide Use [DEVELOPMENT.md](./DEVELOPMENT.md) for setup and cross-repository workflows, and [TESTING.md](./TESTING.md) for validation gates. The instructions exposed inside a running VFS are a separate operator contract in [agent-guidance.md](./crates/bloom-vfs/src/docs/agent-guidance.md). ## Authority and ownership Read the relevant architecture before changing a cross-process contract: - [Triad process architecture](./docs/specs/2026-07-23-triad-process-architecture.md) - [Wallet architecture and account identity](./docs/architecture/Wallet.md) - [Solana native integration](./docs/architecture/Solana%20Native%20Integration.md) - [Triad release package](./packaging/triad/release/README.md) Historical plans and implementation logs are evidence, not authority, when they conflict with current code or the documents above. Machine talks to Broker; only Broker talks to Signer. Fix an invariant in its owning repository: | Repository | Owns | |---|---| | `bloom` (Machine) | CLI, VFS, Petals, public projections, staging, simulation, broadcast, reconciliation | | `bloom-broker` | Ceremony verification, policy semantics, Sealed Approvals, authorization | …
Read the whole file at its exact version.
How to install
mdr add bloom-directory/bloom/AGENTS.md@sha256:e556d08403935368The line at the top of this page pins the label git:20261102.402b028, 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_fi5rljctixzz2t2g)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 14, 2026 and Nov 2, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261102.402b028 latest | 2026-11-02 | 402b028 | 4,468 B | A | view · diff |
| git:20261030.8e20efd | 2026-10-30 | 8e20efd | 4,335 B | A | view · diff |
| git:20260923.d70e036 | 2026-09-23 | d70e036 | 4,195 B | A | view · diff |
| git:20260914.68e3911 | 2026-09-14 | 68e3911 | 4,161 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4468 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
bloom-directory/bloom · 26 stars · license MIT · pushed 2026-11-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_fi5rljctixzz2t2g GET https://markdownregistry.com/api/v1/resolve?ref=bloom-directory/bloom/AGENTS.md GET https://markdownregistry.com/api/v1/blob/e556d08403935368976e531059cd8abfe4259d5b971f91dadeac121d518dd77b
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: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.
More from bloom-directory/bloom
Every file in bloom-directory/bloom