SOC 2

The 70-year legacy of nuclear machine learning While the tech world treats generative AI as a recent phenomenon, Los Alamos National Laboratory (LANL) has utilized applied statistics and machine learning since 1956. Architect Mark Myshatyn notes that the lab's first supercomputer, Maniac 1, ran chess simulations without enough memory to hold a full board. This deep history in Monte Carlo methods and high-performance computing (HPC) provides the foundation for today’s "agentic era," where AI isn't just a chatbot but a tool for physical science. Moving from chatbots to kinetic science agents The laboratory recently demonstrated an autonomous agent designed to solve Inertial Confinement Fusion (ICF) capsule problems for Lawrence Livermore National Laboratory. Unlike commercial LLMs that merely output text, this agent reads academic papers, generates hypotheses, and then executes code on Venado, an NVIDIA and HPE powered supercomputer. It runs thermodynamic and hydrodynamic tests to optimize designs, effectively integrating 60 years of nuclear stockpile stewardship into a real-time iterative workflow. The brutal reality of government compliance For developers entering the federal space, the regulatory hurdle is often a shock. Myshatyn highlights OMB Memorandum M-24-10 (frequently referenced as the April AI memorandum), which mandates that agencies accelerate AI adoption while managing "real-world impacts." This isn't about selling t-shirts; it’s about data that cannot ever see the internet. Providers must bridge the gap between commercial SOC 2 reports and the rigorous NIST 853 framework, which contains over 1,000 security controls. Furthermore, the DoD Cloud Computing Security Requirements Guide (CCSRG) adds layers of impact levels that many SaaS startups are unprepared to navigate. Four pillars for agentic partnerships To collaborate with entities like the National Security AI Office, Myshatyn defines four architectural mandates. First, **Explainability**: the lab must trust agents as much as human staff, especially regarding high-stakes decisions. Second, **Isolation**: tools must work in air-gapped environments without relying on hyperscaler clouds. Third, **Governance**: developers must provide a Software Bill of Materials (SBOM) and clear plans for patching open-source dependencies. Finally, **Speed**: federal versions of tools cannot lag years behind commercial releases. As Myshatyn puts it, the mission depends on using the most advanced math and science to protect national competitive advantage.