Bläddra i källkod

Updated example and documentation

Efren Yevale Varela 4 dagar sedan
förälder
incheckning
227a6405a7
2 ändrade filer med 11 tillägg och 0 borttagningar
  1. 5 0
      docs/TRIAGE.md
  2. 6 0
      questions.example.json

+ 5 - 0
docs/TRIAGE.md

@@ -254,6 +254,11 @@ The example is the eight-question brief set, in file order:
 | `deadline` | `noul` | Deadlines |
 | `open_question` | `noul` | Open Questions |
 
+Each `noul` question in the example also ships a `threshold` (0.70–0.90), measured across real
+sessions with `triage-eval` so that a flag means something instead of matching most of a meeting.
+Delete a key to fall back to `[triage].escalate_threshold`; re-measure before trusting them on a
+different kind of conversation.
+
 `substantive_update` is the gate: when the model returns a `p` below `brief_gate_threshold`,
 the turn is still classified and shown, but the brief isn't asked to update. The gate is
 fail-open, so a missing or non-numeric answer passes. `questions.json` is gitignored user

+ 6 - 0
questions.example.json

@@ -1,6 +1,7 @@
 {
   "substantive_update": {
     "type": "noul",
+    "threshold": 0.75,
     "instructions": "This recent conversation segment adds something a running brief should record.",
     "criteria": {
       "true": "a new issue, decision, owner, deadline, opportunity, risk, or question appears",
@@ -9,6 +10,7 @@
   },
   "opportunity": {
     "type": "noul",
+    "threshold": 0.9,
     "instructions": "A commercial, product, or process opportunity or growth idea was raised.",
     "criteria": {
       "true": "an opportunity or idea worth pursuing is mentioned",
@@ -17,6 +19,7 @@
   },
   "blocker": {
     "type": "noul",
+    "threshold": 0.75,
     "instructions": "An obstacle, dependency, objection, or risk that could block or delay the work was raised.",
     "criteria": {
       "true": "something could stop or delay the work",
@@ -36,6 +39,7 @@
   },
   "action_item": {
     "type": "noul",
+    "threshold": 0.7,
     "instructions": "Someone committed to a concrete next step.",
     "criteria": {
       "true": "a specific next action or commitment was made",
@@ -55,6 +59,7 @@
   },
   "deadline": {
     "type": "noul",
+    "threshold": 0.7,
     "instructions": "A specific date, deadline, or time commitment was stated for a piece of work.",
     "criteria": {
       "true": "a concrete date or timeframe is committed to a task, a delivery, or a scheduled follow-up",
@@ -63,6 +68,7 @@
   },
   "open_question": {
     "type": "noul",
+    "threshold": 0.9,
     "instructions": "Something important is still ambiguous and needs a follow-up question.",
     "criteria": {
       "true": "unclear or unresolved; a follow-up is needed",