Skip to content

Adopt the /source-queue skill and a licence-verified data-source queue #722

Description

@realmarcin

CellStructureMech and AntibioticMech each keep curation/source_queue.tsv — a
ranked list of the data sources the corpus draws on or might adopt, with each
source's licence verified before anything is copied. CommunityMech has no equivalent.

Why this is not a file copy

The skill is five parts, and only some of them are shareable:

part whose
the TSV schema, vocabularies and adoption gate shared — now kg-microbe-source-queue check in claw (culturebotai-claw#274)
curation/source_queue.tsv rows yours — which sources, ranked by which gaps
the ranking rule's gap list yours — what this corpus cannot currently assert
licence verification per source yours — read each source's own licence page
just source-queue wiring yours, one recipe

The rows are the work. Ranking sources by the gap they close for
microbial communities, and verifying each licence against the source's own page rather
than a summary, is curation — which is why claw's manifest currently records
this repository as source_queue: disabled with that reason, rather than
pretending a copied file would do.

The shared half, already available

uv run kg-microbe-source-queue check --mech <name>

It checks the eleven columns both existing queues share, one spelling per licence
class, and the adoption gate: an ADOPTED source must have a verified
redistribution class and the date it was verified, plus anything else this
repository decides to require.

A deliberate non-rule: a candidate may say use: SEED while its
redistribution is still UNVERIFIED. That is the normal state before anyone
has read the licence, and an earlier version of the check reported twelve such
rows across both real queues as violations. The gate applies at adoption.

Why it is worth having

The queue is where "what should we add next?" gets answered with evidence rather
than enthusiasm, and where a licence that forbids redistribution gets caught
before content is copied into a repository — which matters here, since the
corpus is redistributed.

To adopt

  1. Create curation/source_queue.tsv with the eleven shared columns, plus any
    this corpus needs (CellStructureMech adds taxon_link, item_id,
    script; AntibioticMech adds structures).
  2. Fill it with this repository's real candidates, ranked by gap.
  3. Declare source_queue: enabled in claw's manifest with the path and any
    extensions.
  4. Wire just source-queue to the shared checker.

Read CellStructureMech's .claude/skills/source-queue/SKILL.md for the ranking
rule and the adoption gate; the gaps, licences and traps in it are that
repository's and should not be copied.

Activity

  1. realmarcin commented on Aug 31, 2026

    @realmarcin
    ContributorAuthor

    Added a guide that separates the shared half from yours, so this does not mean reverse-engineering another Mech's SKILL.md: docs/guides/SOURCE_QUEUE.md in claw (culturebotai-claw#277).

    It states the eleven columns, the four vocabularies, the ranking rule and the adoption gate as shared and enforced — and marks explicitly as yours, with the reason each is wrong to copy:

    • the gap list, which is why two repositories rank the same source differently;
    • the licence tensions — a CC0 repository hosting CC BY images has a problem a citing-only one does not;
    • the known traps, each of which earns its place by having cost someone time;
    • the rows.

    It also records the one thing an adopter is most likely to get wrong: a candidate may say use: SEED while its redistribution is still UNVERIFIED. That is the normal state before anyone has read the licence, and it is not a finding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions