Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .changes/work-items/feat-8650-ai-disclaimer-setting-5c2e9a41.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
bump: minor
---

### Added

- **`ai_disclaimer` setting.** Set it per user in `userConfig` or per repository in
`docs/conventions/work-items.yaml`, which wins; the schema gains the key.
`reference/ai-disclaimer.md` states the key, its layers and the prefix once, and every reader
points there.

### Changed

- **Lanes no longer prefix the AI disclaimer by default.** Triage, the work-loop intake sweep,
attend-queue answers and autonomous filing from `work` and `scan-todos` add it only when
`ai_disclaimer` resolves `true`; set it to keep the old behavior. A lane running on a person's
own `gh` token, with no `lane_app_slug`, now posts model-written items and comments under that
person's name with no AI marker at all; set `ai_disclaimer: true` there.
- **The work-loop objection window no longer treats an escalation's answer as a new objection.** A
comment answers the newest work-loop escalation marker only when that marker is newer than the
window comment, the comment comes before the autonomous-eligible role label was last applied,
and its author is the trusted labeler who applied it. An attend-queue answer without the
disclaimer does not re-escalate the item; any other comment in that span is still an objection.
- **The objection window no longer reads the AI disclaimer.** Who counts as a person rests on the
author alone (not the write identity, not a bot account): a comment carrying the prefix is still
a person's objection, since anyone can type it.
3 changes: 3 additions & 0 deletions docs/conventions/config-cascade/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ adding an optional layer or relaxing a rule additively is a minor bump.

No contract change.

