From 708427bbf1cf0f0efec86d86cd3f0ffce900cfb8 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Wed, 5 Aug 2026 03:06:30 -0400 Subject: [PATCH 1/2] docs(autonomy): correct the goal glossary row's terminator claim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `reference/routines.md`'s `goal` row claimed the session runs "until a separate grader judges the condition met or a budget cap trips". The official page states a closed two-item set — "A goal keeps running until the condition is met or you run `/goal clear`" — and the section on bounding a goal's duration offers a turn or time clause inside the condition, not a spend cap. The page's only `budget` occurrence is a file-size budget in an example condition. The one dollar cap Claude Code documents is the `--max-budget-usd` CLI flag: print-mode-only and invocation-scoped, while this row is `session-scoped`. A cap-stopped invocation also leaves the goal neither achieved nor cleared, so it is restored on `--resume`/`--continue` — the cap ends the process while the goal outlives it. The replacement clause names the second of the two events that actually change goal state, making the cell complete rather than merely minimal. Co-authored-by: Claude Opus 5 --- plugins/autonomy/CHANGELOG.md | 14 ++++++++++++++ plugins/autonomy/reference/routines.md | 2 +- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/plugins/autonomy/CHANGELOG.md b/plugins/autonomy/CHANGELOG.md index 4f89233e6..248bfc0bc 100644 --- a/plugins/autonomy/CHANGELOG.md +++ b/plugins/autonomy/CHANGELOG.md @@ -6,6 +6,20 @@ All notable changes to the `autonomy` plugin are documented here. Format follows Versions 0.1.0–0.7.0 predate this file (introduced with 0.7.1); their history lives in the merged work-package PRs (#333, #343, #356, #372, #377, #600, #676). +## [VERSION-PENDING] + +### Fixed + +- **`reference/routines.md`: the `goal` glossary row no longer claims a budget cap ends the + session.** The row read "until a separate grader judges the condition met or a budget cap trips"; + the official page documents a closed two-item set — "A goal keeps running until the condition is + met or you run `/goal clear`" — and its own section on bounding a goal's duration offers a turn or + time clause inside the condition, not a spend cap. The only dollar cap Claude Code documents is + the `--max-budget-usd` CLI flag, which is print-mode-only and invocation-scoped, whereas this row + is `session-scoped`; a cap-stopped invocation also leaves the goal neither achieved nor cleared, + so it is restored on `--resume`/`--continue` — the cap ends the process while the goal outlives + it. The replacement clause names the second of the two events that actually change goal state. + ## [0.12.0] ### Changed diff --git a/plugins/autonomy/reference/routines.md b/plugins/autonomy/reference/routines.md index 449ae9d24..ac35c1a4f 100644 --- a/plugins/autonomy/reference/routines.md +++ b/plugins/autonomy/reference/routines.md @@ -45,7 +45,7 @@ fire fresh ones. | Term | Family | Meaning | |---|---|---| | `loop` | session-scoped | repetition on an interval inside one session; dies with the session | -| `goal` | session-scoped | completion condition — the session keeps going until a separate grader judges the condition met or a budget cap trips | +| `goal` | session-scoped | completion condition — the session keeps going until a separate grader judges the condition met or the goal is cleared | | `batch` | session-scoped | parallel fan-out over decomposed units of one brief; NOT bulk-inference batch APIs (a corrected research conflation) | | `dynamic workflow` | session-scoped | orchestration whose decomposition and sub-steps the session composes at run time; ends with the session | | `schedule` | standing | the standing time trigger | From 178cee2e931132a745e3f7d977f15a4bdebbc515 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Wed, 5 Aug 2026 10:17:16 -0400 Subject: [PATCH 2/2] chore(autonomy): apply the allocated 0.12.2 version bump Literal allocated centrally by the orchestrator (one in-flight claim per plugin; 0.12.1 is claimed by open PR #1934). Co-authored-by: Claude Opus 5 --- plugins/autonomy/.claude-plugin/plugin.json | 2 +- plugins/autonomy/CHANGELOG.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/autonomy/.claude-plugin/plugin.json b/plugins/autonomy/.claude-plugin/plugin.json index 2c1b8ceea..18c0a833b 100644 --- a/plugins/autonomy/.claude-plugin/plugin.json +++ b/plugins/autonomy/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", "name": "autonomy", - "version": "0.12.0", + "version": "0.12.2", "description": "Governed autonomous agent operation: role-topology, binding-seam, wiring-vs-advisor, telemetry, return-accounting, trigger-dispatch, per-work-class guardrail-matrix, standing-routine-catalog, and design-only runner-charter contracts for climbing the AI-adoption ladder, plus a guided-setup skill that discovers an adopting org's state, writes its schema-versioned binding, wires standards-pinned OTLP emission with a zero-cost file-artifact default, wires human-attested return capture at the task boundary, wires signal adapters with one governed dispatch entrypoint, binds the five-class guardrail matrix to an org's isolation substrates with an in-boundary live-validation probe before recording each fail-closed binding, and stands up standing-routine-catalog classes as scheduled temporal signal adapters behind the one governed queue with free scheduling defaults wired as reviewable changes and each routine's work-class mapping homed on the security surface.", "author": { "name": "Melodic Software", diff --git a/plugins/autonomy/CHANGELOG.md b/plugins/autonomy/CHANGELOG.md index 248bfc0bc..ea3e09fb4 100644 --- a/plugins/autonomy/CHANGELOG.md +++ b/plugins/autonomy/CHANGELOG.md @@ -6,7 +6,7 @@ All notable changes to the `autonomy` plugin are documented here. Format follows Versions 0.1.0–0.7.0 predate this file (introduced with 0.7.1); their history lives in the merged work-package PRs (#333, #343, #356, #372, #377, #600, #676). -## [VERSION-PENDING] +## [0.12.2] ### Fixed