\relax 
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong, direct opening. Sets scope immediately.}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid1}{12703339}{44941311}
\pgfsyspdfmark {pgfid4}{31254300}{44915575}
\pgfsyspdfmark {pgfid5}{35899615}{44675891}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider: ``operators'' appears 3x in two sentences. Maybe: ``Based on these procedures and their interpretation of plant conditions, they make critical decisions...''}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid6}{24172130}{41140223}
\pgfsyspdfmark {pgfid9}{31254300}{41114487}
\pgfsyspdfmark {pgfid10}{35899615}{40874803}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``But, reliance'' — the comma after ``But'' is unusual. Either drop it or restructure: ``However, this reliance...'' or ``This reliance, however, has created...''}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid11}{12694016}{39239679}
\pgfsyspdfmark {pgfid14}{31254300}{34211341}
\pgfsyspdfmark {pgfid15}{35899615}{33971657}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ ``are needed that can'' — passive. Try: ``Autonomous control systems must safely manage...''}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid16}{9008701}{35438591}
\pgfsyspdfmark {pgfid19}{31254300}{28106555}
\pgfsyspdfmark {pgfid20}{35899615}{27866871}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear statement of approach.}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid21}{8902520}{32587775}
\pgfsyspdfmark {pgfid24}{31254300}{23730167}
\pgfsyspdfmark {pgfid25}{35899615}{23490483}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Nice parallel structure showing the gap.}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid26}{11177092}{27836415}
\pgfsyspdfmark {pgfid29}{31254300}{22027649}
\pgfsyspdfmark {pgfid30}{35899615}{21787965}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This paragraph is dense. Consider breaking after the three stages, then a new paragraph for the compositional verification point and Emerson demo.}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid31}{4749422}{12632063}
\pgfsyspdfmark {pgfid34}{31254300}{12606327}
\pgfsyspdfmark {pgfid35}{35899615}{12366643}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``can be used for'' — weak. Try: ``...will demonstrate that autonomous control can manage complex nuclear power operations while maintaining safety guarantees.'' Or even stronger: ``...enables autonomous management of complex nuclear power operations with safety guarantees.''}{i}{}\protected@file@percent }
\pgfsyspdfmark {pgfid36}{26033217}{11681791}
\pgfsyspdfmark {pgfid39}{31254300}{6594471}
\pgfsyspdfmark {pgfid40}{35899615}{6354787}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good practical framing — emphasizes accessibility.}{ii}{}\protected@file@percent }
\pgfsyspdfmark {pgfid41}{14318560}{45891583}
\pgfsyspdfmark {pgfid44}{31254300}{45865847}
\pgfsyspdfmark {pgfid45}{35899615}{45626163}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong industrial grounding — the ``platforms they already use'' point is compelling for adoption.}{ii}{}\protected@file@percent }
\pgfsyspdfmark {pgfid46}{6062694}{33538047}
\pgfsyspdfmark {pgfid49}{31254300}{33512311}
\pgfsyspdfmark {pgfid50}{35899615}{33272627}
\@writefile{toc}{\contentsline {section}{Contents}{iii}{}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {1}Goals and Outcomes}{1}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear thesis statement. Gets right to it.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid51}{7637198}{43613118}
\pgfsyspdfmark {pgfid54}{31254300}{43587382}
\pgfsyspdfmark {pgfid55}{35899615}{43347698}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Stakes established immediately — good hook.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid56}{12512020}{40762302}
\pgfsyspdfmark {pgfid59}{31254300}{40736566}
\pgfsyspdfmark {pgfid60}{35899615}{40496882}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ The ``and'' here joins two distinct issues (autonomy barrier + economics). Consider making the causal link explicit: ``This reliance on human operators not only prevents autonomous control capabilities but also creates...'' or split into two sentences.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid61}{7381388}{34110398}
\pgfsyspdfmark {pgfid64}{31254300}{34084662}
\pgfsyspdfmark {pgfid65}{35899615}{33844978}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``What is needed is'' — Gopen would call this a weak topic position. The sentence buries the subject. Try: ``Autonomous control systems must safely manage complex operational sequences...'' Puts the actor in the topic position.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid66}{23610026}{29359038}
\pgfsyspdfmark {pgfid69}{31254300}{24507646}
\pgfsyspdfmark {pgfid70}{35899615}{24267962}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Excellent setup of the gap — shows why neither approach alone is sufficient.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid71}{5491809}{20806590}
\pgfsyspdfmark {pgfid74}{31254300}{15674808}
\pgfsyspdfmark {pgfid75}{35899615}{15435124}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Hypothesis is clear and testable.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid76}{4791893}{15104958}
\pgfsyspdfmark {pgfid79}{31254300}{12336822}
\pgfsyspdfmark {pgfid80}{35899615}{12097138}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This qualifications paragraph feels orphaned here. It's important context but reads as an afterthought. Consider integrating it into the approach paragraph (``...demonstrated on Emerson hardware through our partnership with the Cyber Energy Center'') or moving to a ``Why This Will Succeed'' framing later.}{1}{}\protected@file@percent }
\pgfsyspdfmark {pgfid81}{10973961}{10353598}
\pgfsyspdfmark {pgfid84}{31254300}{9890126}
\pgfsyspdfmark {pgfid85}{35899615}{9650442}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``cold shutdown through criticality to power operation'' — concrete and impressive scope.}{2}{}\protected@file@percent }
\pgfsyspdfmark {pgfid86}{9648007}{27836415}
\pgfsyspdfmark {pgfid89}{31254300}{27810679}
\pgfsyspdfmark {pgfid90}{35899615}{27570995}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear ``what's new'' statement.}{2}{}\protected@file@percent }
\pgfsyspdfmark {pgfid91}{4050292}{21282815}
\pgfsyspdfmark {pgfid94}{31254300}{21257079}
\pgfsyspdfmark {pgfid95}{35899615}{21017395}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong closing — ties technical work to real-world impact and economic necessity.}{2}{}\protected@file@percent }
\pgfsyspdfmark {pgfid96}{18900337}{13680639}
\pgfsyspdfmark {pgfid99}{31254300}{13654903}
\pgfsyspdfmark {pgfid100}{35899615}{13415219}
\citation{NUREG-0899,10CFR50.34}
\citation{10CFR55.59}
\citation{WRPS.Description,gentillon_westinghouse_1999}
\@writefile{toc}{\contentsline {section}{\numberline {2}State of the Art and Limits of Current Practice}{3}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good roadmap — tells reader exactly what's coming.}{3}{}\protected@file@percent }
\pgfsyspdfmark {pgfid101}{21980756}{40762302}
\pgfsyspdfmark {pgfid104}{31254300}{40736566}
\pgfsyspdfmark {pgfid105}{35899615}{40496882}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Current Reactor Procedures and Operation}{3}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ This paragraph is doing a lot. Consider splitting: first paragraph on the hierarchy and compliance, second on the lack of formal verification. The ``No mathematical proof exists...'' sentence is powerful and deserves emphasis.}{3}{}\protected@file@percent }
\pgfsyspdfmark {pgfid106}{20423612}{24880744}
\pgfsyspdfmark {pgfid109}{31254300}{24855008}
\pgfsyspdfmark {pgfid110}{35899615}{24615324}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ This repeats the ``No mathematical proof exists...'' sentence almost verbatim from the paragraph above. Either cut it from the paragraph or from the LIMITATION box.}{3}{}\protected@file@percent }
\pgfsyspdfmark {pgfid111}{13626615}{17278568}
\pgfsyspdfmark {pgfid114}{31254300}{16022170}
\pgfsyspdfmark {pgfid115}{35899615}{15782486}
\citation{operator_statistics}
\citation{10CFR55}
\citation{10CFR50.54}
\citation{Kemeny1979}
\citation{WNA2020}
\citation{hogberg_root_2013}
\citation{zhang_analysis_2025}
\citation{Kiniry2024}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This is the key insight — the hybrid nature is already there, just not formally verified.}{4}{}\protected@file@percent }
\pgfsyspdfmark {pgfid116}{14097656}{42090495}
\pgfsyspdfmark {pgfid119}{31254300}{42064759}
\pgfsyspdfmark {pgfid120}{35899615}{41825075}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Human Factors in Nuclear Accidents}{4}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong thesis for this subsection.}{4}{}\protected@file@percent }
\pgfsyspdfmark {pgfid121}{5927496}{30010025}
\pgfsyspdfmark {pgfid124}{31254300}{29984289}
\pgfsyspdfmark {pgfid125}{35899615}{29744605}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``the person responsible for reactor safety is often the root cause of failures'' — devastating summary. Very effective.}{4}{}\protected@file@percent }
\pgfsyspdfmark {pgfid126}{4915358}{19557033}
\pgfsyspdfmark {pgfid129}{31254300}{19531297}
\pgfsyspdfmark {pgfid130}{35899615}{19291613}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Strong empirical grounding. The Chinese plant data is a nice addition — shows this isn't just a Western regulatory perspective.}{4}{}\protected@file@percent }
\pgfsyspdfmark {pgfid131}{4609444}{10054313}
\pgfsyspdfmark {pgfid134}{31254300}{10028577}
\pgfsyspdfmark {pgfid135}{35899615}{9788893}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Well-stated. The ``four decades'' point drives it home.}{4}{}\protected@file@percent }
\pgfsyspdfmark {pgfid136}{4792689}{5302953}
\pgfsyspdfmark {pgfid139}{31254300}{4760899}
\pgfsyspdfmark {pgfid140}{35899615}{4521215}
\citation{Kiniry2024}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}Formal Methods}{5}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2.3.1}HARDENS}{5}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good technical depth on HARDENS toolchain.}{5}{}\protected@file@percent }
\pgfsyspdfmark {pgfid141}{20999294}{21457577}
\pgfsyspdfmark {pgfid144}{31254300}{21431841}
\pgfsyspdfmark {pgfid145}{35899615}{21192157}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear articulation of the gap your work fills.}{5}{}\protected@file@percent }
\pgfsyspdfmark {pgfid146}{23128957}{11004585}
\pgfsyspdfmark {pgfid149}{31254300}{10978849}
\pgfsyspdfmark {pgfid150}{35899615}{10739165}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2.3.2}Sequent Calculus and Differential Dynamic Logic}{6}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{red!40}{\textcolor {red!40}{o}}\ Typo: ``ivariant'' should be ``invariant''}{6}{}\protected@file@percent }
\pgfsyspdfmark {pgfid151}{4749422}{20507305}
\pgfsyspdfmark {pgfid154}{31254300}{20481569}
\pgfsyspdfmark {pgfid155}{35899615}{20241885}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider adding a concrete example here — ``For instance, a system with N modes and M continuous state variables...'' to give readers a sense of the scaling problem.}{6}{}\protected@file@percent }
\pgfsyspdfmark {pgfid156}{18750152}{12905129}
\pgfsyspdfmark {pgfid159}{31254300}{12879393}
\pgfsyspdfmark {pgfid160}{35899615}{12639709}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ ``but are far from a complete methodology to design systems with'' — awkward ending preposition. Try: ``but remain far from a complete design methodology'' or ``but do not yet constitute a complete design methodology.''}{6}{}\protected@file@percent }
\pgfsyspdfmark {pgfid161}{8940582}{10054313}
\pgfsyspdfmark {pgfid164}{31254300}{5829135}
\pgfsyspdfmark {pgfid165}{35899615}{5589451}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Your comment here is spot-on. You should add a LIMITATION box: \textit  {Differential dynamic logic has been used for post-hoc analysis of existing systems, not for the constructive design of autonomous controllers.} This is exactly the gap you're filling — you're doing synthesis, not just verification.}{6}{}\protected@file@percent }
\pgfsyspdfmark {pgfid166}{14192475}{45403152}
\citation{HANDBOOK ON HYBRID SYSTEMS}
\@writefile{toc}{\contentsline {section}{\numberline {3}Research Approach}{8}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{orange!50}{\textcolor {orange!50}{o}}\ Missing space before ``Our}{8}{}\protected@file@percent }
\pgfsyspdfmark {pgfid167}{21351522}{32209854}
\pgfsyspdfmark {pgfid170}{31254300}{32184118}
\pgfsyspdfmark {pgfid171}{35899615}{31944434}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Simplified hybrid automaton for reactor startup. Each discrete state $q_i$ has associated continuous dynamics $f_i$. Guard conditions on transitions (e.g., $T_{avg} > T_{min}$) are predicates over continuous state. Invariant violations ($\neg Inv_i$) trigger transitions to the SCRAM state. The operational level manages discrete transitions; the tactical level executes continuous control within each mode.}}{9}{}\protected@file@percent }
\newlabel{fig:hybrid_automaton}{{1}{9}{Research Approach}{figure.1}{}}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This is your key insight — the novelty is compositional, not component-level.}{9}{}\protected@file@percent }
\pgfsyspdfmark {pgfid172}{5905037}{17221912}
\pgfsyspdfmark {pgfid175}{31254300}{17196176}
\pgfsyspdfmark {pgfid176}{35899615}{16956492}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}System Requirements, Specifications, and Discrete Controllers}{9}{}\protected@file@percent }
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Control scope hierarchy in nuclear power operations. Strategic control (long-term planning) remains with human management. HAHACS addresses the operational level (discrete mode switching) and tactical level (continuous control within modes), which together form a hybrid control system.}}{10}{}\protected@file@percent }
\newlabel{fig:strat_op_tact}{{2}{10}{System Requirements, Specifications, and Discrete Controllers}{figure.2}{}}
\citation{MANYUS THESIS}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Continuous Control Modes}{13}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ This three-mode taxonomy is elegant — maps verification tools to control objectives cleanly.}{14}{}\protected@file@percent }
\pgfsyspdfmark {pgfid179}{15985073}{33177599}
\pgfsyspdfmark {pgfid182}{31254300}{33151863}
\pgfsyspdfmark {pgfid183}{35899615}{32912179}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Transitory Modes}{14}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Stabilizing Modes}{15}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.3}Expulsory Modes}{16}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Industrial Implementation}{17}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{red!40}{\textcolor {red!40}{o}}\ Typo: ``excess should be ``access}{17}{}\protected@file@percent }
\pgfsyspdfmark {pgfid184}{25258844}{17656489}
\pgfsyspdfmark {pgfid187}{31254300}{17630753}
\pgfsyspdfmark {pgfid188}{35899615}{17391069}
\@writefile{toc}{\contentsline {section}{\numberline {4}Metrics for Success}{18}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ TRL as primary metric is smart — speaks industry language.}{18}{}\protected@file@percent }
\pgfsyspdfmark {pgfid189}{6508678}{41712574}
\pgfsyspdfmark {pgfid192}{31254300}{41686838}
\pgfsyspdfmark {pgfid193}{35899615}{41447154}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Good framing — explains why other metrics are insufficient.}{18}{}\protected@file@percent }
\pgfsyspdfmark {pgfid194}{7276206}{33160126}
\pgfsyspdfmark {pgfid197}{31254300}{33134390}
\pgfsyspdfmark {pgfid198}{35899615}{32894706}
\@writefile{toc}{\contentsline {paragraph}{TRL 3 \textit  {Critical Function and Proof of Concept}}{18}{}\protected@file@percent }
\@writefile{toc}{\contentsline {paragraph}{TRL 4 \textit  {Laboratory Testing of Integrated Components}}{18}{}\protected@file@percent }
\@writefile{toc}{\contentsline {paragraph}{TRL 5 \textit  {Laboratory Testing in Relevant Environment}}{19}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{yellow!60}{\textcolor {yellow!60}{o}}\ Consider noting why graded responses are out of scope — is it time, complexity, or scope creep? Brief justification helps.}{19}{}\protected@file@percent }
\pgfsyspdfmark {pgfid199}{15785403}{27497812}
\pgfsyspdfmark {pgfid202}{31254300}{27472076}
\pgfsyspdfmark {pgfid203}{35899615}{27232392}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear success criteria. Committee will know exactly what ``done'' looks like.}{19}{}\protected@file@percent }
\pgfsyspdfmark {pgfid204}{13547172}{12293460}
\pgfsyspdfmark {pgfid207}{31254300}{12267724}
\pgfsyspdfmark {pgfid208}{35899615}{12028040}
\@writefile{toc}{\contentsline {section}{\numberline {5}Risks and Contingencies}{20}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Honest acknowledgment of risks with clear contingencies — committee will appreciate this.}{20}{}\protected@file@percent }
\pgfsyspdfmark {pgfid209}{19227927}{44563390}
\pgfsyspdfmark {pgfid212}{31254300}{44537654}
\pgfsyspdfmark {pgfid213}{35899615}{44297970}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Computational Tractability of Synthesis}{20}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Discrete-Continuous Interface Formalization}{20}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Procedure Formalization Completeness}{22}{}\protected@file@percent }
\citation{eia_lcoe_2022}
\citation{eesi_datacenter_2024}
\citation{eia_lcoe_2022}
\@writefile{toc}{\contentsline {section}{\numberline {6}Broader Impacts}{24}{}\protected@file@percent }
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ ``If it works here, it works anywhere — strong closing argument.}{25}{}\protected@file@percent }
\pgfsyspdfmark {pgfid214}{19399794}{25935871}
\pgfsyspdfmark {pgfid217}{31254300}{25910135}
\pgfsyspdfmark {pgfid218}{35899615}{25670451}
\bibstyle{ieeetr}
\bibdata{references}
\@writefile{toc}{\contentsline {section}{\numberline {7}Schedule, Milestones, and Deliverables}{26}{}\protected@file@percent }
\gtt@chartextrasize{0}{164.1287pt}
\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Project schedule showing major research thrusts, milestones (orange row), and publications (green row). Red diamonds indicate completion points. Overlapping bars indicate parallel work where appropriate.}}{26}{}\protected@file@percent }
\newlabel{fig:gantt}{{3}{26}{Schedule, Milestones, and Deliverables}{figure.3}{}}
\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Milestones and Deliverables}{26}{}\protected@file@percent }
\bibcite{NUREG-0899}{1}
\bibcite{10CFR50.34}{2}
\bibcite{10CFR55.59}{3}
\bibcite{WRPS.Description}{4}
\bibcite{gentillon_westinghouse_1999}{5}
\bibcite{operator_statistics}{6}
\bibcite{10CFR55}{7}
\bibcite{10CFR50.54}{8}
\bibcite{Kemeny1979}{9}
\bibcite{WNA2020}{10}
\@writefile{tdo}{\contentsline {todo}{\fcolorbox {black}{green!40}{\textcolor {green!40}{o}}\ Clear timeline with publication targets — shows you have a plan.}{27}{}\protected@file@percent }
\pgfsyspdfmark {pgfid220}{4865044}{36388863}
\pgfsyspdfmark {pgfid223}{31254300}{36363127}
\pgfsyspdfmark {pgfid224}{35899615}{36123443}
\@writefile{toc}{\contentsline {section}{References}{27}{}\protected@file@percent }
\bibcite{hogberg_root_2013}{11}
\bibcite{zhang_analysis_2025}{12}
\bibcite{Kiniry2024}{13}
\bibcite{eia_lcoe_2022}{14}
\bibcite{eesi_datacenter_2024}{15}
\gdef \@abspage@last{32}