How do I try EAR in Planisphere?

Open the Console to see sealed records and verify one yourself, read the Docs for the endpoints, or read the capability briefing for what the product does and does not claim.

EAR.

EAR 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 EAR-controlled transfer ever occurring.

Open the Console See how a record is checked

Reviewed 2026-07-08

01 ·

Promise. compliance

The contract this mark binds — derived, not asserted.

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

02 ·

What this is.

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

Use. Dual-use export control (EAR99 / CCL) · AI-diffusion chip + weight controls.

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

03 ·

See it work.

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

Planisphere measures your tool deployment against EAR 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.

Prepare evidence for program review →See how a record is checked

04 ·

Questions this answers.

1 high-intent question buyers search — each on its own page, each pinned to EAR.

Are AI model weights subject to EAR export controls? Read the answer →

05 ·

The boundary this control draws.

Related marks, and the surface this one funnels to.

EAR (Dual-use export control (EAR99 / CCL) · AI-diffusion chip + weight controls) asks for an evidence record: EAR draws a boundary around technical data and who may receive it. Read the related defense AI workflow product context at /defense.