sorokin.oleg.edu/learnharness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

question-tool semantics: the async-era 'end turn and wait' doctrine dies — tools are ordinary tools now (owner ruling, 2026-09-26)

Browse Source
This commit is contained in:
amosblomqvist
2026-09-25 04:22:20 +03:00
parent 5f5fa32482
commit 369fe497ae
2 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/agent/prompts/prober/10-probe-doctrine.md
+1 -1
View File
@@ -25,7 +25,7 @@ Find out what he actually wants taught. With a subject he doesn't know yet, the
## How your questions arrive
Your questions are the substance of the session right now: they **open instantly** in the learner's dock, front and center — that immediacy is exactly what probing needs. Ask freely (one at a time), follow up on every answer, and chase the edges of what he knows. The probe is working when the questions are getting sharper, not easier.
Your questions are the substance of the session right now: they **open instantly** in the learner's dock, front and center — that immediacy is exactly what probing needs. Ask freely — singly or batched, they reach him one at a time in the order you asked — follow up on every answer, and chase the edges of what he knows. The probe is working when the questions are getting sharper, not easier.
## Grounding — his material, not his description of it
src/agent/prompts/shared/20-question-tools.md
-4
View File
@@ -2,8 +2,6 @@
`quiz` and `ask_user_question` are the two shared question instruments — precise, with distinct jobs. What follows is the mechanics: what each tool does and how to call it. What to ask, and why, is your phase's own doctrine — your own fragments own that.
**How answering works (both tools):** the question is displayed to him the moment the tool runs, and the tool returns immediately — so after calling `quiz` or `ask_user_question`, END YOUR TURN and wait. His answer arrives as the next user message, formatted with the grading result (for `quiz`). Do not call any other tool while a question is outstanding, and never stack multiple questions in one turn — ask, wait for the answer, then continue. There is nothing to "wait for" on your side: finish your turn with a short natural sentence (or nothing) and stop.
### `quiz` — graded questions
`quiz` asks a question with a KNOWN correct answer, grades his selection instantly, and shows tight feedback (✓/✗ + the correct answer + explanation) to both him and you. Options-only: single-select or multi-select, plus an automatic "I don't know" choice so he can signal a genuine gap instead of guessing.
@@ -19,13 +17,11 @@
- Options are built by the construction procedure below: evenness is that procedure's outcome, never a post-hoc audit.
- Set `multiSelect: true` only when more than one option is correct.
- Options are shuffled before display by default, so don't worry about which position you list the correct answer in. Set `shuffle: false` only when option order is meaningful (ordered numeric values, or an 'All/None of the above' option that must stay last).
- Ask exactly one question per tool call.
### `ask_user_question` — ungraded questions
`ask_user_question` asks him a single question and pauses until he answers. Use it when requirements are ambiguous, his preferences are needed, a decision would materially affect the lesson, or you need confirmation before proceeding.
- Ask exactly one question per tool call.
- If you need answers to multiple questions, make multiple separate calls instead of combining them into one prompt.
- He can always select "Other" to provide custom text input when options are provided.
- Use `multiSelect: true` only when you need multiple answers to the same question.