DCAF17 has an experimentally supported CUL4/DDB1 association, while its proposed substrate-recognition mechanism remains unresolved. Human 293T DDB1 affinity purification identified DCAF17 with seven peptides, followed by GST-DCAF validation in Figure 1E lane 10. These are cellular association experiments, not a purified binary-binding or substrate-transfer assay. The paper's Cdt2 substrate-destruction experiments do not establish the corresponding DCAF17 activity. PMID:16949367(https://doi.org/10.1016/j.molcel.2006.08.010)
The official products reconstruct to 520 and 240 residues; the short product is exactly the final 240 residues of the long sequence. The 2008 study reports both untagged beta and alpha products in nucleoli, with endogenous C2orf37/B23 colocalization and peptide-competition controls. GFP fusion instead caused aggregation and nuclear disruption, so it is not the positive localization evidence. Both predicted long-product helices are deleted in the short sequence. The study does not establish membrane insertion, nor does transcription-blockade sensitivity settle a specific RNA-processing or ribosome-biogenesis activity. PMID:19026396(https://doi.org/10.1016/j.ajhg.2008.10.018)
The official HPA record independently reports Supported nucleoplasmic localization. Nucleoplasm excludes the nucleolus in the GO definition, so these are retained as separate observed contexts. HPA antibody images were not independently inspected and its signal does not distinguish the two products. The five Reactome sources contain literal paths through the CRL4 complex and DCAF set to DCAF17/Q5H9S7 in nucleoplasm. Their UBE2M, CAND1, COMMD and COP9 mechanisms are not assigned to DCAF17 simply because it is present. HPA DCAF17, Reactome DCAF17
Mouse Dcaf17 exon-4 deletion causes male infertility and prominent post-meiotic sperm-development defects. Histology, alpha-tubulin staining and electron microscopy support the spermatogenesis annotation as a contextual role. These experiments do not show direct DCAF17-microtubule binding or an identified ubiquitination substrate. The paper explicitly proposes its CUL4 connection as a hypothesis. Its later correction concerns author indexing only. PMID:29907856(https://doi.org/10.1038/s41598-018-27379-0), PMID:30068992(https://www.nature.com/articles/s41598-018-29836-2)
Later mouse testis RNA-seq and proteomics add downstream expression and protein-abundance changes. The 2022 study discusses indirect effects and cell-composition differences. The 2025 abstract reports increased bulk ubiquitin signal, but its full text and PDF were inaccessible in this review. Neither source provides an inspected DCAF17 substrate-recruitment or ubiquitin-transfer assay. Their positive contextual evidence is retained without converting it into a demonstrated molecular mechanism. PMID:36509865(https://pubmed.ncbi.nlm.nih.gov/36509865/), PMID:40449516(https://doi.org/10.1080/19396368.2025.2504459)
All 15 genuine seeded source objects are retained exactly. Ten are accepted, one generic binding row is refined to GO:0097602 cullin family protein binding, two are kept as contextual positives, and two remain undecided. The uncertainties concern membrane topology and the performed ubiquitination role. No new annotation is proposed. The one core summarizes cullin association and CUL4 membership; it does not assign substrate-adaptor or ligase activity. Its nucleoplasmic context follows HPA and Reactome, without asserting that the association experiment was localized to nucleoli or demonstrated separately for both products.
The actual 48-node PTHR14815 tree places human PTN002495134 below PTN001028294. The literal IBD at that ancestral node assigns GO:0080008 with Q5H9S7 as descendant evidence, supported by its direct human IDA source. This is legitimate self-grounded inheritance, not circular evidence. The target alignment sequence matches the long product. The electronic ubiquitination mapping names IPR031620 and UPA00143, not an ARBA rule. The family description itself qualifies substrate-receptor function as possible.
Both current Complex Portal variants are curator-inferred. The CUL4A association is more explicit in the original validation; CUL4B membership is retained contextually with that limit. A weaker panel signal is not treated as absence. Complex-level ubiquitin-ligase terms are not automatically molecular functions of every participant. CPX-2415, CPX-2416
The source guide supplies public original URLs, figure/section locators, product distinctions and literal Reactome paths. It is authored navigation rather than an independent primary source. Current contextual interaction records do not include a literal PMID16949367 pair; that database coverage limit does not overturn the recovered original experiment.
The normal gene and publication fetches were actually run in an isolated workspace. Falcon authentication failed, and the configured Perplexity-lite fallback returned an insufficient-quota error. No provider report was generated or replaced with authored text. The manual review therefore records its own source access explicitly.
An independent annotation/core consultation recovered the 2006 and 2008 author PDFs and assessed eight source rows. The owner independently read the decisive original Methods/Results/Discussion passages and inspected Figure 1C/E and Figure 4 pixels, then integrated the other seven rows, mouse literature, HPA, products, PAINT and Reactome evidence. The normal caches for both recovered papers remain abstract-only and unchanged; original access does not silently rewrite cache metadata. The 2018 and 2022 mouse papers were read at selected cached Methods/Results/Discussion scope, without figure-pixel or supplement inspection. The 2025 source is abstract-only. No equivalent activity of both human products is inferred from their shared antibody epitope or sequence segment.
The independently generated PMID15815621 cache is byte-identical to the existing pending CYP4V2 cache. It was obtained through the normal fetch mechanism, not copied from the pending proposal. Original source snapshots and runtime tooling are preserved for publication qualification. Whole-review and normal-check outcomes will be appended after the immutable scientific draft is assessed.
The ordinary status updater, default validation, CI-equivalent source/schema/reference/term validation, status check, explicit term validation and rendering all completed successfully. The updater genuinely derived COMPLETE from an absent inherited status. The membrane and protein-ubiquitination annotations remain UNDECIDED; the derived workflow status does not resolve those biological uncertainties. There were no gene-validation advisories. A dependency deprecation notice during term validation is preserved in the execution log.
All 15 original source objects, the two reconstructed product identities, 37 protected original files and 291 runtime files remained exact. No source or ontology-cache restoration was needed. The only scientific-YAML successor leaf is INITIALIZED to derived COMPLETE. The public guide and both supporting excerpts are unchanged. The final notes were rendered again after this append so the published page includes this outcome. Independent full-review acceptance and current publication applicability are recorded separately by the publishing reviewer.
The original notes above remain the historical record. This follow-up addresses review 5549462344, detail 6218002398 and their four inline comments on the submitted DCAF17 review.
The single cullin-association core now includes nucleolus as well as nucleoplasm. The original PMID19026396 supports nucleolar localization of both untagged products in HEK293 cells and endogenous protein with B23 in lymphoblasts (author PDF pages 2–6, Figure 4). These are independent protein-localization observations, not evidence of a nucleolar ubiquitination reaction. The HPA nucleoplasm record was inspected; its antibody images were not. The earlier guide intentionally limited the core to nucleoplasm, but that representation omitted the strongest experimentally characterized protein location.
Membrane row 9 remains UNDECIDED. The long product has two predicted hydrophobic helices, and UniProt explicitly records their conflict with the nucleolar results. The short product lacks both helices. Insertion, topology and product-specific partitioning remain unresolved. This is an affirmative conflict in the available evidence, not an absence-of-disproof argument. UNDECIDED permits genuine uncertainty as well as requiring caution when relevant text is inaccessible; both primary localization and association originals were read here.
CUL4B membership row 12 changes from KEEP_AS_NON_CORE to ACCEPT, aligning it with CUL4A. PMID16949367 Figure 1E lane 10 and the explicitly curator-inferred CPX-2415/2416 entries support association with both assemblies. Relative band intensity is not a quantified biological distinction between core and contextual membership. One generic CUL4 core remains. DDB1 association is supported by the same original, including seven peptides in Figure 1C, but DDB1 is not a cullin and is not covered by GO:0097602. A bounded official GO search did not establish a suitable DDB1-specific binding descendant; no replacement or new term is invented.
Ubiquitination row 10 remains UNDECIDED. Noncatalytic structural or substrate-recruitment contributions can satisfy participation, but association alone does not identify which step DCAF17 performs. The published substrate-turnover experiments concern Cdt2; the mouse transcriptome/proteome findings do not resolve a DCAF17 substrate or assembly contribution. Complex membership remains positive without assigning the complex's catalytic activity to DCAF17. Product descriptions now state product biology concisely; the unresolved 2006 clone sequence and untested equivalence of the two products remain in the guide and review context. The exploratory PMID15815621 cache is preserved without adding it as a supporting formal reference.
All 15 source objects, 17 reference identities and existing quoted excerpts are preserved. There is one core and no NEW annotation. Only CUL4B membership changes action. Normal status, validation, rendering and append-only history will be handled by ROOT against the accepted final application boundary.