You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cff7ff6
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: skillopt/envs/babyvision/prompts/deep_probe.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
You are an expert diagnostic-probe designer for BabyVision-style visual reasoning tasks.
2
2
3
-
You will be shown representative trajectories, the current student skill, and the student's original prompt context.
4
-
Design one SMALL diagnostic instruction that exposes the student's intermediate visual judgment without materially changing the original scaffold.
3
+
You will be shown representative trajectories, the current target skill, and the target's original prompt context.
4
+
Design one SMALL diagnostic instruction that exposes the target's intermediate visual judgment without materially changing the original scaffold.
5
5
6
6
## Hard Constraints
7
7
1. Do NOT substantially change the original scaffold.
8
8
2. Do NOT prescribe a new step-by-step solving method.
9
9
3. You MAY ask for a short structured list of a few intermediate conclusions, candidate cues, or counted units, as long as it stays close to the original scaffold.
10
10
4. Do NOT ask for exhaustive listing of all cells, all objects, or a full chain-of-thought.
11
-
5. Ask only for a short readout that reveals the student's current latent state.
11
+
5. Ask only for a short readout that reveals the target's current latent state.
12
12
6. Keep it brief and structured, and require the final answer to remain in <answer>...</answer>.
13
13
14
14
## Good Probe Targets
@@ -21,5 +21,5 @@ Design one SMALL diagnostic instruction that exposes the student's intermediate
You are an expert diagnostic-probe designer for theorem-grounded mathematical multiple-choice tasks executed through a Codex trace.
2
2
3
-
You will be shown representative trajectories, the current student skill, the student's original prompt context, hidden reference fields, and numbered Codex trace steps.
4
-
Choose exactly one trajectory and one probe point. The probe point determines how much of the prior Codex trace will be shown back to the student before asking a short diagnostic question.
3
+
You will be shown representative trajectories, the current target skill, the target's original prompt context, hidden reference fields, and numbered Codex trace steps.
4
+
Choose exactly one trajectory and one probe point. The probe point determines how much of the prior Codex trace will be shown back to the target before asking a short diagnostic question.
5
5
6
6
## Hard Constraints
7
-
1. Do NOT reveal or paraphrase the hidden reference directly to the student.
7
+
1. Do NOT reveal or paraphrase the hidden reference directly to the target.
8
8
2. Do NOT prescribe a new full solving procedure.
9
9
3. Do NOT ask for a full proof, full chain-of-thought, or exhaustive option-by-option derivation.
10
-
4. Ask only for a short readout of the signal that should already exist at that point in the student's process.
10
+
4. Ask only for a short readout of the signal that should already exist at that point in the target's process.
11
11
5. The probe instruction must explicitly request a short <analysis>...</analysis> block before the final <answer>...</answer>.
12
12
6. Select a probe point that is informative about theorem choice, decisive constraint, option elimination, or why a stronger/weaker option should be rejected.
13
13
14
14
## Probe Point Semantics
15
15
-`probe_target_id` must be one of the shown trajectory ids.
16
-
-`probe_after_step` is the last numbered Codex trace step that should remain in the student's context.
17
-
- The student will be re-run with the raw trace up to and including `probe_after_step`, then asked your `probe_instruction`.
16
+
-`probe_after_step` is the last numbered Codex trace step that should remain in the target's context.
17
+
- The target will be re-run with the raw trace up to and including `probe_after_step`, then asked your `probe_instruction`.
18
18
- To probe before a tool call, choose the step immediately before that tool call.
19
19
20
20
Respond ONLY with a valid JSON object:
21
21
{
22
-
"reasoning": "<why this trajectory and probe point expose the student's intermediate state>",
22
+
"reasoning": "<why this trajectory and probe point expose the target's intermediate state>",
23
23
"probe_target_id": "<trajectoryid>",
24
24
"probe_after_step": <integerstepnumber>,
25
-
"probe_instruction": "<the exact instruction text to append to the student's prompt>"
25
+
"probe_instruction": "<the exact instruction text to append to the target's prompt>"
0 commit comments