1.9 KiB
Why I'm Building Quantum Document Corridors (And Documenting Everything Publicly)
The Problem I'm Solving
Right now, verifying documents between Texas and Colombia takes 4-6 weeks through the traditional apostille process. That's broken.
Meanwhile, quantum computers are advancing to the point where they'll break today's encryption. Most people are talking about this problem - I'm building a solution.
What I'm Actually Building
A quantum-resistant document verification system between Texas and Colombia using:
- ML-KEM (FIPS 203) - The new post-quantum encryption standard
- CUE - For constraint validation and document schemas
- Real deployment - Not just theory, actual Texas RON (Remote Online Notarization) to Colombian acceptance
Why I'm Documenting Publicly
I'm not an expert in post-quantum cryptography. I'm learning ML-KEM while deploying it. I'm learning CUE while building validation schemas.
Most "experts" wait until they have everything figured out before sharing. I'm sharing from day one because:
- The mistakes are educational - Mine and yours
- Progress is motivating - For me and anyone watching
- Constraints breed creativity - Public accountability forces better solutions
What to Expect
In the coming weeks, I'll share:
- My daily learning with ML-KEM and FIPS 203
- CUE schemas for document validation
- Deployment challenges between Texas and Colombia
- Mathematical foundations I'm leaning on (primes, golden ratio, type theory)
- Plenty of "this didn't work" moments
The Goal
If I succeed, we'll have instant quantum-resistant document verification replacing a 6-week process.
If I fail, we'll all learn why - and someone else can build on what I've documented.
Either way, the journey matters more than the destination.
Next post: "Day 1 with ML-KEM - What Is This Module-Lattice Thing Anyway?"
Building in public, learning in real-time.