de-meta the system prompts; method leads the composition (owner, 2026-09-27)
The owner's capture-vs-composition check confirmed the wire sends exactly
what composes (byte-identical save the nodeId paragraph ebfe058 had since
changed). This wave removes the implementation meta that leaked into the
prompts and reorders so the method carries weight:
- base: owner's new opener verbatim (install understanding; the
understanding definition — which absorbs the old 'Understanding is
structure' paragraph); Voice moved in from shared/10 (deleted); the
philosophy keeps edge-dependence + logistics ('standard learning'
dropped per owner); intro's two-agents/fragments sentence gone.
- teacher/05-method opens with the owner's methodology bridge ('No other
teaching methods come close') — paragraph 3 of the opener, placed here
so the shared base never points the prober at methodology it doesn't
carry.
- deleted: teacher/60-probing-in-brief (self-evident from shared history;
its mid-lesson mini-probe move salvaged into 20-teaching as one
sentence), the 'Session shape — the durable artifact' section
(extraction-pipeline meta), the fragments-meta lines in shared/20 and
05-method, 'the transcript's seam' phrasing, prober's 'the teacher
that takes over' / 'the handoff is automatic'.
- composition reorder (listSourceSegments): base -> the agent's own
fragments -> shared/ appendix. Teacher method now starts at 12% in
(was 62%); prober doctrine at 34%. shared/20 opens with the owner's
decision rule (quiz only for known-correct-answer, ask for everything
else).
- HANDOFF_TEXT: the owner's user-message version — first-person, paces
the planning (unconditional truths, motivated derivations), ends at
plan_init + accept-or-changes.
Teacher 31.4k -> 28.7k chars; prober 10.0k -> 9.6k. Gates: typecheck 0,
1018/1018, lint clean, build green. (Suite runs 16s; the earlier 10-min
timeout was stale node_modules after master's df1328e 0.87.1 sync —
npm install fixed it.)
This commit is contained in:
@@ -165,12 +165,11 @@ export interface TurnUsage {
|
||||
* 2026-09-26: the learner's next message is a natural reply — a change
|
||||
* request or the go-ahead). */
|
||||
export const HANDOFF_TEXT =
|
||||
"The probe is concluded — the learner assessment is recorded. " +
|
||||
"This is the session's highest-leverage moment, and nothing has been authored yet — take your time. " +
|
||||
"Read his assessment and the probing transcript, and reason out the optimal way to teach this person this thing: " +
|
||||
"what he already holds and where each strand runs out, the misconceptions to route around, " +
|
||||
"and the minimal tree from what he holds as obviously true to his goal — so every step lands as obviously true. " +
|
||||
"When the plan is genuinely reasoned out, call plan_init, present it, and end your turn — his next message either asks for changes or moves the lesson forward.";
|
||||
"Next: plan the full teaching arc from my current understanding to the goal understanding. " +
|
||||
"Apply the teaching methodology in your system prompt, and find the optimal way to teach me this. " +
|
||||
"Find the unconditional truths, plan the motivated derivations/discoveries, so every reasoning step has to land as obviously true. " +
|
||||
"Take your time here and really think this through. " +
|
||||
"When it's genuinely reasoned out, call plan_init and present the plan; I'll accept it or ask for changes.";
|
||||
|
||||
|
||||
export interface PlanBlockData {
|
||||
|
||||
Reference in New Issue
Block a user