AGENTS.md@infrastructure/provenanceA
AGENTS.md@infrastructure/provenance from docxology/template is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add docxology/template/infrastructure/provenance/AGENTS.md@git:20260922.a7fab00Pins git:20260922.a7fab00 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- docxology/template
- Path
infrastructure/provenance/AGENTS.md- Versions recorded
- 4
- Latest version
- git:20260922.a7fab00, committed Sep 22, 2026
- First version recorded
- Jul 6, 2026
- Size
- 5,232 bytes
- Repository stars
- 23
- License
- Apache-2.0
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
# `infrastructure/provenance/` — Provenance DAG (PROVENANCE-1) ## Purpose Records the **live lineage** of research sessions as a content-addressed DAG: which tools ran, which artifacts they produced, which sources were consulted, and which claims were verified or refuted. This module complements the static `evidence_graph` (pipeline-DAG snapshot) and `evidence_registry` (manuscript-facing claim ledger) by capturing dynamic session provenance with full transitive lineage queries. ## Files | File | Role | |---|---| | `models.py` | Typed dataclasses: `NodeKind`, `EdgeRelation`, `ArtifactNode`, `RunNode`, `SourceNode`, `ClaimNode`, `Edge` | | `store.py` | Content-addressed JSON store; `Provenance` namespace with `record`, `link`, `get`, `query`, `list`, `clear`, `path` | | `review.py` | Reviewer finding system; `Review` namespace with `record`, `findings_for_node` | | `validation.py` | DAG structural and topological validator (`ProvenanceValidationReport`, `validate_provenance_dag`) | | `cli.py` | CLI commands: `record-artifact`, `list`, `review`, `validate`, `experiment-add`, `experiment-update`, `experiment-validate` | …
Read the whole file at its exact version.
How to install
mdr add docxology/template/infrastructure/provenance/AGENTS.md@sha256:8870d1245e08e610The line at the top of this page pins the label git:20260922.a7fab00, 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_i4zne5ss7yjvdedw)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 6, 2026 and Sep 22, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.a7fab00 latest | 2026-09-22 | a7fab00 | 5,232 B | A | view · diff |
| git:20260821.60fb9b9 | 2026-08-21 | 60fb9b9 | 3,771 B | A | view · diff |
| git:20260820.0db2afc | 2026-08-20 | 0db2afc | 3,536 B | A | view · diff |
| git:20260706.11e587f | 2026-07-06 | 11e587f | 3,401 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5232 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
docxology/template · 23 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i4zne5ss7yjvdedw GET https://markdownregistry.com/api/v1/resolve?ref=docxology/template/infrastructure/provenance/AGENTS.md GET https://markdownregistry.com/api/v1/blob/8870d1245e08e6101b1969af8d0427a0c1a630bcfae69a14351933f920100772
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.