- **`work-items` gains `ai_disclaimer`.** The Implementers row, renamed `work-items` (settings
keys), adds the key beside the triage keys; this repository's `docs/conventions/work-items.yaml`
now exists and sets it `false`.
- **`knowledge` gains Implementers and root-rule rows.** Its `upstream_records_dir` key lives in
`<home>/knowledge.yaml`, with no `userConfig` layer and no overlay, and a per-run `--out`
argument over it.
Expand Down
4 changes: 2 additions & 2 deletions docs/conventions/config-cascade/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -574,7 +574,7 @@ conformance.
| `repo-fleet-hygiene` | `--config` then team then user-global | whole-file, no per-key |
| `work-items` | overlay on the allowlist | per-key overlay |
| `work-items` (recurring schedule) | team only | single-layer |
| `work-items` (triage keys) | team | per-key |
| `work-items` (settings keys) | team | per-key |
| `songwriting` | project override over the bundled default | whole-file per template, no per-key |
| `ai-slop` | later layer | per-key (lists replace) |
| `docs-naming` | later layer; team on named policy-floor keys | per-key |
Expand Down Expand Up @@ -648,7 +648,7 @@ its conformance cell.
| `repo-fleet-hygiene` | no-floor | `.claude/repo-fleet-hygiene.conf` | user-global + team | `--config` then team then user-global | whole-file, no per-key | declared deviation; whole-file precedence (explicit `--config` > team > user-global fallback), no per-key merge, no overlay layer (#1099) |
| `work-items` | no-floor | `.work-item-tracker.json` (repo root) | team + local overlay | overlay on the allowlist | per-key overlay | declared deviation ([ADR 0015](../../adr/0015-bind-the-tracker-at-repo-root-with-an-allowlisted-personal-overlay.md)): layers live at the repo root, not under `.claude/`; overlay (`.work-item-tracker.local.json`) merges per-key over a deny-by-default allowlist (lease TTL, jira/linear/gitea auth identity, `docs`); deliberately no user-global layer, since a cross-repo personal rung would reopen the per-user provider trap the allowlist forecloses. Anchors at the repo root (`CLAUDE_PROJECT_DIR`, else git toplevel), no CWD climb. The overlay's gitignore line is outside the `.claude/**/*.local.*` one-liner, so `/work-items:setup apply` appends it, announced, a declared exception to the recommend default (ADR 0015) |
| `work-items` (recurring schedule) | no-floor | `.github/recurring-schedule.json` | team only | team only | single-layer | declared deviation ([ADR 0042](../../adr/0042-ratify-consumer-config-location-outliers-in-place.md)): the schedule lives under `.github/`, not `.claude/`, tracked and team-shared with no user-global layer and no overlay. Written by `track add` and `track recheck`; read by `track audit`, `done`, `due`, `search` and `stats`, by `work` candidate discovery, and by `setup`, which also writes it; anchors at `CLAUDE_PROJECT_DIR`, else git toplevel. Separate from the tracker binding row above |
| `work-items` (triage keys) | no-floor | team: `docs/conventions/work-items.yaml` (schema `plugins/work-items/schemas/work-items.schema.json`); per user: the plugin's `userConfig` option of the same name | `userConfig` + team | team | per-key | conforms to the [location axis](#location-of-the-team-layer-a-docs-convention-file-or-claudename) ([ADR 0064](../../adr/0064-home-plugin-customization-in-docs-conventions-yaml.md)), with the layer order of its Decision 8: the manifest default, then `userConfig`, then the team file; no `~/.claude` file and no overlay. Keys are `triage_repro_count` and `triage_objection_window_hours`. A value outside a key's range is named with its file, key and value, and that layer is dropped; the key then takes its manifest default, never a lower layer. The file is absent in this repository, so this row records a layer that is not tracked here. Read by `/work-items:triage` only, through `skills/triage/scripts/parse-concern-value.sh` from the repository root, or at a pinned ref under `--config-ref`; the `/work-items:work-loop` admission gate reads the window's end from the marker comment triage posts, not the file. Hand-edited, since `/work-items:setup apply` does not write this file yet |
| `work-items` (settings keys) | no-floor | team: `docs/conventions/work-items.yaml` (schema `plugins/work-items/schemas/work-items.schema.json`); per user: the plugin's `userConfig` option of the same name | `userConfig` + team | team | per-key | conforms to the [location axis](#location-of-the-team-layer-a-docs-convention-file-or-claudename) ([ADR 0064](../../adr/0064-home-plugin-customization-in-docs-conventions-yaml.md)), with the layer order of its Decision 8: the manifest default, then `userConfig`, then the team file; no `~/.claude` file and no overlay. Keys are `triage_repro_count`, `triage_objection_window_hours` and `ai_disclaimer`. A value outside a key's range is named with its file, key and value, and that layer is dropped; the key then takes its manifest default, never a lower layer. This repository's file sets `ai_disclaimer: false`. The triage keys are read by `/work-items:triage` only, through `skills/triage/scripts/parse-concern-value.sh` from the repository root, or at a pinned ref under `--config-ref`; the `/work-items:work-loop` admission gate reads the window's end from the marker comment triage posts, not the file. `ai_disclaimer` is read through the same script by each lane that follows `plugins/work-items/reference/ai-disclaimer.md`. Hand-edited, since `/work-items:setup apply` does not write this file yet |
| `songwriting` | no-floor | `songwriting/templates/pat-pattison/<name>.md` | team only, over a bundled default | project override over the bundled default | whole-file per template, no per-key | declared deviation ([ADR 0042](../../adr/0042-ratify-consumer-config-location-outliers-in-place.md)): the override path is under `songwriting/`, not `.claude/`. One tracked team file per template wins whole over `${CLAUDE_PLUGIN_ROOT}/context/pat-pattison/templates/<name>.md`, the first match, and freezes that template against plugin updates; no user-global layer and no overlay. The ADR rules on location only. Written by `/songwriting:setup apply`, read by the craft skills |
| `ai-slop` | no-floor | `.claude/ai-slop.json` | all three | later layer | per-key (lists replace) | conforms; per-key override, resolved by `/ai-slop:audit` (user-global, team, `.claude/ai-slop.local.json` overlay). Four list keys are additive-by-replacement rather than merged (`vocab_add` / `vocab_remove` tune the shipped word list, `phrase_add` / `phrase_remove` the shipped model-era phrase roster; the later layer's list wins per key). No policy-floor class: every key is a taste dial over prose style, and a personal overlay that silences a rule weakens nothing another surface depends on. Keys owned by `/ai-slop:setup`; `_comment` is an allowed free-text annotation, not drift |
| `docs-naming` | team-only | `.claude/docs-naming.json` | all three | later layer; team on named policy-floor keys | per-key | conforms, with the one sanctioned dual-read declared by retirement records `docs-naming-r001` and `docs-naming-r002` (the retired `.claude/docs-hygiene.json` and `.claude/docs-hygiene.local.json` are read as authority, with a WARN, only while the new name is absent); per-key override on `file_names.*`, with a policy-floor class on `tiers`, `generated`, `sweep_exclude`, `sweep_exclude_sites`, and the three `exempt_*` keys: a personal layer may ADD entries and never remove them, and `generated` is team-layer only. Those keys decide what `/docs-naming:realign-file-names` does to a tree (which files are frozen, which reference forms are rewritten, and which shell command runs after a move), so narrowing one from a single machine would weaken a team decision, while adding a scope root or an exemption weakens nothing and stays open. `rule`, `regex`, and `redirect_map` are nearest-wins. Keys owned by [`plugins/docs-naming/reference/config.md`](../../../plugins/docs-naming/reference/config.md), which also partitions them from plugin `userConfig` (this plugin declares none, so a layer naming one is an inert unknown key). Written by `/docs-naming:setup apply`, resolved by `plugins/docs-naming/scripts/resolve-config.sh` |
Expand Down
8 changes: 8 additions & 0 deletions docs/conventions/loop-lane/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,14 @@ topology, the escalation contract, the capability-tier vocabulary, or any loop-l
major bump, and additive guidance is a minor bump. A new model release re-audits the capability-tier
table (§3); drift found by that audit is recorded here.

## [12.7.0] - 2026-10-26

Minor. Guidance only; no topology, escalation-contract, capability-tier or §4 invariant changed.

- **AI disclaimer is a setting.** The attend-queue park and hold comments open with the AI
disclaimer only when work-items' `ai_disclaimer` setting resolves `true`; it defaults to `false`.
§4's lane-editable config adds that both lanes read `work-items.yaml` for the key (#8650).

## [12.6.0] - 2026-10-26

Minor. Guidance only; no topology, escalation-contract, capability-tier or §4 invariant changed.
Expand Down
7 changes: 4 additions & 3 deletions docs/conventions/loop-lane/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -900,7 +900,8 @@ offer to persist the answer; the headless path never waits on one.
time that the lane's own process could edit (audited in #7680). work-loop and attend-queue read
the tracker binding `.work-item-tracker.json` from the checkout, including the role labels that
admission matches on. The triage step they run reads `docs/conventions/work-items.yaml` and
`docs/conventions/pr-pipeline.yaml` from the working tree when no `--config-ref` is given. The
`docs/conventions/pr-pipeline.yaml` from the working tree when no `--config-ref` is given, and
both lanes read that `work-items.yaml` for `ai_disclaimer` the same way. The
babysit loop reads its `babysit_loop_*` keys from the `source-control` config seam's user-global,
team and local layers, and reads the team layer from the working tree when the checkout is the
target repository. A deny rule makes such a file read-only to a lane only when at least these four
Expand Down Expand Up @@ -1210,8 +1211,8 @@ gh issue comment <n> -R "$R" --body "Parked by operator: <reason>."

When an `attend-queue` session writes this comment, or the hold comment below, on the operator's
behalf, it opens with the
[AI disclaimer](../../../plugins/work-items/reference/ai-disclaimer.md); the operator's own words
need none.
[AI disclaimer](../../../plugins/work-items/reference/ai-disclaimer.md) when that file's setting
resolves `true`; the operator's own words need none.

`list-frontier --autonomous` excludes that label, so `work-loop` stops selecting the item from its
next cycle-start snapshot. The comment carries no machine marker, which is what marks the item
Expand Down
5 changes: 5 additions & 0 deletions docs/conventions/work-items.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# yaml-language-server: $schema=../../plugins/work-items/schemas/work-items.schema.json
# Team layer for the work-items plugin's settings.
# Resolution: plugins/work-items/reference/ai-disclaimer.md (ai_disclaimer).
# Autonomous lane posts here come from a bot account, whose author line already marks them.
ai_disclaimer: false
6 changes: 6 additions & 0 deletions plugins/work-items/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,12 @@
"default": 0,
"min": 0
},
"ai_disclaimer": {
"type": "boolean",
"title": "AI disclaimer on lane posts",
"description": "When true, autonomous work-items lanes (triage, work-loop, attend-queue answers, autonomous filing) start each tracker item and comment they create with the AI disclaimer. Default false, so lanes omit it. The repository's docs/conventions/work-items.yaml overrides this per repo.",
"default": false
Comment thread
kyle-sexton marked this conversation as resolved.
Resolved
Comment thread
kyle-sexton marked this conversation as resolved.
Resolved
},
Comment thread
kyle-sexton marked this conversation as resolved.
Resolved
Comment thread
melodic-automation-lanes[bot] marked this conversation as resolved.
Resolved
"work_dispatch_concurrency_cap": {
"type": "number",
"title": "Autonomous dispatch concurrency cap",
Expand Down
11 changes: 10 additions & 1 deletion plugins/work-items/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ off) have a repository layer as well: the same keys in the consuming repo's
`docs/conventions/work-items.yaml`, checked by
[`schemas/work-items.schema.json`](schemas/work-items.schema.json), win over the
per-user values. Lowest first: the manifest default, `userConfig`, the
repository file. Only `/work-items:triage` reads the file, through the bundled
repository file. Only `/work-items:triage` reads these two keys, through the bundled
`parse-concern-value.sh`, and reports which layer supplied each value; the
work-loop admission gate reads the window's end from the marker comment triage
posts. A lane that passes `--config-ref <ref>` to triage has the
Expand All @@ -185,6 +185,11 @@ triage posts an "Objection window until <UTC>" comment beside the brief of each
item it makes autonomous-eligible; the work-loop lane skips the item until the
window ends and escalates it if a person replies inside the window.

`ai_disclaimer` (default `false`) takes the same layers, in the same order:
when it resolves `true`, autonomous lanes start each tracker item and comment
they create with the AI disclaimer. The key, its layers and the prefix are
stated once in [`reference/ai-disclaimer.md`](reference/ai-disclaimer.md).

Everything else is project-specific behavior that routes through the consuming
repo's own surfaces: the bound provider in `.work-item-tracker.json` (including
the optional `config.role_labels` canonical-role → label remap), its labels
Expand Down Expand Up @@ -213,6 +218,9 @@ from being overwritten by another's.
**`work_loop_frontier_item_cap_ceiling`.** A quota guard: items carrying `capability-tier: frontier`
are bounded by this ceiling instead of the general one.

