CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

WFDC5

protein-coding gene in the species Homo sapiens

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJul 17, 2025
Entity authorityQ18051905 ↗
Source-derived summary

WAP four-disulfide core domain protein 5 is a protein that in humans is encoded by the WFDC5 gene.

This gene encodes a member of the WAP-type four-disulfide core (WFDC) domain family. Most WFDC proteins contain only one WFDC domain, and this encoded protein contains two WFDC domains. The WFDC domain, or WAP signature motif, contains eight cysteines forming four disulfide bonds at the core of the protein, and functions as a protease inhibitor. Most WFDC gene members are localized to chromosome 20q12-q13 in two clusters: centromeric and telomeric. This gene belongs to the centromeric cluster.

Editorial summary

The public source identifies “WFDC5” as protein-coding gene in the species Homo sapiens. This brief keeps that definition visible, then builds a research path around WFDC5, protein-coding and gene.

Editorial reviewA practical orientation to terminology and classification, particularly when read beside dated observations, specimens or technical literature. The current 95-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with WFDC5, protein-coding and gene providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “WFDC5”, the useful work is to connect “protein-coding gene in the species Homo sapiens” to the records capable of establishing context and consequence.

Evidence profile

Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Jul 17, 2025. The linked authority identifier is Q18051905. None of the 0 selected statements returned an explicit reference.

Critical limits

Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “WFDC5”, its source revision and the description used here.
  2. Expand the search: follow WFDC5 primary sources, WFDC5 archive and WFDC5 research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “WFDC5”?
  2. Is the terminology current, historical or disputed?
  3. Has classification or technical consensus changed since the cited source?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “WFDC5” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.