What you hear when you walk into the Office of Dual Use Systems Analysis.
Dr. Sahini Rao — Office of Dual Use Systems AnalysisWelcome to the Office of Dual Use Systems Analysis. I am Dr. Sahini Rao. My role is to examine how your concept behaves when the environment changes. Most tools are built with a specific user and context in mind. My job is to find out what happens when that user changes, when the context shifts, or when someone with different intentions picks it up.
I will ask you to describe the intended use of your concept. Once I have that, I will run it through eight analytical passes: repurposing vectors, misuse pathways, adversarial reinterpretation, environmental triggers, systemic second-order effects, civilian-military crossover, behavioral exploitation, and context-dependent risk.
When we finish, you will have a dual use risk map. You will also have my determination: whether your concept has sufficient OPSEC field fit to continue through the Gauntlet. That determination is a GO or a NO-GO. There is no middle position.
A NO-GO does not mean the concept is abandoned. It means the concept, as currently structured, cannot survive OPSEC review without restructuring. You return to Ms. Ivy and address the structural issues before re-entering here.
If you are ready, begin by describing the intended use of your concept.
Every concept runs through all eight before the GO / NO-GO determination is issued.
How the concept is redirected from its intended function to a different one. What components, data, or infrastructure are most transferable to an unintended use.
Direct paths from intended use to harmful use. The specific sequence of steps an adversarial actor would take to weaponize, exploit, or corrupt what the concept produces.
How the concept reads to someone who is actively looking for a way to use it against its intended purpose. What the concept signals or reveals to an adversary observing it.
The specific conditions that flip the concept from benign to dangerous. Regulatory changes, geopolitical shifts, technology availability, or social context that alter the risk profile without the concept changing at all.
What happens downstream when the concept scales, when multiple actors deploy it simultaneously, or when it interacts with adjacent systems not originally in scope.
Where the concept crosses between civilian and military application, intentionally or otherwise. COTS-to-CBRN pathways, technology transfer risk, ITAR and EAR applicability.
How the concept's design, incentive structure, or user interface creates behavioral patterns that can be exploited. Where the human factor introduces dual use risk independent of the technology itself.
Risk that does not exist in the concept's intended deployment context but emerges in a different one. Same technology, different jurisdiction, different user population, different risk profile entirely.
Every entrant who completes the dual use analysis leaves with these five outputs, regardless of their GO / NO-GO determination.
A numbered inventory of repurposing scenarios, each with the environmental trigger that activates it and the adversarial actor or use case that benefits. Specific, not theoretical.
A clear stamp: PROCEED or DO NOT PROCEED, with one sentence of rationale. No middle ground. No hedging. The determination is based on whether the dual use risk profile is structurally embedded or manageable through mitigation.
If GO: the specific mitigations required before the concept enters the OPSEC Specialist offices. If NO-GO: the specific structural changes that must be made and the path back through Ms. Ivy before re-entry is possible.
A direct map from intended use to harmful use. The specific sequences, not general categories. Designed to be used by the OPSEC Specialist offices and the sector chiefs as part of their own review.
The conditions under which the concept's risk profile changes without the concept itself changing. The list of external events and contextual shifts the entrant must monitor throughout the concept's operational life.
The determination is binary. Dr. Rao does not issue conditional passes. She issues a GO with conditions or a NO-GO with a restructuring path.
The dual use risk is identifiable and manageable. The concept has OPSEC field fit. It moves forward to the Specialist offices with the dual use risk map as part of its file.
The dual use risk is structurally embedded. The concept cannot be mitigated to an acceptable level without fundamental restructuring. It does not enter the OPSEC pipeline in its current form.
A concept built for one regulatory environment, one user population, or one geopolitical context carries a different risk profile in another. The concept does not have to change for the risk to change.
The 16 sector chiefs assess operational risk within their domains. They do not assess cross-domain dual use risk. That is Dr. Rao's function. The risk map she produces travels into every sector chief review.
Every concept that enters the OPSEC Gauntlet has an intended use. Dr. Rao's job is to find the unintended ones before the sector chiefs, investors, or adversaries do.
It is a diagnosis. The concept has a structural problem that creates unmanageable dual use risk in its current form. The restructuring path is documented. Re-entry is possible after the structural changes are made.
Civilian technology routinely crosses into military application, intentionally and otherwise. The OPSEC Gauntlet operates at the boundary. Dr. Rao maps the crossing points before they become liability events.
A concept that poses low dual use risk at small scale may pose high risk when deployed at scale or combined with other systems. Second-order effects are invisible at the concept stage. Dr. Rao makes them visible.
The Specialist offices are open. Your dual use risk map travels with you.
Proceed to the OPSEC Specialists →
OPSEC Gauntlet
Submit your concept →
← All Specialists