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
docs(planning): point draft-goal-condition's ultracode lines at the docs without losing behavior offline #12357
#12272 measured cutting both to pointers. The cut showed a loss, so it was left out: the skill could not read the pointers with network access denied.
Done when
The two lines become pointers the skill can still act on with network access denied (for example a local record the skill reads), or the eval case runs with docs access. Either way, the eval case exercises the changed lines; plugins/planning/evals/dg-workflow-keyword-unattended (from fix(discovery,planning): point setup's fork default at the docs and add two eval cases #12272) is the existing one.
Before and after are measured on VALID runs (run-validity.py), with a negative control per /playbooks:skill-authoring's rewrite-a-plugin reference. The change ships only on no loss; a loss is recorded here.
Each shipped pointer carries an as-of date and a recheck trigger (.claude/rules/skill-bodies-state-current-rules.md).
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: two restated upstream facts in the draft-goal-condition skill (where the ultracode keyword works, and plan availability and the xhigh condition) should become pointers that still work with network access denied. The change ships only if before and after measurements on valid runs show no loss, and each pointer carries an as-of date and a recheck trigger.
Nothing is missing. The choice between a local record the skill reads and running the eval case with docs access is an implementation choice. I would suggest the local record, since the skill must still act offline. The measured runs may need a host or paid eval, which admission can route separately. No duplicates found among the open issues.
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
Claimed by lane 1 (melo-lap-001, hub assignment 2026-11-02 16:5xZ). Plan: local pointer record the skill reads offline, before/after on VALID runs with a negative control via plugins/planning/evals/dg-workflow-keyword-unattended. Ships only on no loss.
Lane 1: PR #12426 merged (2ab3443). It ships the keyword and plan-availability moves into reference/workflow-row.md, measured with no loss and network access denied (before 1/1/1, after 1/1/1, negative control 0.44). The xhigh clause stays in SKILL.md, now with a pointer, an as-of date and a recheck trigger. Moving it failed preregistered measurement v5: three correct answers failed the line-based grader, so the xhigh case read 0.70 against 1.00. Remaining on this issue: move the xhigh clause once #12467 makes the graders read answers that span lines, then measure again. Lane 1 releases its claim.
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: two restated upstream facts in the draft-goal-condition skill (where the ultracode keyword works, and plan availability and the xhigh condition) should become pointers that still work with network access denied. The change ships only if before and after measurements on valid runs show no loss, and each pointer carries an as-of date and a recheck trigger.
Nothing is missing. The choice between a local record the skill reads and running the eval case with docs access is an implementation choice. I would suggest the local record, since the skill must still act offline. The measured runs may need a host or paid eval, which admission can route separately. No duplicates found among the open issues.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 2, 2026
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 2, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.kyle-sexton commentedon Nov 2, 2026
Claimed by lane 1 (melo-lap-001, hub assignment 2026-11-02 16:5xZ). Plan: local pointer record the skill reads offline, before/after on VALID runs with a negative control via plugins/planning/evals/dg-workflow-keyword-unattended. Ships only on no loss.
test(planning): add an eval case for the standing ultracode xhigh con…
test(planning): stop the xhigh grader passing "it works" answers
test(planning): stop the xhigh grader passing a conditional hedge
test(planning): fit the xhigh grader to every observed reply
test(planning): spell behavior the repo way in an xhigh sample
docs(planning): keep the ultracode xhigh condition in the skill body
test(planning): tighten the xhigh grader's clause and sentence bounds
docs(planning): give the restored xhigh condition its record
kyle-sexton commentedon Nov 2, 2026
Lane 1: PR #12426 merged (2ab3443). It ships the keyword and plan-availability moves into
reference/workflow-row.md, measured with no loss and network access denied (before 1/1/1, after 1/1/1, negative control 0.44). Thexhighclause stays in SKILL.md, now with a pointer, an as-of date and a recheck trigger. Moving it failed preregistered measurement v5: three correct answers failed the line-based grader, so thexhighcase read 0.70 against 1.00. Remaining on this issue: move thexhighclause once #12467 makes the graders read answers that span lines, then measure again. Lane 1 releases its claim.test(planning): reject hedged and denied claims in the keyword and xh…