01 ·

What Planisphere makes.

Measured behavior · bound authority · signed evidence record · evidence check

A customer starts with a workflow that may need to survive authorization, audit, litigation, or mission review. Planisphere records what happened, measures the tools involved, binds the behavior and controls to the relevant authorities, and produces a signed evidence record. A compliance team can recompute that record from the files alone and see whether it still matches.

Graph first. Harness second. Evidence third. The graph names the workflow and its sources; the harness runs the validation loop; the evidence record gives compliance a recomputable artifact instead of a trust-me memo.

ClassAI behavior evidence instrument
SubjectsAI agents — LoRA adapters, models, prompt-wrapped variants, RAG configs, vendor endpoints
CategoriesFour-axis battery — distinctness, drift, coherence, alignment — per agent, trinary grade
VerticalsDefense · education · law · medicine · general — same kernel, vertical-tuned probe set
ProjectionStereographic, conformal · SVD on the centered grade matrix
OutputSha-pinned, Merkle-rooted evidence record
DeterminismBit-identical across runs for identical inputs and pinned code
See how a record is checkedReproducible by any third party from inputs alone · open evidence check · record check
RuntimeStdlib + numpy · Air-gap capable · No network calls
Instrument versionPlanisphere 1.0.0
Compliance packagingEvidence packaging can be mapped toward CMMC / DoW impact-level review · Custom bundling available
Reference rootcddd2b753dd3e651aef04f0980290df2b5a171f57c648696b4d24b80982d2af5 · published reference record · recompute it
Coverage on reference6 subjects · 4 categories · Ed25519-signed · RFC 6962 Merkle root

The instrument carries its own integrity proof. Record contents can be recomputed locally; issuer trust can be pinned separately.

02 ·

Foundation · records and standards.

Four evidence-record shapes · twelve standards counterparts · one record

The instrument's evidence reduces to four artifact shapes inside the record and twelve standards counterparts the vocabulary tracks. Each card below names what binds, where, and how an evaluator picks it up.

Evidence-record artifacts Inside every record · sha-pinned · NIST MEASURE-mapped

Spectral LinesWhat does one row of evidence look like? Per-adapter signature · NIST M-1.1 · M-2.5 5-D spectral coordinate vector per adapter — norm, stable_rank, sv_entropy, effective_rank, cos_centroid — sha-pinned, embedded in the record. The atomic evidence row from which every aggregate claim is built. 5 scalars · sha-pinned · ATTESTATION.json artifact_id = per_adapter_signature Mapped
ConstellationWhere is the geometry of the fleet rendered? Fleet spectral report · NIST M-2.7 PC1/PC2 attribution, variance-explained spectrum, distinct-profile cluster map — the projection that lets a procurement officer see redundancy and outliers at a glance. PCA over centered grade matrix · variance shares · distinct-profile count Mapped
Merkle TreeWhat is the record the customer files? Behavior evidence record · NIST M-1.1 · M-2.5 · M-2.7 Time-stamped, sha-pinned, Merkle-rooted evidence record — the customer-filed evidence, recomputable byte-for-byte by any third party from the published algorithm. Merkle root · sha pin · timestamp · bit-exact recompute Mapped
Pulsar BeaconHow does today's signature differ from the last one? Drift differential · NIST M-2.5 Differential signature across adapter versions — the vector that lets a re-authorization cite evidence of behavioral change since the prior signed record root. Signature delta · prior root chains · re-check evidence Mapped

Standards counterparts Vocabulary tracked against federal & IETF standards

