Five open records carry remedies that name verbs or pages itd-2610090831227812 retired with no alias on 2026-10-09: iss-25 and iss-52 name abcd source add (iss-52 also source ledger), and iss-92, iss-2608210934566220 and iss-2610040350491915 name prepare-this-repo, so a lane applying any of them targets a command that no longer exists; nothing checks a remedy against the retired names.

Frontmatter

.abcd/work/issues/open/iss-2610241549433260-five-open-records-carry-remedies-that.md
open on GitHub ↗ · commit history ↗

mentions6

• iss-25related_sources frontmatter for record-store documents (intents, ADRs, research notes): machine-readable acknowledgment of the sources that informed a document — public sources by CSL key, confidential sources by a random opaque per-source id assigned at ingest (NEVER a content hash: hashing an obtainable document is verifiable by outsiders and breaks confidentiality). Needs schema sanction in record-lint, an id-resolution path via the local corpus, and add-source generating ref_id. Complements the ledger's used_in field (the corpus-side half, already shipped).
• iss-52Every corpus source carries an epistemic tier — peer-reviewed, preprint, practitioner, or ai-generated — recorded at ingest time and surfaced by consult, so that the trust level of a source travels with the source rather than living in the reader's head. The convention serves evidence discipline: AI-generated sources support nothing on their own and may only corroborate claims grounded elsewhere, and a consult result that hides tier invites laundering weak evidence into strong claims. Detector: the ledger lint refuses influence edges whose source lacks a tier; acceptance is an ingest path that cannot register a source without one and a consult output that displays it.
• iss-92Maintainer hunch (record only; do not implement, and map against SOTA during design per prefer-sota). Onboarding should follow a strict playbook that identifies every non-standard file in a target repo (e.g. Manuscripts WORKLOG.md, DECISIONS.local.md, SLICE_START), matches each against abcd canon, and proposes where it belongs -- presented interview-style so the maintainer picks from a recommended default they can accept or override (verifier-selects-gates-decide). This generalises the narrower worklocal-nonstandard-members-no-migration finding into the adopt-phase UX. The interview mechanism is a hypothesis, not a decision: the SOTA for convention-onboarding/scaffolding UX must be researched and adversary-filtered for fit before adopting. Detector/acceptance (to firm at design): an adopt run that emits a per-non-standard-file placement proposal with a recommended default the user accepts or overrides.
• iss-2608210934566220The six bundled OPINIONS rules each end with a pointer to a file under .abcd/development/principles/ that exists only in the abcd repo itself — a managed repo inherits the injected lines verbatim, so every prompt whose recall matches the domain hands its agent six dangling references (the principles corpus is not part of adoption). Either the bundled lines need self-contained phrasings with the pointer marked as abcd-repo-only, or adoption (prepare-this-repo / ahoy) should ship a distilled principles set the pointers can resolve against. Found while adding the memory-graduation rule, whose line was written self-contained for exactly this reason
• iss-2610040350491915itd-2610030814013772 criterion A1 says 'when setup runs, then it writes AGENTS.md' with the example 'after setup in a new folder the root holds AGENTS.md', confirmed by the product thinker on 2026-10-03, but a bare setup writes no AGENTS.md: docsTargetDefault is skip (internal/core/ahoy/detect.go), so only an install at --docs-target agents_md, or prepare-this-repo, creates the file. The fidelity audit of 2026-10-04 judged A1 MET_WITH_CONCERNS on that difference. The spec (spc-2610031156364295, open design question 1) chose reading (a), keeping the standing ruling that a default install names abcd in no committed conventions file (iss-2609110944498549), and the facilitator decided it without a question; the criterion's example, as the product thinker confirmed it, reads the other way. Either the example is confirmed as holding at agents_md only, or the default is reopened; today the record carries both.
• itd-2610090831227812A person who types `/abcd:` sees the commands people use