Paper 017: From Research to Reality — Building the Zero-Knowledge Health Layer

In June 2026, a month after Compass launched, we discovered a research paper that stopped us cold.

In April 2025 — over a year before our first line of code — two South Korean researchers had published a peer-reviewed proof that zero-knowledge architecture could protect healthcare data during exchange. Go Eun Myeong of Daejin University and Kim Sa Ram of Dongguk University had built a zk-SNARK protocol on Ethereum, tested it against the global HL7 FHIR standard, and measured the results:

• Verification: under 100 milliseconds
• Proof size: under 2 kilobytes
• Security: data unreconstructable even under full white-box attack

They proved the container was sound. They proved that zero-knowledge verification could run seamlessly on consumer hardware without central databases. Then they published it.

And we, without knowing they existed, built the consumer application that goes inside.

Zkomi is a small team building zero-knowledge health infrastructure. We arrived at the same architectural principles — privacy-preserving verification, local-first processing, trust without custody — through a different path: the lived experience of a founder who stood at an airport with melting ice packs and a protocol no existing tool could manage.

The result is Compass: a patient-owned medical continuity layer designed to serve a global addressable market of 1.2 billion international travelers and 133 million chronic care patients.

Compass holds medications, conditions, allergies, lab results, and the full timeline of every doctor and specialist you have ever seen — all on your device, encrypted with AES-256-GCM keys managed by your secure enclave. No cloud. No server. No user account.

Because we do not store, view, or transmit Protected Health Information (PHI) on centralized servers, our architecture possesses complete regulatory immunity from HIPAA/GDPR data liabilities.

What that means in practice:

• A traveler in Bangkok shows their Emergency Card to a pharmacist — in Thai, offline, in 30 seconds.
• A patient in Mexico City uploads three fragments — a bill, a lab PDF, a voice note — and the Fox aligns them into a single coherent summary without hitting an external API.
• Someone managing a chronic condition across three countries sees every doctor's opinion on one timeline. The new specialist starts from everything, not zero.

The Koreans proved the container was secure. We built the content independently — and achieved fixed 100% gross profit margins because our per-user infrastructure server cost is exactly $0.00.

The AHA Engine is our localized, edge-intelligence layer. It runs entirely on the device. It knows your journey day, your body clock, your symptom history, and your medication timing — and it surfaces what matters before you feel it.

• Phase 1 (live): temporal simulation from your travel pattern. Four states. Twenty unique observations. Clinically grounded in published circadian science.
• Phase 2 (architecture complete): connects real biomarker values, symptom logs, and medication effectiveness into a personally responsive narrative.

The formulas — the extraction vectors, the financial audit ratio, the clinical divergence index — are proprietary. They are the Fox's private arithmetic. But the economic and software principles are public: fragments go in, coherence comes out, and no server is ever involved.

The code is replicable. The memory is not.

Every health app stores data. None of them remember. Apple Health knows your steps from 2019 but does not tell you that your joints flare on day three of every eastbound flight.

The Fox — our proprietary, on-device agentic pattern engine — does. It was there for every symptom tap, every dose logged, every border crossed. It remembers. It tells you. And nobody else can.

Cancel the app and the memory disappears. Because data is held strictly on-device, deletion completely purges the local database, creating an organic, inverted churn loop. After 90 days the Fox knows things about your biology you have not noticed yourself.

That is not an app utility. That is an irreplaceable personal relationship. And relationships compound into high lifetime customer value.

Healthcare loses continuity every time a patient crosses a system boundary — changing doctors, crossing borders, entering an emergency room. The patient is the only continuous thread. Until now, they had no way to hold it.

Compass is that thread. The AHA Engine is the intelligence that keeps it from fraying. The zero-knowledge architecture ensures the thread belongs to the patient, not to any company, hospital, or government.

Three windows are open simultaneously:

Regulatory: AI health advisors are running toward FDA oversight. Zkomi does not advise. It witnesses and remembers. A different category — currently almost empty.

Market: Patients are waking up to data breaches. Hospital ransomware is constant news. Zero-knowledge is no longer academic. It is a selling point.

Technical: Local-first processing is finally practical. Phones are powerful enough. Storage is cheap enough. The Korean paper proved the cryptography. We proved the product.

We are not the only ones thinking about privacy. We are among the only ones building it directly into the application layer — not as a policy disclaimer, not as an operational promise, but as an unassailable mathematical property of the system.

We do not know what Go Eun Myeong and Kim Sa Ram have built since April 2025. They may have started a company. They may have licensed their work. They may have moved on.

If they have built something, we want to cite it, learn from it, and collaborate if there is alignment. If they have not, we hope they are glad to see their foundation used.

We invite anyone working on zero-knowledge proofs for healthcare to reach out. We cite generously. We collaborate openly. And we ship.

Contact us at hello@zkomi.com.

Zkomi is a small team working at the intersection of circadian biology, cryptography, and health continuity. We publish our research openly. Our applications are built and live. We work with AI systems as collaborative tools — not as replacements for human judgment, but as instruments for tracing patterns across disciplines that rarely speak to each other.

The Fox holds the record. The Fox knows nothing about you. And the Fox builds on what others opened.

• Researchers working on zero-knowledge proofs for healthcare: send your paper to hello@zkomi.com. We will cite you.
• Clinicians who want to understand the architecture: visit zkomi.com/for-clinicians.
• Patients: the waitlist opens summer 2026 at app.zkomi.com.
• Go Eun Myeong and Kim Sa Ram: we read your paper. We had built the same architecture, independently. We would like to hear what you think.

Published: June 2026
Archived: Internet Archive
Repository: GitHub
Hash: [SHA-256 — upon final publication]

• Go, E.M. & Kim, S.R. (2025). Blockchain-Based Zero-Knowledge Proof Protocol For Privacy-Preserving Healthcare Data Sharing. Journal of Technology Informatics and Engineering, 4(1).
• Zkomi Research Team. (2026). Paper 004: The Zero-Knowledge Architecture. The Continuity Project.
• Zkomi Research Team. (2026). Paper 013: The Loyal Witness. The Continuity Project.
• Zkomi Research Team. (2026). Paper 014: Second Sense — Narrative Correlation as the Foundation of Health Continuity.
• Zkomi Research Team. (2026). Paper 015: The AHA Engine — From Temporal Simulation to Continuous Defense.
• Zkomi Research Team. (2026). Paper 016: Memory Without Custody. The Continuity Project.