Black box track: This hub is public; core implementation and repo detail stay partner scoped. Research status (what ships, what is spec): Research status. Technical briefings under NDA: Partners.

PhiKey and Phyllux Vault: public research and reference

Promotional strip: Phyllux Vault public research lane, headline PhiKey, test vectors and threat model, call to open the Phyllux Vault lane

Phyllux Vault — public lane (same message as the hero image)

PhiKey is the geometric key story behind Phyllux Vault: a phyllotactic (golden-angle) layout, explicit test vectors, and a threat model that says out loud what is still open. This page collects what we can show without turning the public web into a partner vault.

Plain talk. We are not selling “unbreakable” or “military-grade” here. If you need regulated assurance, you already know that comes from process, review, and scope — not from a tagline. See the Phyllux Accord for how we write about this work in public.

What PhiKey is

At the center is a 121-node Vogel-style lattice, a walk that produces key-stream material bound to a seed, and standard AEAD on the outside for the part users actually ship. A separate reference path treats password and salt with a KDF that has its own bar (and an Argon2id path where that fits the stack).

None of that replaces a professional audit, side-channel work, or your own counsel on disclosure. It does give a single place to read the engineering intent, run the same bytes as the tests, and stop pretending the hard parts are done when they are not.

Card: public lane, what we publish on the open site
Public versus partner depth: the open site is clear about what is published here.
Card: rigor and limits, claims we will not make without data
Honest research bar: what requires measurement, review, and scope before it counts as a claim.

What you can inspect today

Reference shape (illustrative)

Downstream integrators work from interfaces and test vectors, not from guesswork. A minimal Python-flavored outline of the public reference family looks like this:

# Illustrative only — not a full integration guide. lattice = PhiKeyLattice(seed, params) # 121-node walk, published constants keystream = lattice.keystream(n_bytes) # bind encryption to the walk aead = AEAD_AES_GCM # real deployments wrap with a standard AEAD ciphertext = aead.seal(plaintext, ad=... , key=derive(...))

Exact module names, version pins, and partner-only tuning live in agreements, not in a static HTML box.

PDF monograph

When counsel and the author agree to mirror a build, the file is assets/docs/phikey/PhiKey_Golden_Lattice_Security.pdf from the Phyllux Vault page. If the link 404s, the publication decision has not cleared yet. That is on purpose.

Go deeper with NDA-shaped detail, or keep reading in public and hold us to the same honesty bar we publish.

Partner path Contact