Opens research 043 through playbook 01, from the operator's idea of 2026-10-10: could the issue tracker estimate how hard an issue is, and so which model an agent should solve it with?
The overview frames the questions and answers none of them yet: what complexity means and whether a report alone shows it, who estimates and when, a stored hint versus one derived from a setting, how outcomes are measured (first-time review and checks, rework, tokens and wall time per model), the risk of a weak model on a core change, the relation to severity and needs on the tracker, who reads the hint, and prior art.
Only 01-RESEARCH/043-…/00-overview.md is added. records.py, index.py, cycle.py and words.py pass locally.
Opens research 043 through playbook 01, from the operator's idea of 2026-10-10: could the issue tracker estimate how hard an issue is, and so which model an agent should solve it with?
The overview frames the questions and answers none of them yet: what complexity means and whether a report alone shows it, who estimates and when, a stored hint versus one derived from a setting, how outcomes are measured (first-time review and checks, rework, tokens and wall time per model), the risk of a weak model on a core change, the relation to severity and needs on the tracker, who reads the hint, and prior art.
Only `01-RESEARCH/043-…/00-overview.md` is added. records.py, index.py, cycle.py and words.py pass locally.
The operator asked whether the issue tracker could estimate how hard an issue is
and so which model an agent should fix it with. Framed as questions, not answers.
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@81aad4189b77` — **stopped** since 2026-10-11T19:15:47Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 15:37 (new) → proposed (announced): novox/hq#282's head announced
- 2026-10-10 15:38 proposed → checked (checked): the verdict names this commit
- 2026-10-10 15:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 19:15 ready → stopped (closed): the pull request closed unmerged
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Closing (triage, 2026-10-11): it only adds research 043 under 01-RESEARCH, which hq no longer holds since #312 (issue 426). Research lives in the knowledge base now; the knowledge base has no research 043. To keep it, reserve and propose it there (knowledge-base.reserve kind research, knowledge-base.propose).
Closing (triage, 2026-10-11): it only adds research 043 under 01-RESEARCH, which hq no longer holds since #312 (issue 426). Research lives in the knowledge base now; the knowledge base has no research 043. To keep it, reserve and propose it there (`knowledge-base.reserve` kind research, `knowledge-base.propose`).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Opens research 043 through playbook 01, from the operator's idea of 2026-10-10: could the issue tracker estimate how hard an issue is, and so which model an agent should solve it with?
The overview frames the questions and answers none of them yet: what complexity means and whether a report alone shows it, who estimates and when, a stored hint versus one derived from a setting, how outcomes are measured (first-time review and checks, rework, tokens and wall time per model), the risk of a weak model on a core change, the relation to severity and needs on the tracker, who reads the hint, and prior art.
Only
01-RESEARCH/043-…/00-overview.mdis added. records.py, index.py, cycle.py and words.py pass locally.Delivery
novox/hq@81aad4189b77— stopped since 2026-10-11T19:15:47ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Closing (triage, 2026-10-11): it only adds research 043 under 01-RESEARCH, which hq no longer holds since #312 (issue 426). Research lives in the knowledge base now; the knowledge base has no research 043. To keep it, reserve and propose it there (
knowledge-base.reservekind research,knowledge-base.propose).Pull request closed