correction-pipeline

Root-cause user-reported factual errors and fix them at their contamination source.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill correction-pipeline-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: correction-pipeline
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/correction-pipeline
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill correction-pipeline-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent states a wrong fact, simply noting the correction leaves the bad data in place to resurface later. This Skill traces every user-reported factual error back to its true source — a brain page, memory file, rendered identity file, or facts table — fixes it there, and checks for propagation. ## Core Features & Use Cases - Root-Cause Classification: Sorts each error into BRAIN_ERROR, MEMORY_ERROR, SOUL_USER_ERROR, FACTS_TABLE_ERROR, HALLUCINATION, STALE_DATA, or CROSS_CONTAMINATION, each with its own fix surface. - Source-Level Fixes: Edits brain pages with commit and re-sync, expires wrong facts rows via forget/remember with provenance, and fixes rendered SOUL.md/USER.md through the bootstrap answer bank rather than direct edits. - Propagation Checks: Greps the whole brain and runs gbrain search to find and fix every instance of the wrong fact, then delivers a structured root-cause report. - Use Case: A user says "That's wrong — Alice never worked at WidgetCo." The Skill searches the brain and memory, finds the bad claim on a people page, corrects it with a dated source note, re-syncs, checks for spread, and reports the fix. ## Quick Start Tell the agent "that's wrong, root-cause this error and fix it everywhere" after it states an incorrect fact.

Frequently Asked Questions about correction-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a factual error my AI agent keeps repeating?

Trigger the correction pipeline by stating the error, and it traces the claim through the brain, memory files, identity files, and facts table. It then fixes the actual source, checks for propagation, and reports the root cause.

What is the difference between a brain error and a hallucination?

A BRAIN_ERROR means the wrong fact exists in a stored brain page and is fixed by editing the page, committing, and re-syncing. A HALLUCINATION has no source; the fix is writing a guard fact with provenance so the confabulation cannot reseed.

Why shouldn't I edit SOUL.md or USER.md directly to fix identity errors?

These files are rendered from the bootstrap answer bank, so hand edits are silently lost on the next render. The fix goes through gbrain bootstrap interview to update the answer, then a re-render of the affected file.

How does the correction pipeline handle stale or outdated facts?

STALE_DATA errors are fixed by updating the source page with current truth and superseding old facts rows using gbrain forget followed by gbrain remember with fresh provenance. This keeps both the repo and database in agreement.

When should I use the contradictions probe instead of this skill?

The correction pipeline is reactive and fires only when a user reports an error. The contradictions probe (gbrain eval suspected-contradictions) is proactive, finding intra-brain conflicts before the user notices them.