<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="/v2/static/oai2.xsl"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-10-06T12:36:39Z</responseDate>
  <request identifier="oai:figshare.com:article/34037049" metadataPrefix="oai_dc" verb="GetRecord">https://api.figshare.com/v2/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:figshare.com:article/34037049</identifier>
        <datestamp>2026-09-30T22:36:18Z</datestamp>
        <setSpec>category_29185</setSpec>
        <setSpec>category_29188</setSpec>
        <setSpec>item_type_9</setSpec>
        <setSpec>month_year_09_2026</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Artifact for "Verifying Fault Robustness by Type Checking: A Verified Information-Flow Approach" (VMCAI 2027, paper #3141)</dc:title>
          <dc:creator>Vadim Zaliva (25146471)</dc:creator>
          <dc:creator>Valerii Huhnin (25146480)</dc:creator>
          <dc:creator>Jeffrey S. Foster (25146483)</dc:creator>
          <dc:subject>Formal methods for software</dc:subject>
          <dc:subject>Programming languages</dc:subject>
          <dc:subject>fault robustness</dc:subject>
          <dc:subject>information-flow analysis</dc:subject>
          <dc:subject>type systems</dc:subject>
          <dc:subject>formal verification</dc:subject>
          <dc:subject>Lean 4</dc:subject>
          <dc:subject>artifact evaluation</dc:subject>
          <dc:description>&lt;p&gt;Artifact for the VMCAI 2027 paper &lt;em&gt;Verifying Fault Robustness by Type Checking: A Verified Information-Flow Approach&lt;/em&gt;. Poison is a core imperative language whose type system tracks faulty (sentinel) values through data and control flow by information flow. The artifact contains the Ott specification, a Lean 4 executable typechecker and interpreter, the mechanised proof that type checking enforces fault robustness (no sorry, standard axioms only), and 111 example programs used as a test suite.&lt;/p&gt;&lt;p&gt;The archive contains a Docker image (linux/amd64, project prebuilt and tested), the sources, a README with instructions, and logs. Requirements: x86-64, 16 GB RAM, 4+ cores recommended, about 13 GB disk for the loaded image; no network needed after loading.&lt;/p&gt;</dc:description>
          <dc:date>2026-09-30T22:36:18Z</dc:date>
          <dc:type>Software</dc:type>
          <dc:type>Software</dc:type>
          <dc:identifier>10.6084/m9.figshare.34037049.v1</dc:identifier>
          <dc:relation>https://figshare.com/articles/software/Artifact_for_Verifying_Fault_Robustness_by_Type_Checking_A_Verified_Information-Flow_Approach_VMCAI_2027_paper_3141_/34037049</dc:relation>
          <dc:rights>MIT</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
