aidd-lint tier2 candidate: ambiguous-target-or-scope #140
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#140
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
An instruction's object is underspecified (which files, which directory, how many) so two competent agents would act on different sets.
Why it matters
Scope ambiguity leads to non-deterministic behavior and incomplete execution. Agents need explicit boundaries.
Provenance
Proposed by external review (Codex, GPT-5.6 tier) on 2026-07-26; zero observed instances in this repo yet; candidate only.
Status
Candidate, subject to promotion threshold: at least 5 confirmed positives across at least 3 files and at least 2 repos (no more than 2 from the originating file), at least 10 hard negatives, dual-reviewer agreement, roughly 90% precision / 80% recall on a held-out eval, and no regression on existing categories. See ADR-0060 for closed-catalog gate.
decision recorded — evidence-collection sweep of a second repo dispatched before any admission; rule remains a candidate.
Second-repo evidence sweep complete (~/dev/cc-plugins, 36 files + ruby-gems fallback): 0 confirmed positives — every work-set-determining hedge had an in-file resolver (4 near-misses documented in session). Admission bar (≥5/≥3 files/≥2 repos) not met; remains a candidate. Calibration note: authors resolve genuine ambiguity in-file, so expected fire rate is low.
Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.