executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
recovery_evaluationEvaluate Tent recovery artifacts for numeric metrics, source-boundary compliance, and mechanism-faithful proxy evidence.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this skill after running a Tent recovery experiment. It is appropriate for full CIFAR/ImageNet recovery and for soft-mode reduced recovery. Do not accept a proxy solely because an accuracy value is high; the trace must show target-only entropy adaptation, changed modulation parameters, and executable evidence.
recovery_result.json with paper target, metrics, commands, and mechanism checks.training_trace.json with losses and parameter values before and after adaptation.source_manifest.json and generated skill invocation logs.module_plan.json fast recovery target.ok, metric gaps, mechanism failures, and recommended decision.loss_before and loss_after, plus params_before and params_after.accept only when executable evidence and mechanism checks pass.Run python scripts/evaluate_recovery.py --self-test. The self-test checks a valid proxy trace and an invalid unchanged-parameter trace.
This evaluator complements, but does not replace, Distiller's recovery experiment validator. Always run both in final recovery.
An unchanged-parameter ablation produced a refine decision; proxy acceptance must require parameter or optimizer-state change, not metric text alone.