Gift posture · biomimicry · study welcome ← Back to Hub

Open resource

Golden-angle biomimetic light field from the public hub—same visual language as the gift posture pages — Hub raster art (golden-angle spiral field)—Open resource shares the same north star as the rest of the site.

phyllux.io is meant to be useful, not a toll booth. The aim here matches our north star: flourishing people can trust—honest inquiry, local-first craft where it applies, and pattern-grounded study. We nudge people toward patterns that are kinder to living systems: golden-angle geometry, careful science, replication where we can show our work, and room for wonder without fraud. If you teach biomimicry, study phyllotaxis, or prototype antennas and interfaces, you are welcome to treat the published educational layer of this site as material you can learn from, cite, and build on. Formal terms live in the repo licenses below so everyone knows what applies.

Paid evaluation, licensing, and prototypes. Start on Partners (partner path PDF, commercial routes). General routes: Contact. Evidence bar: Research status.

Where products and services ship. Paid software and recurring services are meant to ship on their own sites and agreements, not as a shopping cart on phyllux.io. This domain stays the public research and resource lane, with a clear commercial front door on Partners. Narrative and craft essays: Public library. Example: Novelmate Studio (local first fiction workspace) markets at novelmatestudio.com; line its product copy to Research status row five the same way you would here.

Commercial use is not free. The gift posture covers study, teaching, citation, and personal exploration under the published licenses. Commercial use, integration into a product, or resale is a separate track and needs an explicit license through Partners. Buyers and investors interested in exclusive rights, asset purchase, or acquisition should use Partners and email phibronotchi@gmail.com with a clear subject (see Contact).

What “everything is up for grabs” means in practice

Site copy and diagrams (public pages). Reuse for teaching, coursework, and nonprofit explainers is exactly what this posture is for. Cite phyllux.io and the page you used. If you pull from the GitHub site repo, follow DOCS_LICENSE.md (documentation: CC BY-SA 4.0) and LICENSE (code: MIT).
Knowledge base articles. Many entries are CC BY 4.0 seeds; each article’s metadata in Knowledge base reflects what was published.
Replication notes. Specifications meant to be checked (for example the 137 & geometry parameters, PhiKey public lane) are there so others can verify or disagree in the open.
VAULT / PhiKey builders. The public engineering lane (Phyllux Vault, PhiKey, vault docs) is for people who want to teach, verify, or build products and services under license and honest review—not a checkout on this domain.
What is not “free to ignore.” Third party assets (fonts, any credited photos, tradition specific material you must respect in context), plus anything marked partner or NDA, are not yours to strip mine. Trademarks and project names still need normal care.

If this work helped you

Licenses first. What the repo grants under MIT and CC is what it grants: you are not legally required to send money because you read a page or ran some code. I mean that seriously.

Human fairness. I have poured years into the research, writing, and tooling here so others can learn and build. If you use what is on this site—ideas, copy, diagrams, software—in a way that creates real value for you (income, a funded project, a product you ship), I would genuinely appreciate a fair share coming back: something that reflects the lift you got, not a shakedown. I am awkward about asking for that, so I will say it plainly: voluntary reciprocity feels right to me, and it helps me keep this lane alive.

How to do it. For something structured, start with Partners or Contact and we can find a simple path. The optional e-transfer on the hub is intentionally only for keeping the site hosted and working—not a substitute for talking about substantive use. However you engage, thank you for taking the work seriously.

What stays partner scoped (honesty)

Black box integrations, undisclosed vault internals, and manufacturing style detail can stay under agreement. That protects people who build seriously without pretending the hard parts are all on the web. The split is intentional: public gift layer versus partner depth. See IP, Partners, and LICENSE-IP-NOTICE.md in the repo.

Accord still matters

Reuse for learning and beneficial applications is welcome. Uses that need explicit governance fit—defense, regulated sectors, or sensitive deployments—should route through Partners so expectations match the Phyllux Accord and your compliance process.

Quick links

Fair reciprocity · Public library (narrative worlds, principles, awareness & giving) · Strategic acquisition · phyllux-web on GitHub · DOCS_LICENSE.md · LICENSE (MIT) · IP notice · Research status · Pattern lab