Defense
Your AI proposes the controlled action. The record shows a named person reviewed it.
Authority to operate is becoming a standing evidentiary burden, not a one-time gate. A policy is a promise. A sealed record of who reviewed each controlled action is evidence.
Controlled sharing
The program's marking review
The export-control officer
Sealed
The duty
The burden sits with the program, not the vendor.
Fielded defense AI runs under rules that ask the program office to show the review happened.
| Rule | What it asks |
|---|---|
| ITAR | Control who receives U.S. Munitions List technical data, including the deemed-export boundary for model artifacts. |
| DFARS 252.204-7012 | Safeguard controlled unclassified information and report cyber incidents within 72 hours. |
| CMMC | Cybersecurity maturity at Level 1, 2 or 3, shown to an assessor with evidence. |
| ATO | Route security evidence to the authorizing official and keep it current after the decision. |
| NIST AI RMF | Operate the Govern, Map, Measure and Manage functions, not just document them. |
| DoW RAI S&IP | AI that is responsible, equitable, traceable, reliable and governable. |
Build your frame
Your program's rules, not ours.
Planisphere doesn't ship a program's policy. You name the boundary, the check you already trust, the person who guards it and what happens at the crossing.
Technical data shared with a vendor, a contract response, a release outside the program.
Your export-control marking or CUI review, recorded with its answer.
The export-control officer, the program security lead, the approving office.
Watch records every crossing today; Hold and Wall run through the gate API.
For your developers
Four calls around the share.
Gate the controlled action, record the officer's decision, export the trail, verify it.
const ps = new Planisphere("ps_live_YOUR_KEY");
// 1. Gate the share
const d = await ps.gate({ pack: "defense",
action_type: "defense:controlled_sharing",
proposed_action: "Share AI-drafted technical details with an outside vendor.",
context: { program_boundary: "sensor-prototype", export_control_marker: "ITAR",
classification_or_cui_marker: "CUI", approving_office: "export-control" },
regime_refs: ["ITAR", "DFARS 252.204-7012"] });
// → decision: "needs_review"
// 2. The officer's decision, sealed as its own receipt
await ps.recordReview({ pack: "defense", action_key: d.action_key,
reviewer: "export-control-officer", decision: "approved" });
// 3. Export the trail · 4. Verify, no trust requiredVerifying a receipt needs no account. A record is not a legal finding or a certification.
Questions.
Is a record an export-control determination?+
No. It keeps records of what your program's tools and people did. A record can support an ATO package or an assessment; it isn't an export-control legal conclusion or a certification.
Does controlled data have to leave our environment?+
Your workspace decides how much readable detail a record keeps, and Planisphere can run inside your boundary. Talk to us before you connect a system that carries CUI.
Who can check a receipt?+
Anyone you give it to: a program office, an assessor or an authorizing official. Verifying needs no account and no trust in the program.
Related: Law · Medicine · Education · Run it inside your boundary · Corpus