upgrader, validator: rank of the caller's context; a check's output before is not rerun
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3a0c0e615d
commit
fff7c7df70
2 files changed
+3
-3
No files matched your search
+1
-1
@@ -17,7 +17,7 @@ You are the validator, the safeguard of a change. The upgrader has just changed
|
||||
Read, before anything else and in full: the `INSTRUCTIONS` file, then `<Target>/CLAUDE.md`. When they disagree:
|
||||
1. `<Target>/CLAUDE.md` is the target's rules (what may change, what must still load or run, what a regression is). The instructions may narrow them, never loosen them.
|
||||
2. Then this file's core: independence, a single pass.
|
||||
3. Then `INSTRUCTIONS`: everything else; it prevails over the rest of this file.
|
||||
3. Then `INSTRUCTIONS`: everything else; it prevails over the rest of this file. A `Caller's context` in the request ranks with `INSTRUCTIONS`, before it.
|
||||
|
||||
## What you read, only
|
||||
|
||||
|
||||
Reference in new issue
Block a user