U.S. patents pending
Planisphere patents pending.
The pending work describes one shared measurement kernel with two parts: an evidence boundary called Port that controls what crosses, and a review-record contract called Starboard that lets each domain use the shared measurements without changing them.
U.S. patents pending
Evidence boundary
Review-record contract
Zenodo DOI 10.5281/zenodo.20372606
01 · Port
An evidence boundary, enforced by code.
A named, typed boundary between a measurement substrate and a customer's data plane. It admits one shape of object outbound: derived, sha-pinned, Merkle-rooted evidence metadata.
PORT.crosses AttestationManifest, attestation_root, fleet_sha256, spectral_geometry_sha, per_adapter_signature, fleet_grades_csv, nist_controls, rank_collapse_attestation PORT.never_crosses raw_probe_responses, callable_references, api_keys, bearer_tokens, customer_pii, raw_behavioral_signature_vector, raw_rank_trajectory
The continuous-integration test planisphere.tests.test_port_contract fails the build if either list is silently expanded. The lists are the contract; the test is the proof. This describes the patents-pending method and the measurement kernel's contract. It is not a console tab, and it does not describe what the hosted console stores (see Privacy).
02 · Starboard
A typed contract for domain review records.
Every domain review record inherits the shared measurement root, code pins and signatures as they are.
Each domain adds its own regulatory context on top.
A conformance test stops a new domain from changing the kernel while it extends the surface.
The API reference is canonical for the live record contract. Domain views claim no certification or legal sufficiency.
03 · Posture
Verification without disclosure.
"Show me the model, the prompts, the data" can't be answered by a frontier vendor and shouldn't be by a regulated customer. The method lets a third party verify a record root from the manifest and the public key alone.
Related: Verify a receipt · The Mirror · About