correction-capture
Installation
SKILL.md
Correction Capture
Capture evidence-backed observations that should carry forward AND that need human review before becoming authority. A clarified requirement and an exposed drift are often the same moment ("you skipped the baseline again" is both). One journal, one skill. The worker records; it never gains authority.
What to capture (the only 5 types)
| type | example | why it needs the review gate |
|---|---|---|
correction |
user: "actually, chart titles must include the run name" | the worker shouldn't self-canonize "what the user wants" |
drift |
a check failed because a constraint wasn't loaded | root cause, so the next run doesn't repeat it |
negative_constraint |
"never auto-promote a lesson" | a "don't do X" that must not be silently relaxed |
pitfall |
"running test A without env B gives false confidence" | a repo trap proven by a failure, not a guess |
architecture_constraint |
"approved lessons live in control/; workers can't write there" | a design rule that, if wrongly rewritten, breaks the trust model |
Captures evidence when something exposes it (a user, a check, a concrete self-observed error). It does not guarantee the agent notices its own drift unprompted.