Full journal, podcast, and videos
- Read the complete open-access journal in English, French, or Spanish: Vigil in the Orb — Zenodo record and DOI
- Listen to the affiliated podcast: Google Drive
- Watch the full video: Why Complex Geometry Fails at Cryptography — and What Actually Works
- Watch the short video: How Envelope Encryption Secures the Orb
For four years, I tried to answer a question that would not leave me alone:
Can fractal geometry protect information in a way that ordinary cryptographic architecture does not?
I followed that question through Fibonacci structures, complex planes, quaternion rotations, chaotic attractors, Penrose tilings, quasicrystals, Apollonian packings, reversible permutations, container formats, Python engines, plugins, tests, failures, and many nights where the next idea felt close enough to touch.
Today I can say something that would have been much harder for me to say four years ago:
I did not produce a new, independently validated fractal cryptographic algorithm.
And today, I am not sad.
The sentence I once wanted to prove
When I began, I wanted geometry itself to carry security. I wanted a fractal trajectory, a quasicrystalline structure, or a sufficiently complex transformation to become more than a representation. I wanted it to become a protection mechanism.
The intuition was not ridiculous. Cryptography is full of mathematical structure. Geometry can create vast spaces, irregular trajectories, sensitive transformations, and forms that are extremely difficult to understand by looking at the result alone.
But visual complexity is not cryptographic hardness.
A beautiful transformation is not automatically one-way. A chaotic orbit computed with finite precision is not automatically entropy. A secret-looking image is not a security proof. A reversible permutation can make data appear unrecognizable while adding no independently established confidentiality.
Cryptography does not care how mysterious the output feels. It asks harder questions:
- What is the secret?
- Which primitive protects it?
- What can the adversary observe or modify?
- How are confidentiality and integrity defined?
- Can the implementation be reproduced across systems?
- What evidence could prove the claim wrong?
My experiments kept returning me to those questions.
Failure became useful when I stopped asking it to flatter me
For a long time, every partial success invited a bigger claim.
A transformation worked, so perhaps it contributed security. A geometric path looked unpredictable, so perhaps it could become a key schedule. Two implementations drew similar forms, so perhaps the structure was stable enough to authenticate. A prototype completed a round trip, so perhaps the underlying concept was almost proven.
Then the difficult cases arrived.
Short cycles appeared. Collisions remained possible. Floating-point tolerances changed decisions. Similar drawings could hide different bytes. Numerical sensitivity did not become cryptographic entropy merely because the animation looked dramatic.
These results did not prove that geometry is useless. They showed me where geometry belongs.
That distinction changed the project.
Instead of asking geometry to impersonate encryption, I began separating the layers:
- established cryptographic primitives protect confidentiality and integrity;
- random content keys carry actual secret material;
- envelope encryption allows one protected payload to serve multiple authorized recipients;
- canonical encoding keeps authenticated bytes stable;
- geometry describes domain, path, structure, and provenance;
- tests, attack cases, and explicit refusals prevent the interface from claiming more than the evidence supports.
The Orb became more honest when it stopped pretending to be the lock.
What the four years actually produced
It would be false to say that nothing came from this work.
FQLC1 became an experimental single-destination container and a useful object of autopsy. It helped expose the difference between a password-hardening function, authenticated encryption, and a reversible geometric transformation.
FQLC2 became a multi-recipient experimental architecture built on an envelope model. The content is encrypted once with a random key. That key can then be encapsulated separately for recipients. The geometric context can travel with the container as authenticated structure without being misrepresented as the source of secrecy.
The wider laboratory also produced reproducible software evidence, formats, contracts, attack matrices, educational exercises, and a system named Vigil whose most important ability is not to declare victory. Its role is to inspect a claim, ask for missing evidence, propose an attack, and suspend a decision when the conditions are not met.
That is a real result.
It is not a cryptographic certification. It is not independent cryptanalysis. It is not proof of post-quantum security. FQLC2 remains an experimental, unaudited pre-alpha prototype.
The full journal preserves that boundary because the boundary is part of the work.
Why I need to stop this cycle now
I could continue indefinitely.
There is always another benchmark to build, another formalization to attempt, another implementation to compare, another attack surface to inspect, and another mathematical family to test. Research can consume every available hour while still making the next hour feel necessary.
But I also need to live.
I need to find sustainable work, create income, and give my energy to projects that can support the next part of my life. That is not a scientific conclusion about what fractal geometry may eventually contribute to security. It is an honest conclusion about what I can continue funding alone.
Four years of personal effort do not create an obligation to spend a fifth year pretending resources are unlimited.
Moving on does not erase the research. The journal is public. The mechanisms, limits, and evidence are documented. The two videos explain the central distinction. The podcast carries the larger story. Someone else can read the work, challenge it, reuse what is sound, reject what is weak, or continue a question with better mathematics and more resources.
That is why I am publishing the trace instead of burying the disappointment.
Today I won a war against my own ego
The hardest adversary in this project was not an attacker trying to break a container.
It was my own need for the original dream to be correct.
After thousands of hours, it is tempting to protect the story instead of the people who may trust it. It is tempting to rename an experiment as a breakthrough, to treat complexity as proof, or to believe that personal sacrifice earns scientific certainty.
It does not.
Effort deserves respect. It does not deserve immunity from evidence.
Today I do not feel defeated. I feel lighter. I can love fractals, recognize what they taught me, preserve the useful architecture, and still refuse to call the experiment something it has not become.
That refusal is not the death of the work.
It is the moment the work became responsible.
The children matter more than my career
I am building educational systems because the next generation will inherit security decisions made by people who may never see the mathematics underneath them.
Children and students do not need another confident interface telling them that a beautiful shape is secure. They need environments that teach them to distinguish representation from mechanism, mechanism from evidence, and evidence from a claim.
They need to see that an engineer can say:
- this part works;
- this part is experimental;
- this part failed;
- this part remains unknown;
- and this is where another person can continue.
If my career were the most important thing, I might be tempted to announce that I invented fractal cryptography.
But children are more important than my career.
Their future security is more important than my need to be remembered as the person who solved the problem. If this work helps one young builder learn that honesty is part of engineering, then the four years did not disappear.
What I carry forward
I still believe geometry has a place in security research. It can help structure domains, provenance, visualization, canonical paths, educational models, and new questions. What I no longer accept is the shortcut from fascination to protection.
The next phase of my life needs paid work and sustainable collaboration. I am open about that because open research without a sustainable human behind it eventually becomes abandoned infrastructure.
If you are a cryptographer, security engineer, educator, researcher, maintainer, or organization that sees value in this discipline, read the journal and challenge it. If you see a place where my work can contribute professionally, contact me. I am not asking anyone to preserve my conclusion. I am asking them to inspect the trace.
For now, this cycle is closed.
I did not win by proving that fractals are cryptography.
I won by refusing to let my ego become a security primitive.
And that may be the most important algorithm I produced in four years.
What should a responsible researcher publish when the original hypothesis does not survive, but the failures produce a better architecture?
