<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02069nam a2200301Ia 4500</leader>
  <controlfield tag="003">MX-MdCICY</controlfield>
  <controlfield tag="005">20260521091532.0</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">CICY</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">B-16629</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Inhibition Mechanism of an Anti-CRISPR Suppressor AcrIIA4 Targeting SpyCas9</subfield>
  </datafield>
  <datafield tag="490" ind1="0" ind2=" ">
    <subfield code="v">Molecular Cell, 67(1), p.117-127.e5, 2017</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Prokaryotic CRISPR-Cas adaptive immune systems utilize sequence-specific RNA-guided endonucleases to defend against infection by viruses, bacteriophages, and mobile elements, while these foreign genetic elements evolve diverse anti-CRISPR proteins to overcome the CRISPR-Cas-mediated defense of the host. Recently, AcrIIA2 and AcrIIA4, encoded by Listeria monocytogene prophages, were shown to block the endonuclease activity of type II-A Streptococcus pyogene Cas9 (SpyCas9). We now report the crystal structure of AcrIIA4 in complex with single-guide RNA-bound SpyCas9, thereby establishing that AcrIIA4 preferentially targets critical residues essential for PAM duplex recognition, as well as blocks target DNA access to key catalytic residues lining the RuvC pocket. These structural insights, validated by biochemical assays on key mutants, demonstrate that AcrIIA4 competitively occupies both PAM-interacting and non-target DNA strand cleavage catalytic pockets. Our studies provide insights into anti-CRISPR-mediated suppression mechanisms for inactivating SpyCas9, thereby broadening the applicability of CRISPR-Cas regulatory tools for genome editing.</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ACRIIA4</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ANTI-CRISPR PROTEIN</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">CAS9</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">CRISPR RNA</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">CRISPR-CAS</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ENDONUCLEASE</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">GENOME EDITING</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">RUVC</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">TARGET DNA CLEAVAGE</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">TRANS-ACTIVATING CRRNA</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Yang, H.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Patel, D.J.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://drive.google.com/file/d/1fsUqfX3fWNfkbOGceFMhah5WPA9fQkr3/view?usp=drivesdk</subfield>
    <subfield code="z">Para ver el documento ingresa a Google con tu cuenta: @cicy.edu.mx</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">Loc</subfield>
    <subfield code="c">REF1</subfield>
  </datafield>
  <controlfield tag="008">250602s9999    xx |||||s2   |||| ||und|d</controlfield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">26738</subfield>
    <subfield code="d">26738</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">Loc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">F1</subfield>
    <subfield code="a">CICY</subfield>
    <subfield code="b">CICY</subfield>
    <subfield code="c">RE</subfield>
    <subfield code="d">2025-06-25</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">B-16629</subfield>
    <subfield code="r">2025-06-25 16:01:55</subfield>
    <subfield code="w">2025-06-25</subfield>
    <subfield code="y">REF1</subfield>
  </datafield>
</record>
