02 · Space Force · Scope
Re-entry Capsule
00 ·
Prepare evidence for Re-entry Capsule review.
First evidence record within 21 days of access. Re-runs in a single business day.
This is the intake shape. Send these answers through the evidence intake or to email@planisphere.ooo, and we can map the next review-ready evidence record.
01 ·
Tool deployment inventory.
What runs in your enclave.
- How many Re-entry Capsule instances are under audit? Per-instance grades are emitted, not a deployment average.
- Which environments? Production, staging, evaluation — name each. The evidence record pins the environment in ATTESTATION.json.
- Hosting shape. On-prem, single-tenant cloud, multi-tenant SaaS. The measurement engine runs in-enclave on customer hardware in all three.
- Existing probe sets. If you already maintain one, we extend it. If not, we ship a synthetic set for Re-entry Capsule.
02 ·
Cadence & turnaround.
First record, repeat records, drift comparison.
- First record. Within 21 days of access — scoping, probe-set delivery, in-enclave run, evidence sign-off.
- Re-runs. Single business day once the engine is pinned. The record's
engine.versionis recorded so deltas are explained, not just measured. - Drift records. Pair two records and emit a delta. Drift is named, not asserted.
03 ·
Compliance controls to include.
The regulator's requirement row — pre-write the answer.
Tell us which controls and requirements should land in this evidence record. Common picks:
NIST AI RMF · OMB M-25-21/22 · ISO/IEC 42001 · FIPS 140-3 · HIPAA · FERPA · FRE 702 · ABA Model Rules.
Full control set lives at register 09.
04 ·
Next step.
One email and we're scoping.