David/TeamIDE-methodology
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Ornith best practices: spell out repo, path and branch per change

Browse Source
This commit is contained in:
David
2026-10-25 22:09:54 -05:00
parent b5aac43f62
commit cf78e1faa5
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Model-Best-Practices/Ornith-q8-best-practices.md
+1
View File
@@ -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". - [ ] 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". - [ ] 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`). - [ ] 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 ## How to run it
- [ ] **One task card per session; fresh session per card.** Don't keep saying "continue" into a long session. - [ ] **One task card per session; fresh session per card.** Don't keep saying "continue" into a long session.