Register 09 · Compliance controls

ITAR.

ITAR draws a boundary around technical data and who may receive it. Planisphere's posture is the answer: model state never leaves the enclave, only sha-pinned metadata crosses the port — so the audit can be performed without an ITAR-controlled transfer ever occurring.

register 09 · Compliance controls· Export control

Reviewed 2026-07-08

01 ·

What this is.

Seventy-two regulatory cite-anchors, organized for evidence lookup and review

Use. USML technical-data control · deemed-export boundary for model artifacts.

Register. 09 · Compliance controls — one of the 17 registers of the PLANiSPHERE corpus library.

02 ·

Promise. compliance

The contract this mark binds — derived, not asserted.

ITAR draws a boundary around technical data and who may receive it. Planisphere's posture is the answer: model state never leaves the enclave, only sha-pinned metadata crosses the port — so the audit can be performed without an ITAR-controlled transfer ever occurring.

Answers: How does Planisphere audit a model without triggering ITAR?

03 ·

See it work.

Evidence record you can check — not code you have to trust.

Planisphere measures your tool deployment against ITAR and seals the result into a signed, Merkle-rooted evidence record. The grade recomputes on your own hardware; the model state never crosses the boundary.

05 ·

The boundary this control draws.

Related marks, and the surface this one funnels to.

ITAR (USML technical-data control · deemed-export boundary for model artifacts) asks for an evidence record: ITAR draws a boundary around technical data and who may receive it. Read the related defense AI workflow product context at /defense.

EAR reg 09 · Dual-use export control (EAR99 / CCL) · AI-diffusion chip + weight controls ATO reg 09 · Authorization to Operate · program-office citation C-SCRM reg 09 · supply-chain risk · NIST SP 800-161r1
06 ·

Routes here from.

Where this mark is referenced in the Planisphere surface.

Any internal link in the Planisphere site that names "ITAR" canonicalises here.

See the record ITAR asks for.

The console shows the evidence; the docs show the endpoints; the briefing shows what the product does and does not claim.

API ·

When ITAR asks for proof, hand over records — not assurances.

record the duty · seal the receipt · verify offline

Planisphere records each duty event — an output marked, a disclosure shown, a review made — and seals it into a receipt that verifies offline against our published keys. You send hashes, never content. A record is evidence a third party can check; it is not a certification and not a legal determination.

See how a record is checked