ks · compliance
Compliance.
Public collaborations with regulators and civic bodies. The foundry holds protocols, not personal records — and we'd rather show that to a working group than promise it on a pitch deck.
how it works
From consult to align.
on the record · open windows
- § 01open
Consult
Regulators read the protocol specs alongside us. We answer questions; they flag gaps. No NDAs.
- § 024–8 weeks
Draft
We co-author a posture document — what the protocol does, what it doesn't, where the legal seams are.
- § 0330–60 days
Review
Submit to the working group. Public comment window. Revisions on the record.
- § 04yearly
Align
Final attestation published. Audit cycle scheduled. Compliance test suite goes open-source.
what we ship
Public, reproducible, auditable.
Public attestations
Every alignment is published — what's covered, what isn't, who signed. No private side-letters.
Audit trails by default
The Trade artifact carries cryptographic receipts; the Neuron artifact logs ingest provenance. Auditors get tooling, not promises.
Open compliance tests
Every framework alignment ships with a test suite anyone can run. Pass/fail is reproducible.
PDS sovereignty
The foundry never custodies user data. Right-to-be-forgotten is a protocol primitive, not a feature request.
active engagements
On the table.
- drafting
EU AI Act
Co-drafting consent attestations for the Neuron protocol. PDS-bound corpora map cleanly to Article 10 data-governance requirements.
- aligned
GDPR · UK-GDPR
Posture published. PDS sovereignty is the right-to-be-forgotten primitive; deleting the PDS deletes the data, full stop.
- consulting
Charter of Fundamental Rights
Reading the protocol alongside Articles 7, 8, 11. Identity is the privacy seam; Trade is the property seam; Neuron is the expression seam.
- consulting
Aapti civic-data charter
PDS as a civic primitive. Working with Aapti on the right-to-data-portability spec for South Asian deployments.
- audited
Open Data Charter
Trade Suite — five sovereign paradigms with Phase-7-A formal verification. Money-Lock invariant proved; audit on record.
released
Frameworks on record.
GDPR posture v1
Public posture document explaining how PDS sovereignty satisfies right-to-be-forgotten under Articles 17 and 20.
GDPR · UK-GDPR
2026 Q1Trade audit-trail spec
Specification for cryptographic receipts on every trade settlement. Auditable by anyone with public history.
Open Data Charter
2026 Q1Neuron consent revocation API
Reference implementation for revoking consent on PDS-bound training data. Watch the corpus shrink in the audit log.
EU AI Act (draft)
2026 Q2
asked often
Quick answers.
Where's user data held?
Not by KashScript. Every account is a DID resolved against a Personal Data Store the user controls. We define formats; we don't custody data.
How does right-to-be-forgotten work?
Deleting the PDS deletes the data. The DID can be tombstoned. The foundry holds nothing to retain.
Are the audit reports public?
Yes. Every framework alignment is a public document. Drafts include public comment windows.
Can a regulator request user data?
There is no user data with us to request. Subpoenas and orders are routed to the relevant PDS operator — the user, or whoever they trust to host them.