No -deep-research-PROVIDER.md exists for this gene: deep-research tooling was
unavailable (the configured OpenAI key is rejected). Per repository policy no
self-authored file was named as provider output. The review rests on the cached
publications, all of which were present for the PMIDs GOA cites, plus five papers
fetched during the work.
GOA carries GO:0016263 on Cosmc as NOT|enables. Read without the negation
flag this looks like a textbook necessity-mistaken-for-possession error: the IMP
behind it measured T-synthase activity in patient cells and found it reduced.
It is the opposite — the curators drew exactly the right distinction. Worth
remembering that the review-stub seeding does carry negated: true correctly;
the trap is reviewer-side, in reading the row before the flag.
An early draft of this review asserted Cosmc has "no glycosyltransferase fold".
That is wrong, and the local UniProt record says so plainly:
SIMILARITY — "Belongs to the glycosyltransferase 31 family. Beta3-Gal-TCAUTION — "Was originally (PubMed:12361956) assigned to be aSo Cosmc is a degenerate GT31 member that retains the family relationship while
having lost catalysis. This matters for the negation's value: family- and
sequence-based inference will keep proposing the activity because it is GT31,
and only an explicit NOT stops it.
Relevant to the project's cazy2go work, where GT31 is already flagged
narrowMatch as too heterogeneous to propagate at family level — a GT31 member
with zero activity is about as strong an argument for that flag as the family
can supply.
Three GOA rows placed Cosmc in the Golgi. The compartment was inherited from its
client's reaction (Reactome models the Golgi-lumenal transfer). Cosmc's own ER
residence is not merely asserted in review prose:
Note UniProt asserts only the generic "Membrane" and commits to neither
compartment, so correcting Golgi → ER does not contradict it.
GO:0044183 protein folding chaperone is the term used. Not GO:0051082
unfolded protein binding, which an OpenScientist run recommended: that term is
obsolete (QuickGO returns "obsolete unfolded protein binding"), a known problem
tracked in issue #2222.
Whether a dedicated single-client chaperone should carry involved_in on the
process it enables. GOA itself is unsettled — it uses involved_in on two rows
and acts_upstream_of_or_within on a third. The existing rows are accepted, but
core_functions.directly_involved_in is deliberately not asserted: Cosmc
catalyses no step and contributes neither structure nor cofactor activity to the
glycosyl transfer, which is the same standard used to demote GCNT1's leukocyte
tethering and C1GALT1's angiogenesis in this batch.
function-hypothesis-go-0016263 (verdict SUPPORTED) and
function-hypothesis-go-0000139 (verdict refuted, i.e. not Golgi). The first
supplied the GT31 correction above; the second surfaced PMID:21262965. Both
reports' claims were re-checked against local records before use, and both
carry reference_review notes recording what each got wrong as well as right.