Photograph: bright modern secure research interior with glass, concrete, and warm metal accents—editorial establishing shot, no text or logos in frame.

PhiKey & Phyllux Vault

PhiKey is the geometric key story behind Phyllux Vault—part of the same north star as the rest of the site: flourishing people can trust, with an honest research bar on crypto claims. It uses a phyllotactic (golden-angle) layout, explicit test vectors, and a threat model that states plainly what is still open. This page collects what we can show without turning the public web into a partner vault. Philosophical and literary essays elsewhere on phyllux.io are not part of the cryptographic evidence chain for PhiKey; treat those as separate reading unless counsel routes them.

Fiction workspace Novelmate Studio is marketed on novelmatestudio.com, not on this page. PhiKey receipts stay in repos, tests, and Research status; Novelmate product claims align on row five there.

Phyllux Vault — public lane

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.

Photograph: macro sunflower seed head showing natural spiral phyllotaxis—real plant detail, evocative of lattice geometry. — Natural phyllotaxis as a daylight photograph—not a fabricated abstract noise tile.

Keystream from the walk

The story we tell in public is procedural: a structured traversal yields bytes you can bind into a construction, then you ship with conventional authenticated encryption where the platform expects it. The art on this page is mood and geometry only; the engineering receipts live in repos, tests, and the research-status table.

Photograph: long-exposure cyan and white light trails along a brightly lit modern data corridor—suggests flowing bytes without depicting real payload. — Still photography mood for sequence and flow— illustrative only.

AEAD on the outside

Downstream systems still meet the world through standard interfaces. PhiKey’s public narrative is about where the geometric story hands off to well-understood crypto primitives—not about replacing your compliance stack in a hero image.

Photograph: frosted acrylic layers and envelopes on marble in bright studio light—a sealed-package metaphor, not a crypto diagram. — Product-style still life for “wrap with AEAD in production”—not protocol art.

Photograph: fine metal security mesh in daylight—neutral industrial texture, calm exposure. — Threat-model posture stays in the writing; imagery is ornamental only.

Photograph: bright analyst desk with papers, glasses, and lamp—audit and review vibe, no readable confidential text. — Review culture is process and evidence—not a substitute for certification marks.

Photograph: wafer or board macro under crisp ring illumination—lab inspection metaphor, not a branded product shot. — Reproducible vectors and the research-status table remain the receipts.

What you can inspect today

phyllux-framework on GitHub — framework and public hooks (prior-art lane).
Research status — what is implemented, what is still on paper, in one table.
Phyllux Vault (public lane) — licensing posture and safe-publish checklist.
Safe public publish — what belongs on this domain, and what does not.

Photograph: polished vault door hinge and bolts in bright gallery-style light—dramatic craftsmanship, illustrative only. — Mood establishing shot—not a disclosure of premises or deployments.

Everything on this site for VAULT / PhiKey

These URLs are the full public stack for the vault track: engineering context, disclosure rules, and replication helpers. There is no checkout on phyllux.io; partner agreements cover extra implementation depth where that belongs.

Photoreal still life: leather book on sunlit desk—decorative strip between sections.

Phyllux Vault — public lane and licensing (long-form monograph not hosted on this domain).
PhiKey (this page) — narrative, threat-model posture, reference shape, framework pointer.
Technology — VAULT/PhiKey pillar — four-pillar context and spec summary.
Technology overview PDF & markdown — long-form WAVE–MESH–VAULT–CORE walkthrough.
Research status — what is demonstrated versus still open.
Docs hub — entry to all public documentation trees.
VAULT / PhiKey docs index — overview and deep links.
Safe public publish — disclosure tiers and deploy checklist.
VAULT/PhiKey decision space — open versus protected layers.
Demo appendix — public phyllux-core constants and CLI recipes (synthetic data only).
Pattern lab — open local tools; not production vault secrets.
IP · Open resource — reuse, reservations, and partner depth.
Partners · Proof — evaluation, licensing, prior art.
Accord — public claims discipline.
Knowledge base — reviewed articles (Accord, safe publishing, concepts).

Commercial use: you can build on this

If you want to ship products or services that use PhiKey ideas, treat phyllux.io as the published reference lane: study and integrate under the repo licenses, run your own security and legal review, and respect IP and LICENSE-IP-NOTICE.md. We do not warrant an audited consumer cryptosystem from these pages alone; we do publish enough for serious builders to evaluate, teach, consult on, or productize without a storefront on this domain. For production tuning and partner-scoped recipes, use Partners.

If this lane helps you ship something that pays the bills, the license text asks for nothing extra — and it would still mean a lot if you read Open resource → If this work helped you and consider fair voluntary reciprocity, which helps keep the public stack sustainable.

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.

Long-form monograph (not on phyllux.io)

We do not host a PhiKey monograph PDF on this public site. Full construction write-ups are shared only under partner or counsel-shaped agreements—see Phyllux Vault and Partners. Repository maintainers may build a local PDF from source via npm run build:phikey-pdf (writes to build/phikey-monograph/, outside deployable web assets).

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

Partner path Contact