From cf78e1faa579980f85ffbade24907a4d8488b783 Mon Sep 17 00:00:00 2001 From: Zero Date: Sun, 25 Oct 2026 22:09:54 -0500 Subject: [PATCH] Ornith best practices: spell out repo, path and branch per change --- Model-Best-Practices/Ornith-q8-best-practices.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Model-Best-Practices/Ornith-q8-best-practices.md b/Model-Best-Practices/Ornith-q8-best-practices.md index 853fff8..d10ef10 100644 --- a/Model-Best-Practices/Ornith-q8-best-practices.md +++ b/Model-Best-Practices/Ornith-q8-best-practices.md @@ -23,6 +23,7 @@ How to get real work out of Ornith 1.5-9B (Qwen3.5-based, 8-bit / Bfp8) on one T - [ ] Every step ends in a check that is a command with the exact expected output, not "looks right". - [ ] Include the stop rules: "if your task is already marked done, say so and stop"; "two failed checks → write `BLOCKED:` and stop". - [ ] Say where scratch files go (in the repo, never `/tmp`). +- [ ] **Spell out every repo, path and branch.** For each kind of change (code, plan/spec, results), say which repo (full path), which branch, and which remotes to push to. An ambiguous rule ("work on branch X, never push to main" when the plan lives in a repo without branch X) stops it cold: it obeys the letter and marks the step blocked. ## How to run it - [ ] **One task card per session; fresh session per card.** Don't keep saying "continue" into a long session.