correction-pipeline skillA
correction-pipeline is agent-read markdown (skill) from garrytan/gbrain: When the user corrects a factual error, root-cause it immediately. Don't just note the correction — trace the error to its source, fix the source, and prevent recurrence. Every factual error is either a data error (bad brain page, bad memory file, bad rendered SOUL/USER identity, bad facts row) or a hallucination (LLM confabulated from partial signals)..
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
# Correction Pipeline > **Convention:** see [conventions/brain-first.md](../conventions/brain-first.md) > — Step 1 of the root-cause chain IS the brain-first lookup chain (`search` > for exact tokens, `query` for concept-shaped questions) before anything else. > > **Convention:** see [_brain-filing-rules.md](../_brain-filing-rules.md) — > corrections edit pages in place; the page stays filed by primary subject. ## Trigger ANY factual error the user identifies. No exceptions. No "I'll note that." (Routing here is a harness convention, not a mechanical guarantee — but once this skill is in play, the no-exceptions contract above is the discipline.) ## Immediate Response 1. **Acknowledge the error.** Don't defend. Don't explain. Just: "You're right. I got that wrong." 2. **Quote the specific wrong claim** so the user can see you know exactly what was wrong. 3. **State the correct fact** as the user gave it. ## Root Cause Analysis (do THIS, not just a memory note) Run these steps IN ORDER. Report findings to the user. ### Step 1: Search the brain ```bash gbrain search "<relevant terms>" --limit 10 ``` For concept-shaped or synonym-phrased claims, escalate to `gbrain query …
Read the whole file at its exact version.
How to install
mdr add garrytan/gbrain/correction-pipeline@v1.0.0mdr add garrytan/gbrain/correction-pipeline@sha256:caf1264b7afec465Pin 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_wjxqpgum4tgeqxet)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12921 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
garrytan/gbrain · 30,275 stars · license MIT · pushed 2026-09-23 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_wjxqpgum4tgeqxet GET https://markdownregistry.com/api/v1/resolve?ref=garrytan/gbrain/correction-pipeline GET https://markdownregistry.com/api/v1/blob/caf1264b7afec46569d30f6d92b07f37ae375e3f4e6aeddd58866aec327053de
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.