We try to speak plainly: what belongs on the open web and what is still bench work are spelled out on Research status. Good-faith corrections and sharp questions help us keep that line honest. If you need evaluation, licensing, a prototype, or an NDA conversation, start with Partners or Contact.
← Back to Hub
Phyllux Vault
A geometric key story for a world of people and machines—consistent with Phyllux’s north star: stronger binding between identity, policy, and cryptography than password-only habits, without pretending the hard parts are already finished. PhiKey — full public page →
Consumer fiction tooling under Novelmate Studio lives on novelmatestudio.com. This vault lane is Phyllux identity and crypto posture; line Novelmate checkout copy to Research status row five when you compare honesty across domains.
Humans & AI
Research honesty
Post-quantum intent
Licensing lane
What we do not claim here.
Phyllux Vault is
not described as a completed, independently audited consumer cryptosystem on this site. Post-quantum language is a
design direction until outside review says otherwise. We avoid “unbreakable,” “military-grade,” and “quantum-proof” without a defined threat model and counsel review — see the
Phyllux Accord.
Safety first — nothing we cannot afford to lose.
Phyllux.io is a permanent public surface, not an archive for counsel-gated or partner-only material. Before each deploy that touches vault or crypto copy, run npm run preflight and follow Safe public publish. Anything that would materially ease reversal of a partner-only root of trust stays off this domain until counsel clears it.
Three lanes
Share with the world
What appears here is the narrative, evidence bar, and tooling boundary cleared for public disclosure: what is measured, what is still open, and demos that use synthetic placeholders only — not production key material or partner-only recipes.
Hold back the irreversible
Commercial advantage and safety both benefit from discipline: some details are better exchanged under agreement than sprayed across the open web.
- Partner playbooks, production tuning, and integration steps that enable silent misuse stay partner-scoped.
- We keep IP posture explicit: what is public positioning versus what is reserved.
- Black-box delivery is compatible with sharing benefit: interfaces and outcomes can be public while roots of trust stay protected.
Earn a living from the stack
Independent builders may use the public specs, framework repos, and licensed site material to ship products, services, or client work—under the terms we publish, with your own due diligence. Deeper construction write-ups may be available under agreement—not as a download from this domain. We also run licensing, evaluation workshops, and integration programs for teams that want partner-scoped depth—without overselling audit status. If that work pays off for you, see Open resource → fair reciprocity—voluntary, not a license obligation.
All public Vault / PhiKey pages
The canonical checklist lives on PhiKey → Everything on this site for VAULT / PhiKey (same links, one scroll).
Patents, trade secrets, or both?
There is no one-size answer. Patents exchange public disclosure for a time-bounded exclusive right. Trade secrets keep specific implementations and recipes confidential while market fit is proven. Many serious programs mix strategies by asset class. This page is not legal advice: filing and publication calls belong with qualified IP counsel so public disclosure does not overshoot intent.
Long-form monograph
A full PhiKey monograph PDF is not published on phyllux.io. Construction-oriented depth is treated as partner- or counsel-scoped disclosure (see safe-publish tiers — Tier C still applies if you distribute elsewhere). For a serious read under agreement, start at Partners or Contact. Maintainers can generate a local artifact from the site repo with npm run build:phikey-pdf (output under build/phikey-monograph/, not deployed here).
Regulated environments, high-assurance storage, and AI-mediated workflows where keys must not leak by accident call for honest evidence bars first, then depth under agreement.
