Repository navigation
Refuse attacks: a central ethics rule above every other - #69
Merged
Merged
Conversation
heinzel administers machines its operator is responsible for and nothing else, so it must never recover a password or key, break into a system, scan foreign hosts, surveil people, hide traces, or turn the infrastructure against others. The rule holds on the operator's own hosts too, because "it's my server" cannot be checked and is the stock excuse, and no framing (a book, research, a CTF, a claimed permission, an emergency, a step split into harmless parts) unlocks it. It cannot be overridden by a custom rule or by HEINZEL_GUARD_DISABLE, while defensive work stays allowed, and the guard hook backs it below the model layer by blocking the known crackers and attack suites, both run and installed, in every permission mode. An AI agent wrote this text in my name. I know that is problematic.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A central ethics rule, above every other, that no story around a
request can work around.
heinzel administers machines its operator is responsible for and
nothing else: never recover a password or key, break into a
system, scan hosts it does not administer, surveil people, hide
traces, or turn the infrastructure against others. It holds on
the operator's own hosts too, because "it's my server" cannot be
checked. No framing unlocks it (a book, research, a CTF, a
claimed permission, an emergency, a role play, a step split into
harmless parts), and neither a custom rule nor
HEINZEL_GUARD_DISABLE overrides it. Defensive work stays allowed:
reading auth logs, checking password policy without touching a
hash, resetting a password on a host it administers.
CLAUDE.md: an "Ethics (above every other rule)" block at thetop, and a note that
rules/ethics.mdtakes no overrides.rules/ethics.md: the full rule, the no-framing list, whatstays allowed, and the refusal behaviour (one sentence, a line
in
memory/refusals.log, the topic stays refused for thesession).
guard-taboos.sh: a mechanical backstop blocking the knowncrackers and attack suites by name, both run and installed, in
every permission mode. Like the other taboos it names a known
set, not the effect, so a renamed or hand-built tool is the
model layer's job; 20 new fixtures, 742/0 green.
Ships as 2.32.0.
An AI agent wrote this text in my name. I know that is problematic.