**`ai_disclaimer`.** The false default is a change on update: lanes always added the disclaimer
before this setting existed, so set it true to keep that behavior.

<!-- BEGIN GENERATED: plugin options. Edit plugin.json, then run scripts/sync-plugin-options-docs.py -->

### Options reference
Expand All @@ -226,6 +234,7 @@ reads it from.
| `decompose_container_publish` | boolean | *(none)* | `CLAUDE_PLUGIN_OPTION_DECOMPOSE_CONTAINER_PUBLISH` | When true, /work-items:decompose pre-selects the spec-container offer in its approval round for multi-session breakdowns; the approval gate stays mandatory. Unset or false: the plain ask, with a default answer of no. No default is declared, so unset stays distinct from false. |
| `triage_repro_count` | number<br>*min 1* | `2` | `CLAUDE_PLUGIN_OPTION_TRIAGE_REPRO_COUNT` | Independent reproductions /work-items:triage needs, each with evidence in its comment, before it marks a bug confirmed. Default 2. The repository's docs/conventions/work-items.yaml overrides this per repo. |
| `triage_objection_window_hours` | number<br>*min 0* | `0` | `CLAUDE_PLUGIN_OPTION_TRIAGE_OBJECTION_WINDOW_HOURS` | Hours after triage makes an item autonomous-eligible during which the work-loop lane skips it, so a person can object in a reply. 0 (the default) is off. The repository's docs/conventions/work-items.yaml overrides this per repo. |
| `ai_disclaimer` | boolean | `false` | `CLAUDE_PLUGIN_OPTION_AI_DISCLAIMER` | When true, autonomous work-items lanes (triage, work-loop, attend-queue answers, autonomous filing) start each tracker item and comment they create with the AI disclaimer. Default false, so lanes omit it. The repository's docs/conventions/work-items.yaml overrides this per repo. |
| `work_dispatch_concurrency_cap` | number<br>*min 1* | *(none)* | `CLAUDE_PLUGIN_OPTION_WORK_DISPATCH_CONCURRENCY_CAP` | Maximum worker rows /work-items:work's autonomous execute step lets /implementation:implement-dispatch run at once in one plan phase, passed as its --wave-cap ceiling. A fractional value is floored. Unset: implement-dispatch's implement_dispatch_wave_cap option, else its internal default. |
| `lane_instance` | string | *(none)* | `CLAUDE_PLUGIN_OPTION_LANE_INSTANCE` | Writer identity for this machine's work-loop telemetry, the suffix of its telemetry marker, so concurrent lane instances never overwrite each other. Absent: the sanitized lowercased hostname. Must match ^\[a-z0-9\]\[a-z0-9-\]{0,31}$. It appears verbatim in tracker comments. |
| `lane_app_slug` | string | *(none)* | `CLAUDE_PLUGIN_OPTION_LANE_APP_SLUG` | Slug of the GitHub App whose installation token the work-loop lane runs under, passed as --app-slug to its telemetry upsert so the write identity resolves to <slug>\[bot\]. Needed only under an App token. Absent: the identity resolves from gh api user. Must match ^\[a-z0-9\]\[a-z0-9-\]*$. |
Expand Down
Loading
Loading