Admission criteria
These are the rules every ecosystem uses to admit a source to its roster, and the reserved IDs and markings that limit how an opinion cites one. They live here once. Each ecosystem's AWESOME-HUMANS.md holds its roster tables, its Opted out section, its Source notes, and its decision log, and applies these rules to them.
To propose a source, suggest it for vetting. If you're a listed source and don't want your work cited, ask to opt out. For how both work, see Want in or out?
Track record
Scope: published writing. A source qualifies on text a reader can check: blog posts, documentation, books, and newsletters. Videos, conference talks, and podcasts are out of scope for now, both as citable material and as evidence of a track record. A source that moves to those formats stops qualifying, and becomes a vet-source candidate again if the writing resumes.
A source is the published work of an awesome human: a person or a publication. Admission needs an established track record:
- Longevity: At least two years of sustained publishing. A source with less goes on the watch list, however good the writing. The roster's
Sincecolumn shows how far back each record goes. - Depth: Original insight, such as internals, measurements, or worked reasoning. Paraphrased release notes don't count. A long-lived source with thin depth is admitted with the
**Corroborate.**marking, which limits how it's cited. - Accuracy: A history of being right, and of publishing corrections when wrong.
- Independence: The content stands on its merit, not on marketing reach.
Two rules qualify these criteria:
- An independence concern is a usage limit, not a lower rank. A concern is live when vendor developer relations, product-team work, or project marketing produces adoption-focused content with little critical distance. The source is still admitted, and its section under the roster's Source notes says what a citation can rest on, usually how something works, not whether to adopt it.
- Working for a vendor, or maintaining a package, isn't a concern by itself. Depth with critical distance needs no limit. A conflict is recorded where an opinion might recommend the source's own package or product.
- A concern that no limit could contain leads to a decline or the watch list.
- Dormancy blocks admission, with one exception. A candidate who hasn't published for over a year goes on the watch list, unless the person's writing clearly continues elsewhere, such as official documentation, another publication, or a book. Then the track record follows the person, and the notes record the dormant channel.
- Repository activity isn't evidence. Opinions don't cite commits, releases, or issue threads, so a busy GitHub profile beside a silent blog is still dormant.
- Documentation written in a repository counts. The test is what was published, not where the commits landed.
- The same rule triggers re-evaluation of admitted sources. For details, see
vet-source.
Each roster's Watch list tracks candidates that don't qualify yet, and vet-source re-evaluates them. An opt-out in one ecosystem covers all of them, so vet-source reads every roster's Opted out section before it gathers any evidence. The decision log at the end of each roster records every admission and demotion.
Reserved IDs, markings, and references
Reserved prefix: house:. A house profile's opinions use the source ID house:<profile>, such as house:simon-mckenna. A profile's authority is its owner's experience, not a track record, so it skips the admission criteria, and every house opinion is visibly marked instead. House opinions is the canonical definition of the marking, of how a house opinion sits beside the sourced text, and of contributor adoption. A house: ID never appears in the roster tables.
Reserved marking: **Discovery-only.**. Aggregators, such as link roundups, newsletters, and curated lists, are admitted for discovery and never cited. They lead to a primary source, and the opinion cites that. CI rejects the ID of a source whose notes carry this marking in any sources: list under opinions/ or templates/. Like **House:**, it's a fixed string, so a check can match it exactly.
Reserved marking: **Corroborate.**. Some sources have a long track record but thin depth: SEO-shaped roundups, course funnels, community catalogues, or release paraphrase with occasional substance. They're admitted and marked. The marking limits how you cite the source, not its standing. An opinion can cite it, but never alone: every claim it supports also needs an unmarked citable source. just validate-sources rejects an opinion or template whose citable sources are all marked. Neither a house: ID nor a Discovery-only ID counts as the unmarked source.
References: a named package's own material. When an opinion or template names a package, you can link the project's own material inline as a reference: its documentation site or in-repository docs, its generated API documentation, release notes and changelogs, issues and pull requests, or its page on the package registry. The standard behind a named format or protocol qualifies on the same terms, such as an RFC or the IANA time zone database. An ecosystem's AWESOME-HUMANS.md can name more that qualify, for what they record.
- A reference corroborates a claim and never carries it. It can confirm how something is set up, what it supports, and where it falls short, but the claim still rests on a roster source. A package's own material never decides whether to adopt that package.
- A reference needs no
vet-sourcepass and never appears insources:, sojust validate-sourcesdoesn't see it. - Cite it in the same
Source: Titleform as anything else, as in[xUnit.net: Testing with Native AOT].