Deep research was unavailable in this environment (no provider API keys), so this file
is my own literature journal. Every assertion carries an inline PMID plus a verbatim
quote from the cached record in publications/.
PA14_33310, 342 aa, "CRISPR-associated protein Csy3" = Cas7f, the backbone subunit.
Six copies polymerise along the crRNA:
PMID:32170016, matching UniProt's stoichiometry
Csy1(1),Csy2(1),Csy3(6),Cas6/Csy4(1)-crRNA(1) and
PMID:32170016. A Csy3(6)·Cas6f(1)·crRNA(1) subcomplex also forms (UniProt
SUBUNIT), which is consistent with the IntAct Csy3–Cas6f pair behind GOA's two
GO:0005515 rows (Q02MM1–Q02MM2, NbExp=12). Original PA14 biochemistry:
PMID:21536913.
Binds and kinks the crRNA, non-sequence-specifically.
PMID:32170016 — backbone, not bases:
PMID:32170016. The kinking is the functional point, since it segments the guide:
PMID:32170016.
Pins the crRNA:target-DNA heteroduplex. This is the step that makes the backbone an
active participant in target verification rather than a scaffold:
PMID:28985564. The structures are of the PA14 complex:
PMID:28985564.
Carries the DNA-binding surface of the backbone.
PMID:32170016.
Cas7f is the principal anti-CRISPR target surface of this system, which is why the
module calls it "the surface bound by AcrIF8 and related inhibitors":
PMID:32170016 — and the
inhibitors compete for the very residues above:
PMID:32170016. This is consistent
with the completed phage-side review genes/BPZF4/AcrF8/AcrF8-ai-review.yaml, which
records AcrIF8 contacting both the Cas7f backbone and the crRNA.
Csy3 is required for spacer acquisition — a gene-specific deletion, which is the
grounding for the CACAO IMP:
PMID:26586803, in a system where
PMID:26586803.
Csy3 is not in the strict-requirement class for crRNA accumulation:
PMID:21398535 — so its GO:0043571 annotation is earned by the
acquisition phenotype, not by a crRNA-biogenesis phenotype.
GO:0005515 protein binding rows (IPI, partner Cas6f) → MODIFY toGO:0005198 structural molecule activity. Cas7f is the structural element: sixAspect correction (follow-up). My first pass proposed
part_of GO:0032991 protein-containing complex as the replacement, reasoning from the
E. coli comparator where all five Cascade subunits carry exactly that. That was wrong
in form: these GOA rows carry qualifier: enables, so they are molecular-function
rows, and a gene product cannot enable a cellular component. However
well-supported complex membership is, it cannot be expressed by swapping a CC term
into an enables MF row. The E. coli reviews were not making this mistake — their
GOA already contained separate part_of GO:0032991 rows, which they MODIFY to
GO:1990904; their enables GO:0005515 rows went to GO:0005198 instead.
Reconciled to the same convention:
enables rows to GO:0005198 structural molecule activity ("theNEW part_of GO:1990904 ribonucleoprotein
complex row. PA14 has no part_of complex row for any Csy subunit, unlike allGO:1990904 rather than the bare GO:0032991 root because thecore_functions[].in_complex → GO:1990904 for the same reason.proposed_new_terms entry for a "CRISPR RNA-guided surveillanceGO:1990904, identical in substance to the one the fiveGO:0099048, GO:0043571,GO:0098672 and the obsolete GO:0110132/GO:0110133); ComplexPortal models theGO:0043571 maintenance of CRISPR repeat elements, IMP,acts_upstream_of_or_within_positive_effect → ACCEPT. A clean csy3 deletionGO:0003723 RNA binding (NEW, IDA, PMID:32170016). Comparator: casC (Cas7e,GO:0003723 by IDA (PMID:25103409), as do casA, casD and casE. TheGO:0071667 DNA/RNA hybrid binding (NEW, IDA, PMID:28985564). Comparator: this isGO:0099048 CRISPR-cas system (NEW, IDA). Comparator: all five E. coli CascadeGO:0099048 is not an ancestor or descendant ofGO:0043571 or GO:0051607.GO:0003677 DNA binding. The lysine-rich patch is described as critical for DNAGO:0071667, which is what I propose.core_functions as acontributes_to_molecular_function instead.GO:0051607 defense response to virus. No csy3 allele has been assayed for phagecas3-notes.md).modules/crispr_cas_adaptive_immunity.yaml andmodules/anti_crispr_suppression.yaml, and raised in suggested_questions rather