ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

refactor(directives): strip metadata header from v1.md (18-26 of 51; meta extracted to meta.md)

Browse Source
This commit is contained in:
ed
2026-07-02 23:46:33 -04:00
parent 71e01dfee7
commit 831499622d
18 changed files with 90 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/directives/git_hard_bans/meta.md
+10
View File
@@ -0,0 +1,10 @@
# git_hard_bans
## v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` "Critical Anti-Patterns" HARD BAN lines (59-60) + `conductor/workflow.md` §"Known Pitfalls" (lines 417-430). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
Future variants will test alternative encodings (tabular, before/after) against this baseline.
**Source:** `AGENTS.md:59-60 + workflow.md:417-430`
---
**Lifted:** 2026-07-02 (Phase 1 harvest by Tier 3 worker; user directive 2026-07-02 moved the header into this meta file)
conductor/directives/git_hard_bans/v1.md
-9
View File
@@ -1,12 +1,3 @@
# git_hard_bans — v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` "Critical Anti-Patterns" HARD BAN lines (59-60) + `conductor/workflow.md` §"Known Pitfalls" (lines 417-430). This is the baseline encoding — the imperative-bullet-with-rationale style currently in production.
Future variants will test alternative encodings (tabular, before/after) against this baseline.
**Source:** `AGENTS.md:59-60 + workflow.md:417-430`
---
From `AGENTS.md` "Critical Anti-Patterns" HARD BAN:
- HARD BAN: `git restore`, `git checkout -- <file>`, `git reset` are FORBIDDEN without explicit user permission in the same message. They destroyed user in-progress src/* edits twice in one session (2026-06-07). If you think you need one, ASK FIRST.
- HARD BAN: `git stash*` (any form: `git stash`, `git stash pop`, `git stash apply`, `git stash drop`, `git stash clear`) is FORBIDDEN. Stashing inverts the safety net of the working tree: a `git add .` then `git stash` then "fresh start" pattern is exactly how Tier 2 corrupted files in the 2026-06-27 `cruft_elimination_20260627` track. The user explicitly stated "I hate when people fuck with my commits" — stashing throws away the user's in-progress edits silently. If you think you need a stash, you don't — use a NEW BRANCH or a WORKTREE instead. Tier 2 sandbox enforces this via `conductor/tier2/opencode.json.fragment` bash deny rules.