Triage gives the classifier no criteria for choosing implement vs tdd vs feasibility #1562

Closed
opened 2026-10-27 13:40:53 +00:00 by sam · 0 comments
Owner

Triage picks between implement, tdd and feasibility with no stated criteria,
so the choice collapses to the default.

The mission (internal/domain/workflow/triage.go:47-57) spends all its
guidance on the needs_code_change question ("purely conversational,
administrative, or already resolved needs no code change") and says only
"decide ... which workflow suits it best" about the routing half.

The capture-tool schema (triage.go:111) adds nothing:

"workflow": {"type": "string",
  "enum": ["implement","tdd","feasibility"],
  "description": "Which workflow fits best, when needs_code_change is
                  true. Defaults to implement if omitted or unrecognized."}

Nothing says what feasibility is for (no settled design -> design doc
first, per CLAUDE.md Scope Discipline), what tdd is for (a bug with a
reproducible failure), or that a new capability with no design doc must not
go straight to implement. workflow is absent from required, and both the
schema text and triageWorkflowNames default to implement, so omitting the
decision is the cheapest path for the classifier.

Observed: issue 813 (a new capability, no PRD) was triaged to implement and
produced PR #859, a half-wired slice. Feasibility would have produced the
design doc the repo's own rules require first.

Fix: state the selection criteria in the mission and in the schema
description, and make workflow required when needs_code_change is true so
the default stops being free. Relates to archie-core-tjoc, which is why
every issue reaches triage at all.

Close reason

Fixed in PR #870. Both the decide tool schema and the classify mission now state what each of implement/tdd/feasibility is for, and say not to choose implement merely because nothing else fits. Mission extracted to triageMission so TestTriageStatesItsWorkflowSelectionCriteria can assert the criteria reach the model. workflow stays optional in the schema: it is genuinely irrelevant when needs_code_change is false, and this schema shape cannot express a conditional requirement.


Imported from beads archie-core-s5ys · GitHub #916 · type bug · priority P1 · created 2026-09-18 · closed 2026-09-18

Triage picks between implement, tdd and feasibility with no stated criteria, so the choice collapses to the default. The mission (internal/domain/workflow/triage.go:47-57) spends all its guidance on the needs_code_change question ("purely conversational, administrative, or already resolved needs no code change") and says only "decide ... which workflow suits it best" about the routing half. The capture-tool schema (triage.go:111) adds nothing: "workflow": {"type": "string", "enum": ["implement","tdd","feasibility"], "description": "Which workflow fits best, when needs_code_change is true. Defaults to implement if omitted or unrecognized."} Nothing says what feasibility is for (no settled design -> design doc first, per CLAUDE.md Scope Discipline), what tdd is for (a bug with a reproducible failure), or that a new capability with no design doc must not go straight to implement. `workflow` is absent from `required`, and both the schema text and triageWorkflowNames default to implement, so omitting the decision is the cheapest path for the classifier. Observed: issue 813 (a new capability, no PRD) was triaged to implement and produced PR #859, a half-wired slice. Feasibility would have produced the design doc the repo's own rules require first. Fix: state the selection criteria in the mission and in the schema description, and make `workflow` required when needs_code_change is true so the default stops being free. Relates to archie-core-tjoc, which is why every issue reaches triage at all. ### Close reason Fixed in PR #870. Both the decide tool schema and the classify mission now state what each of implement/tdd/feasibility is for, and say not to choose implement merely because nothing else fits. Mission extracted to triageMission so TestTriageStatesItsWorkflowSelectionCriteria can assert the criteria reach the model. workflow stays optional in the schema: it is genuinely irrelevant when needs_code_change is false, and this schema shape cannot express a conditional requirement. --- _Imported from beads `archie-core-s5ys` · GitHub #916 · type bug · priority P1 · created 2026-09-18 · closed 2026-09-18_
sam added the highbug labels 2026-10-27 13:40:53 +00:00
sam self-assigned this 2026-10-27 13:40:53 +00:00
sam closed this issue 2026-10-27 13:40:53 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1562