EU AI Act · Article 50
Marking and disclosure duties for generative and interactive systems reaching EU users. Record the duty event; the Toolkit seals it into evidence anyone can check.
output_marked · disclosure_rendered · label_published
Five primitives · one receipt
Planisphere Toolkits
Whatever the regulation, the ask is the same: prove it. A Toolkit is the five primitives, pre-arranged for your duty: gate holds the act, route puts a human on the call, seal makes the receipt, verify lets anyone check it forever, meter counts what ran.
gate→route→seal→verify→meter
01 ·
The Toolkits.
seven on the hosted API · one deep, two dated, four catalog-backed · depth straight from the registry
California SB 942
Provenance and transparency duties for covered generative systems in California. Latent disclosures, detection-tool availability, and license state, recorded as they happen.
latent_disclosure_embedded · detection_tool_heartbeat · license_granted
Law
AI-drafted work leaving the firm carries the lawyer’s review duty (ABA Formal Opinion 512). The law Toolkit gates the release, routes a named human, and seals the supervision record.
gate → needs_review → review decision → sealed receipt
Medicine
Clinical workflows carry HIPAA and FDA SaMD duties at the data boundary. The medicine Toolkit gates PHI exports, routes review, and seals model-change evidence.
phi_export_boundary · model_change_evidence
Defense
Program workflows carry ITAR and DFARS 252.204-7012 duties at the sharing boundary. The defense Toolkit gates controlled sharing and seals the contract-response review record.
controlled_sharing · contract_response_review
Education
District and edtech workflows carry FERPA, COPPA, and IDEA duties around student data. The education Toolkit gates the data boundary and seals scoring evidence.
student_data_boundary · scoring_evidence
US regulatory
Federal-adjacent teams answer NIST AI RMF, SP 800-53, FedRAMP, and ISO/IEC 42001 questions on request. The us-regulatory Toolkit maps the control, requests the evidence, and keeps the record.
map_control · request_evidence
02 ·
The five primitives.
one workflow API · every Toolkit is an arrangement of these
Ask before the act
allow · needs_review · block: the decision made before execution, sealed the moment it’s made. The block is a product feature, not a failure.
POST /v1/gate
A named human owns the call
Review lands where your team already works: Slack, ServiceNow, the console. The sign-off becomes part of the sealed record: name, decision, and timestamp.
POST /v1/reviews
Hashes in, receipt out
A KMS-held Ed25519 key signs the attestation root. By default only commitments to your content cross — hashes, never the material. Content you choose to preserve alongside a record crosses as ciphertext you encrypted yourself, under a key Planisphere never receives.
record → sealed receipt
Anyone, forever
Offline, free, no account, against keys published at a well-known address. The party who doesn’t trust you can check every byte.
POST /v1/verify
Counted when sealed
One cent per credit, never more than $25 per action, and the sandbox is free. Old proofs are never re-metered; only new proving is charged.
1¢/credit · $25 cap
03 ·
Start with the duty you have.
Toolkits are entry points, not different products · the same five primitives underneath
Two references stay current without this page: the live registry the API serves, and the regulation library it maps to. Pricing is the same everywhere: one cent per credit, capped at $25 per action.
We don't make you compliant; we make your compliance provable. Records, never certification.