The Standard

No competitor in this space publishes its link-integrity and identity-verification provenance. The Allodium does, for every entry, because a resource list is only as trustworthy as the checks behind it.

How an entry is verified

Identity check: For entries carrying a DOI, the stored title is compared against publisher metadata from Crossref and OpenAlex. A confirmed match is recorded as identity: ok; a strong mismatch is demoted for review rather than published as-is.
Legitimacy triage: Entries are screened for topical relevance, source legitimacy, and identity agreement. Screens that don't clear a confidence threshold are marked needs_review rather than kept, the default when a check is uncertain is exclusion, not inclusion.
Link health: Outbound links are checked and labeled ok, blocked, or unchecked. A dead link is removed from the public set entirely; a blocked link (for example, one behind a bot check) stays listed but is clearly marked inconclusive rather than presented as broken or as working.

Every check above is a normalized, timestamped record. See the "Verification" section on any entry page. Automated checks are not endorsement or advice.

Coverage

Live coverage numbers, identity checks, legitimacy triage, link health, identifiers, modalities, and exclusions. Live on each collection's landing, because they describe that collection's snapshot. See Psychotherapy for the current published set.

Cross-field federation coverage, upstream status, and known blind spots are published separately on the Open Index coverage page.

Credibility signals, not a blacklist

Federated results are not admitted or rejected by a hidden gate. Each result carries an expandable, versioned set of metadata signals: DOI registration, recognized venue and institution records, access and license information, publication version, metadata completeness, and Retraction Watch notices.

Absence from DOAJ, MEDLINE, OpenAlex, ROR, or another allow-list is neutral. It is never presented as evidence that a work or publisher is not credible.
Retractions and expressions of concern remain searchable and are shown as prominent warnings; the historical record is not erased.
The Allodium does not use proprietary or unlicensed predatory-publisher lists. Their licensing, false-positive, and defamation risks are incompatible with a transparent public index.
A score describes available metadata evidence. It does not assess methods, reproduce results, or endorse conclusions.

Current federated policy: 1.0.0. Every displayed signal names its evidence source and license.

Limitations

Checks are automated and deterministic where possible; they are not a substitute for reading the source or for professional judgment.
A blocked link means the automated check was inconclusive (for example, a bot wall), not that the resource is gone. Verify manually if it matters for your use case.
No full text, abstracts, or stored files are published here, just index metadata and an outbound link to the original source.

Optional AI-assisted search

Search has an optional plain-language field. Keyword and facet search always work without it.

The model is qwen2.5:7b-instruct-q6_k, running on Selis. The Worker sends only the visitor's ask text (capped), never PDFs, abstracts, or other unpublished fields.
Suggested filters are re-validated against the public index; unknown tokens are dropped.
If the GPU is offline, times out, or otherwise fails for a reason other than abuse rate-limiting, results fall back to plain keyword search.
This is not therapy or clinical advice. Phrases that look like crisis intent skip the model and show the existing 988 copy.

Verified Sourcepaths

Verified means we ran and show these checks, not that The Allodium endorses a publisher or grants permission to call their URL. This section is an index, not a mirror: we publish titles, artifact URLs, hashes, and check history, and we do not store artifact bodies.

A direct URL is not permission. A blocked row is inconclusive (access blocked), not confirmed dead.

Update cadence

Each public snapshot is regenerated from its source catalog and redeployed as a whole, coverage numbers on a collection landing always describe exactly the entries currently live, not a newer or older dataset.