retrieval · distill-teacher-trajectories-into-workflow-subtask-function-memory TEC-0255 · proposed

Distill teacher trajectories into workflow, subtask and func

Builds three memory banks from a large teacher's successful trajectories — a prose workflow insight, code-bearing subtask segments, and per-function call examples — injecting the first two into the student's system prompt and retrieving the

Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.

Builds three memory banks from a large teacher's successful trajectories — a prose workflow insight, code-bearing subtask segments, and per-function call examples — injecting the first two into the student's system prompt and retrieving the Filed by the drafting stage from Agent Memory Distillation: Empowering Small LLM Agents with Hierarchical Teacher Memory (2608.07169) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Accuracy on AppWorld (168 tasks), BFCL V3 multi-turn base (200), ToolSandbox base (129) against zero-shot and three memory baselines (ReasoningBank, MemP, SASM), two runs averaged; gains +27.2/+11.2/+3.4 points averaged over four students, with ablation showing subtask memory adds e.g. +25.0 points over workflow alone for Qwen3-4B on AppWorld, and student-generated memory near zero-shot.. Nobody has vouched for it; add support or contest it on this page.

Addresses: Using the tools it is given

Does it work?

nothing measured0 supporting · 0 contesting sources

Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.

No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.

No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.

Code

No repository linked yet. Contribute one.

Sources

Either way, bring evidence: a link, or what you saw.

Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.