Development record
The source vocabulary has no member for a finding an autonomous bug-hunt loop files, and a downstream loop wrote source autonomous-hunt, which the reader refuses and skips. Decomposed out of iss-2609120452071388 when its code halves were fixed, because this half is a closed-vocabulary ruling for the product thinker, not an implementer's fix: either such a loop uses an existing member (agent-finding is the nearest) or autonomous-hunt joins issueschema.Sources, with record-lint and the help text following from the one list. Until it is ruled, a record carrying it is skipped with the schema layer named on the board.
The source vocabulary has no member for a finding an autonomous bug-hunt loop files, and a downstream loop wrote source autonomous-hunt, which the reader refuses and skips. Decomposed out of iss-2609120452071388 when its code halves were fixed, because this half is a closed-vocabulary ruling for the product thinker, not an implementer's fix: either such a loop uses an existing member (agent-finding is the nearest) or autonomous-hunt joins issueschema.Sources, with record-lint and the help text following from the one list. Until it is ruled, a record carrying it is skipped with the schema layer named on the board.
Remedy grounds (2026-09-29)
- Why: the record's two answers, each with the one place it changes; the vocabulary is a single list at internal/core/issueschema/issueschema.go, so either answer is small. The ruling is unanswered and none is picked.
- Rejected: accepting unknown sources leniently, which would undo the closed vocabulary the reader enforces.
Frontmatter
| id | iss-2609251151293535 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2609251151293535-the-source-vocabulary-has-no-member-for.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2609120452071388Reported from a downstream repository using abcd, where `abcd capture` (bare,