Route a General Chat question to the profile that fits it

2026-08-09 00:36:13 -04:00
parent 37784bce6c
commit d9225d06d9
4 changed files with 122 additions and 18 deletions
@@ -84,3 +84,24 @@ what is going on here | troubleshoot | Orchestrators/daily_sync_maintenance | |

 # ── The code profile answers from the model alone: no passages, no live state ──────────────────
 write me a script that copies a folder | code | | | hasnt=health,log_tail,incidents,conf_keys
+
+# ── General Chat routes to the profile that fits, not always to the Assistant ──────────────────
+# Chat had one escalation target, so a fault report and a request for code both landed on the
+# documentation assistant. Both were answered adequately; neither was answered well. Order is the
+# policy — code is checked first because it is the only intent about a thing that does not exist
+# yet, and troubleshoot requires diagnostic phrasing AND something here to diagnose.
+why did the daily orch fail | chat | | | profile=troubleshoot diag=yes target=Orchestrators/daily_sync_maintenance
+the daily orch is broken | chat | | | profile=troubleshoot diag=yes
+why did arr_sync.sh error out | chat | | | profile=troubleshoot diag=yes
+create a script to prune old logs | chat | | | profile=code hasnt=health,log_tail,incidents
+make me a one-liner that counts files | chat | | | profile=code
+write me a bash script for backups | chat | | | profile=code
+
+# Diagnostic phrasing about nothing here stays in chat — "why" is not a Varaverk question on its
+# own, and escalating adds capability, so a wrong escalation costs more than a missed one.
+why is the sky blue | chat | | | profile=chat caps=none hasnt=health,log_tail,incidents,conf_keys
+what is wrong with my car | chat | | | profile=chat caps=none
+
+# Naming a script and asking what it does is documentation, not a request to write one. The code
+# router is anchored on the verb for exactly this pair.
+what does arr_sync.sh do | chat | | | profile=varaverk