LeptonX Request Access
A Standing Commitment from LeptonX

How Maya works.

The queries, the boundaries, the architecture — published in full. Because the inside of a system that touches your medical records should not be a competitive secret.

Every other product in this category asks you to take its claims on faith. Every certification, every audit report, every disclosure document is a statement about a system that you are not permitted to inspect.

We took the opposite path. The queries Maya runs against your records, the rules she is forbidden to break, and the architecture she runs on are all published. Not in a whitepaper. On this site.

Claim 01
A query you can read is stronger than a policy you cannot enforce.
Privacy policies, terms of service, and audit attestations all rest on the company's willingness to abide by them. A published SQL query is a falsifiable claim — anyone with the schema can verify what it does and what it does not do.
Claim 02
Hiding the logic is the product, for most of this industry.
When the model is a black box, the only thing left to sell is the marketing copy around it. We built LeptonX so the inside could be shown to a skeptical reviewer and survive scrutiny. The transparency is not a feature added on top. It is the architecture.
Claim 03
Every new disclosure law is an obligation we have already met.
GDPR. CCPA. HIPAA enforcement actions. State-level health data laws. The regulatory environment moves in one direction — toward more disclosure, more inspectability, more patient control. Publishing the queries now means every future obligation is one we already shipped against.
The Series

Three layers. Three pages. One commitment.

01
How Maya delivers your documents.
The full retrieval pipeline — from FHIR DocumentReference resources to per-patient embeddings to the system-prompt rules that govern how Maya cites what she finds. Includes the deny-list in full.
Published
Read →
02
How Maya reconciles your medications.
The discrepancy-detection logic between active medication lists, refill histories, and clinical notes — and the strict boundary against Maya ever asserting that a medication should be discontinued. Ships with the medication-reconciliation feature.
Coming with v3
In preparation
03
How Maya tracks your appointments.
The schedule reconciliation across portals, the prep-summary generation pipeline, and the rules that prevent Maya from advising on whether to attend or skip any given visit. Ships with the appointments feature.
Coming with v3
In preparation
The Standing Commitment

No layer of the platform ships without its own page.

The iceberg metaphor on our home page describes the visible tip of what LeptonX does — appointments, documents, prescriptions — and the sovereign depth underneath that makes the surface possible.

Every layer of the visible tip ships with a transparency page in this series. Not as an afterthought, not as documentation for the technically curious. As a condition of release.

01
The queries published on the transparency pages are the queries running in production.
02
The deny-list rules published on the transparency pages are enforced in the system-prompt layer, not aspirational.
03
When the logic changes, the page changes. The page is a contract, not a snapshot.
04
No feature ships to a patient that we are not willing to explain on this site.
§

The first page is available now.

Document delivery — the layer Maya uses most. Read it before you take anything else we say at face value.

Read Chapter 01 Request Early Access