Rules
Always-on guidance loaded every session. Rules are never optional — they fire before every agent response and enforce gald3r conventions without requiring any user action.
Always Apply
Loaded in every single agent session. These rules fire unconditionally — agent cannot opt out.
Agent Request
Loaded on demand when the agent determines the rule is relevant to the current task.
| Rule ID | Type | What it enforces |
|---|---|---|
| g-rl-00-always | Always Apply | Response format, token tracking, PowerShell vs bash routing, Python UV venv, research-before-answering policy |
| g-rl-01-documentation | Always Apply | docs/ folder requirement, timestamp naming convention, allowed root files, before-creating-md-file gate |
| g-rl-02-git-workflow | Agent Request | Commit message format, branch naming, conventional type prefixes, no-amend-after-push rules |
| g-rl-34-todo-lifecycle | Always Apply | Stub/TODO enforcement — every TODO must have a follow-up task and TODO[TASK-X→TASK-Y] annotation before commit |
| g-rl-35-bug-discovery | Always Apply | Zero-ignore bug policy — current-task bugs fixed inline; pre-existing bugs get a BUG entry + annotation before [🔍] |
| g-rl-38-component-creation | Always Apply | Every new .gald3r_sys/ component must include subsystem_membership tagging. No tagging = violation. |
| g-rl-26-readme-changelog | Always Apply | At every feature boundary: append CHANGELOG.md and update README.md if a relevant section exists |
| g-rl-33-enforcement-catchall | Always Apply | Catchall enforcement gate — surfaces any unresolved violations from other rules before marking tasks complete |