Wax SealWhere does the record live in the standards stack? Evidence record ↔ SCITT receipt Planisphere's evidence record maps to the IETF SCITT receipt/artifact vocabulary — supply-chain trust framed by the standard the auditor already audits against. IETF SCITT (draft-ietf-scitt-architecture)
ConstellationHow is the root tracked across time? Evidence root ↔ CT-style transparent log Every record root is registered transparent-log-style — Receipt Registration in SCITT terms, RFC 9162 CT idiom for the cryptographic chain that survives a vendor change. IETF SCITT · RFC 9162 (Certificate Transparency)
Merkle TreeWhich hash function backs every sha pin? Hash algorithm ↔ SHA-256 Engine emits FIPS 180-4 SHA-256 by default. SHA-3-256 parity track lives behind a flag for FIPS 202 environments. No alien hash — the record's atoms are an evaluator already-trusts primitive. FIPS 180-4 · FIPS 202 (SHA-3-256 parity track)
Wax SealIs the crypto module validated? Crypto module posture ↔ FIPS 140-3 Crypto module validation is in process. CAVP test vectors targeted for the next release; the engine binary is built against the validation track today. FIPS 140-3 · CAVP test vectors
DrydockHow is the engine binary trusted? Build provenance ↔ SLSA L3 Engine binary is signed and carries build provenance. SLSA L3 is the active target; current pipeline matches the in-toto provenance idiom and Sigstore cosign signatures. SLSA v1.0 · in-toto · Sigstore (cosign)
Naval EnsignWhat ships with the engine release? Software bill of materials ↔ SBOM Each release ships an SBOM designed to support NTIA minimum-element and CISA SBOM review — the bill of materials a CISO can hand to a supply-chain assessor without translation. NTIA minimum elements · CISA SBOM
Helm WheelWhere does the SDLC posture map? Secure SDLC ↔ SSDF v1.1 SSDF practice mapping is forthcoming. Current development posture lines up to PO/PS/PW/RV practice families; published mapping will name each practice's evidence artifact. NIST SP 800-218 (SSDF v1.1)
BuoyWhat enclave does delivery run in? Supply-chain risk ↔ C-SCRM Delivery enclave is designed to support NIST 800-161r1 C-SCRM review — the engine ships, runs, and recomputes inside the customer's supply-chain risk posture, not Planisphere's. NIST SP 800-161r1
AstrolabeHow does it sit in the AI risk envelope? AI risk management ↔ NIST AI RMF · ISO/IEC 42001 Govern / Map / Measure / Manage envelope is declared at the program level. The headline MEASURE controls — M-1.1, M-2.5, M-2.7 — are mapped to named record artifacts and enforced by contract tests; further subcategories extend on the same adapter. ISO/IEC 42001 §8.2 (AI risk assessment, triggered when significant changes occur) → §8.3 (treatment) can be mapped to the drift artifact. NIST AI RMF 1.0 · ISO/IEC 42001:2023
Drafting CompassWhere do system-level AI controls land? AI controls ↔ NIST SP 800-53 Rev. 5 Mapping to NIST SP 800-53 Rev. 5 control families (CA/CM/RA/SA/SI in particular) is forthcoming. AI-specific overlays are the active track once published; current record structures the controls already presuppose. NIST SP 800-53 Rev. 5 · AI-specific overlays
SubmarineWho can independently recompute? Independent recompute ↔ FFRDC / UARC Bundle is byte-for-byte recomputable on commodity hardware. An FFRDC or UARC under FAR 35.017 is the natural independent recompute partner; no engagement to date, solicitation open. FAR 35.017 · MITRE · Aerospace · Lincoln Lab · APL · GTRI · ARL-UT
Sonar PingWhat's published so an evaluator can sanity-check? Conformance vector ↔ CAVP / FRVT idiom Published reference inputs + expected outputs against a pinned engine — the same idiom CAVP uses for crypto modules and FRVT uses for face-recognition evaluations. Drop in, run, match. NIST CAVP · FRVT (reference test-vector pattern)
03 ·

Not DocuSign.

It manufactures the definition · it does not capture consent

The obvious mistake is to read this as a signing product. It is not. An e-signature service captures a human's consent over a document someone else authored — it records that you agreed, and binds your assent to a file it never had to understand. Planisphere does the opposite. It does not collect a signature over a document; it manufactures the definition in the first place.

The seal starts with measured system behavior. That behavior is compared against authority that was fixed before the audit ran, then the result is signed as a recomputable artifact. There is no counterparty whose consent is being recorded. There is no document being routed for assent. There is a measurement, a fixed standard, and a record an authorizing official, court, regulator, or counterparty can check from the inputs alone.

DocuSign captures consent over someone else's document. Planisphere produces a checked measurement against a fixed authority. The seal is not an agreement; it is a recomputable evidentiary record.

That is why the evidence check can be given away while the engine stays closed. Anyone can confirm a record in their own browser with zero core code — but confirming a record teaches no one how to manufacture one. See scope for how issued records are scoped.

04 ·

Entity.

Single point of contact · legal entity

§ 04.1 · Single point of contact

AvailabilityLive demonstration, walkthrough, or RFI response on 30-minute notice
Disclosuresecurity@planisphere.ooo · 90-day coordinated disclosure default

§ 04.2 · Legal entity

Legal namePlanisphereUS, Corp. · Delaware C Corp · incorporated
Principal point of contactL. C. Ross · Founder · email@planisphere.ooo
─── about · planisphere corp. · delaware c corp · 2026-05-25 ───