wassname
0fa250b193
route2 directionality exposed the vector is not load-bearing: hack_anchor force-routes teacher+detector by label (bypassing v_grad), tau calibrated from a live detector, so random==real because labels carried it. Redesign: teacher-off@30, drop force-route, calibrate tau from the A-pairs (no live detector), maybe use the pairset directly vs a rank-1 vector. Decisive test = A5 real(126) vs random(135). Queue snapshot + design notes in docs/REFACTOR_HANDOFF.md. Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>
1.7 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| feedback-afk-check-hygiene | AFK hourly checks: track goal STATE not the pasted checklist, and don't journal routine no-finding checks. |
|
Two corrections from the user on how to run AFK hourly checks (projected_grpo, 2026-06-05).
-
The hourly prompt is a stale template. The user pastes the same checklist each hour; its numbered items (e.g. "job 77 keynote", "job 95 A5 harvest") go stale as those jobs close. Track actual goal state, don't re-execute completed items. The user: "why do you keep doing this no cheat thing? our goal is the placebo vector mystery". The live priority is what matters now (the route2 directionality mystery, #196), not the template. Durable scope lives in docs/AFK_CHECK.md.
-
Don't append routine "checked, nothing changed" entries to RESEARCH_JOURNAL.md. The user: "appending it to the journal all the time? what's the point?". The journal is append-only and for experimental FINDINGS (a new number, a failed-run diagnosis, a real result/verdict). A healthy-check-with-no-news earns no entry; code/comment changes belong in the commit message, not the journal.
Why: AFK time is expensive and the journal is a signal channel; re-running closed work and logging no-news both add noise and burn GPU/context without information gain.
How to apply: Each AFK check: read docs/AFK_CHECK.md (current-scope), do the standing checks (idle GPU? new failures? running-job health), advance the live priority, commit code/progress. Only write a journal entry when a run produces a genuine finding. Relates to feedback-afk-autonomy and feedback-burn-down-task-list.