cad-suggest: the tuner has no front door #110

Closed
opened 2026-08-12 18:32:33 +00:00 by john · 0 comments
Owner

planning.mjs trace suggest already reads the run record and returns ranked routing recommendations with the evidence behind each one. Nothing surfaces it. workflows/report.md prints a one-line pointer at the end of /cad-report, and that is the entire discovery path: a user who does not run /cad-report, or who stops reading before its last line, never learns the tuner exists.

Smallest honest version: /cad-suggest, a skill at skills/cad-suggest/SKILL.md that relays the seam and presents each recommendation with the trace figures it rests on. It writes no config of its own - anything accepted goes through /cad-config, named by key, so the write face stays in one place. A trace too thin to clear the evidence floors reports that refusal in one line instead of inventing a suggestion to fill the space.

Registration is part of the requirement, not a follow-up: skills/cad-help, README.md and .planning/DOCS-CLAIMS.md.

Ordering: TRC-01 (#108) lands first. The coordinator events change what the evidence floors are computed over, so the command cannot correctly ship until those are in.

`planning.mjs trace suggest` already reads the run record and returns ranked routing recommendations with the evidence behind each one. Nothing surfaces it. `workflows/report.md` prints a one-line pointer at the end of `/cad-report`, and that is the entire discovery path: a user who does not run `/cad-report`, or who stops reading before its last line, never learns the tuner exists. Smallest honest version: `/cad-suggest`, a skill at `skills/cad-suggest/SKILL.md` that relays the seam and presents each recommendation with the trace figures it rests on. It writes no config of its own - anything accepted goes through `/cad-config`, named by key, so the write face stays in one place. A trace too thin to clear the evidence floors reports that refusal in one line instead of inventing a suggestion to fill the space. Registration is part of the requirement, not a follow-up: `skills/cad-help`, `README.md` and `.planning/DOCS-CLAIMS.md`. Ordering: TRC-01 (#108) lands first. The coordinator events change what the evidence floors are computed over, so the command cannot correctly ship until those are in.
john added this to the v3.1.0 milestone 2026-08-12 18:32:33 +00:00
john closed this issue 2026-08-13 15:32:18 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: crenshawdev/cadence-archived#110
No description provided.