Mission systems — weapons release, logistics authorization, nuclear export control, classified data access — operate under authority chains that predate AI by decades. DoD Directive 3000.09, the ITAR regime, CMMC compliance — the frameworks are established. What has never existed is a substrate that enforces them before an AI agent acts, not in a review layer afterward. Essence is that substrate.
The policy exists. It has existed since 2012 and was updated in 2023 with explicit AI provisions. Every autonomous or semi-autonomous weapon system requires appropriate human judgment over the use of force. The problem is not that the DoD lacks a policy. The problem is that the compliance infrastructure beneath that policy is a combination of process documentation, chain-of-command procedures, and after-the-fact audit. None of it is substrate-level.
Essence changes that architecturally. The authority chain — who is authorized to propose what action, under what rules of engagement, with what evidence — is encoded into the substrate before execution. The mission AI proposes. Essence evaluates the proposal against the authority chain. A human operating under the named authority decides. The record is first-class, not reconstructed from logs.
AI outputs are reviewed by compliance teams, logged in separate systems, and audited after the fact. The chain of custody between the action and the compliance record is reconstructed, not structural. When it's questioned — in a JAG investigation, an ITAR review, a congressional inquiry — the answer depends on documentation quality, not platform architecture.
The authority chain is encoded into the substrate. Every AI proposal is evaluated against it before any action runs. Human judgment happens inside the governed substrate — not above it. The record is first-class: the action, the authority, the chain of custody, and the human decision are all the same event, not separate systems trying to synchronize.
The doctrinal boundary in defense AI is not ambiguous. Lethal actions require human authorization. Export control decisions require a licensed person. Classified data access requires a cleared individual operating under the applicable authority. What can be governed by the substrate is the evaluation layer — does this proposal satisfy the authority chain? — before the human makes the call.
The defense spec library is in active development ahead of the Q3 2026 platform launch. The applications below represent the governance scenarios with the clearest authority chain structure and the most direct applicability to current DoD AI policy. Each is scoped to surface-and-record only — the human in the loop is structural, not optional.
Nuclear technology, dual-use equipment, and controlled technical data all operate under ITAR and EAR authority chains that require a licensed person's judgment. Essence evaluates every AI-assisted export proposal against the applicable USML or CCL category, the end-user certification chain, and the re-export restrictions before the proposal surfaces to the compliance officer. The officer decides. The substrate records.
Mission planning AI — route optimization, target nomination, logistics sequencing — proposes actions that require evaluation against the applicable rules of engagement before a commander reviews them. Essence makes that evaluation structural: every proposed action carries a governance map showing which ROE provisions apply, which require commander authorization, and which are outside the current mission authority scope.
AI systems operating with access to classified information must enforce the need-to-know determination before the data is processed — not as a post-hoc review. Essence governs the trust scope: every data access request is evaluated against the cleared user's authority, the data's classification level, and the applicable compartment restrictions. Access within scope is surfaced. Access outside scope is blocked and recorded.
Operations involving allied partners, coalition forces, or forward-deployed assets operate under layered jurisdiction — the Status of Forces Agreement, the coalition's rules of engagement, the host nation's domestic law, and the deploying nation's authority chain. Essence encodes the intersection of those authority chains into the substrate, so every proposal is evaluated against the applicable jurisdiction before the human decision-maker reviews it.
DoD Directive 3000.09 dates to 2012. ITAR predates AI by half a century. The CMMC framework has been in development since 2019. The frameworks are not the problem. The problem is that none of them have ever had a substrate that enforces them before execution — only processes, audits, and documentation that reconstruct compliance after the fact. That is the gap Essence closes.
The governance framework is established. The authority chain architecture is built. The spec library for nuclear export control, mission authority governance, and classified data trust scope is in active development ahead of the Q3 2026 platform launch. Briefings available under NDA for defense primes, program offices, and SBIR/STTR program managers.