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.
GitHub · Public engineering map
One organization, multiple public surfaces: the deployed site, prior-art and educational material, licensing scaffolding, and coordination repos. Built so partners can navigate quickly—and acquirers can diligence without confusing demos for shipped product claims.
Featured below—each has a distinct job in the public story.
phyllux-web builds phyllux.io.
Immutable history for prior-art and process.
.io active · .com / .org planned.
For acquirers and technical partners: businesses operated outside phyllux.io stay outside the Phyllux Technologies transfer package described on Strategic acquisition. Treat educational demos and narrative depth as distinct from revenue-bearing products unless a partner agreement says otherwise. Disclosure discipline: PhiKey, Phyllux Vault, Safe public publish. Evidence rows: Research status.
Each card links to the canonical GitHub repository. Read the README and commit history first—then cross-check claims on Research status and Technology.
Source for phyllux.io—navigation, research lanes, partner CTAs, docs bridges, and build scripts. Diligence: review GitHub Actions (deploy-github-pages), Cloudflare redirect/header rules (operator doc in-repo: docs/CLOUDFLARE_PAGES_EDGE.md on phyllux-web), npm scripts, and branch policy alongside the domain plan.
Golden-angle biomimetic stack narrative—WAVE, MESH, VAULT/PhiKey, CORE—plus educational demos. Not the marketing site repo; pair with phyllux-web for the full public surface.
Four-tier licensing framework oriented toward independent inventors—clear lanes from research through fair commercial use. Pair with Licensing ladder on the site.
Work-in-progress invention fusion catalog—hundreds of research-stage concepts across categories. Expect churn; use as an ideas ledger, not a release manifest.
Meta-coordination across strategy, commercialization framing, and ecosystem orchestration—how threads tie together beyond any single code drop. Read last after you understand the concrete repos above.
Public pillars on Technology map to this engineering story—RF geometry, neural placement concepts, vault direction, integration spine.
GAFAA-class layout thinking—documentation and goals on site; measured patterns when published.
Wave docs →
Neural placement geometry—research posture; no clinical device claim on this domain.
Mesh docs →
Identity and vault direction—not an audited product cryptosystem in public copy.
PhiKey →phyllux-web is what visitors read and click. biomimetic-inventions-public carries prior-art and educational demos. Mixing them mentally creates diligence drag—keep lanes separate, then connect via this map.
Domains are a routing story, not a revenue claim. Mail and enterprise rollout follow counsel and DNS reality.
Primary technical hub and home for this static site.
Commercial mirror for audiences who expect .com—rollout TBD.
Public marketing lane for Novelmate Studio (local first fiction workspace). Source repo: phibronotchi-beep/novelmate-studio.
We keep phyllux.io focused on R&D evidence and partner routing first—so you are not left guessing what is “the product” versus what is cultural browsing. A sensible first pass is Hub, Technology, Research status, Proof, Partners, and Docs. Long-form media essays and thematic archives are here because we enjoy them and they carry context; they are not the main diligence bundle.
If the map fits your mandate, move to a scoped evaluation—NDA where appropriate—so both sides align on what transfers, what stays excluded, and what still needs measurement.
Partners · evaluationDocs hub → · Research status → · Contact → · Strategic acquisition →