← IP docs

Trade secrets — public lane

Phyllux treats trade secrecy + deliberate public disclosure as complementary tools: the public site and repos establish timeline, teaching context, and prior-art posture; partner lanes carry enabling detail under agreement. That split is intentional—it raises trust with technical buyers and collaborators without turning the public CDN into a leak surface.

Why say anything at all?

Due diligence: reviewers can see a clear boundary—what is evidenced in public copy versus what requires NDA—without guessing from silence.
Partner alignment: NDAs protect specific disclosures; this page sets expectations before anyone signs.
Educational mission: biomimetic geometry and honest research posture can travel under Open resource terms without shipping parameter-level secrets.

Two layers (conceptual)

Public layer: concepts, non-enabling diagrams, replication notes where safe, integrity manifests, blog and docs that pass publish review. Measured results appear when we choose to publish them and label uncertainty.

Protected layer: manufacturing recipes beyond public papers, undisclosed optimization parameters, partner-specific supplier terms, device attestation and key-lifecycle playbooks, private indices or tables used operationally, and counsel-strategy materials. Inner PhiKey/VAULT implementation detail follows PhiKey public positioning—not production-grade claims on the marketing surface.

Protection lanes (definitions)

Internally we tag each tracked item with how it may move (steward + counsel). On this page, PATENT-DRAFT means “may be candidate material if counsel ever chooses to pursue claims”—not a promise to file.

Lane	Meaning on this site
TRADE SECRET	Not published on phyllux.io. Kept under reasonable secrecy measures; enabling detail may appear only under mutual NDA for qualified partners.
PATENT-DRAFT	May be evaluated for patent disclosure per claim if counsel recommends—not a public spec dump.
NDA	Partner-only: disclosed under mutual NDA (interfaces, procedures), not as a public tutorial.

Selective external filings remain exceptional—see IP overview. Day-to-day protection is still trade secrecy + deliberate public teaching.

Domain buckets (categories, not recipes)

Protected know-how is grouped the same way the technology story is grouped. The list below describes kinds of information—not filenames, serial numbers, or values.

Bucket	Typical trade-secret content (examples)	What the public lane shows instead
WAVE (RF / GAFAA-class)	Stack-ups, matching networks, multi-band tuning, calibration shortcuts that survive manufacture.	Geometry intent, documentation goals, measured patterns when published; links to research status.
MESH (interfaces / placement)	Electrode layouts, materials interfaces, biocompatibility process detail beyond public summaries.	Research posture; non-clinical framing on this domain; no device clearance claims.
VAULT (PhiKey direction)	Key schedules, rotation policies, binding recipes, operational vault procedures.	Directional docs, decision trees, safe publish checklist—not audited product crypto claims.
CORE (integration)	Cross-domain orchestration, internal buses, integration smoke tests tied to unreleased builds.	Spine concepts at a high level; evidence rows on research status.
Engineering methods	Proprietary algorithms, solver presets, lab notebooks not cleared for web.	Method names or goals only when useful; otherwise omitted.
Manufacturing & test	Tolerances, yield tricks, vendor-specific instructions.	Qualitative capability language or “measurement when published”—never secret tables.
Commercial ops	Pricing strategy drafts, partner-specific licensing arithmetic, unfinalized term sheets.	Public tiers and routes live on Partners and licensing docs at the level we intend to stand behind.

Register index (TS-001–TS-050)

Codes, domains, and lanes match the steward register. The Public theme column is deliberately bland: it names the topic bucket only—no formulas, tolerances, key schedules, or step-by-step methods. For prior-art and disclosure timeline, use Proof; for evidence posture, Research status.

Lane codes: TS = TRADE SECRET, PD = PATENT-DRAFT, NDA = partner-only (mutual NDA).

Code	Domain	Lane	Public theme (non-enabling)
TS-001	Wave	TS	RF impedance matching — golden-angle family
TS-002	Wave	PD	Feed / phase-center reference cluster
TS-003	Wave	TS	Harmonic steering via element spacing
TS-004	Wave	TS	Multi-band scaling strategies
TS-005	Wave	TS	Radial scaling / sidelobe control
TS-006	ENGENICA	PD	Adaptive redundancy geometry (engineering)
TS-007	Wave	TS	Frequency-selective matching specifications
TS-008	Wave	PD	Beamforming phase reference cluster
TS-009	Wave	TS	Coherent combining / aperture methods
TS-010	Wave	TS	Environmental calibration / MEMS cluster
TS-011	ENGENICA	PD	Nested lattice scalability (engineering)
TS-012	Wave	NDA	Circular polarization — spiral family
TS-013	Wave	NDA	Wideband spiral transition
TS-014	Wave	PD	Conformal surface mapping
TS-015	Wave	NDA	MIMO beamforming — orthogonal spiral layout
TS-016	Wave	NDA	Distributed power / thermal feeds
TS-017	Wave	NDA	Array calibration procedure cluster
TS-018	manufacturing	TS	Tolerance budget / yield envelope
TS-019	Mesh	TS	Interface coating sequence (biology)
TS-020	Mesh	PD	Irregular-surface placement planner
TS-021	Mesh	TS	Neural front-end / common-mode rejection
TS-022	manufacturing	TS	Flexible substrate process specifications
TS-023	Mesh	NDA	Chronic impedance monitoring
TS-024	Mesh	TS	Time-release biofactor formulation
TS-025	testing	NDA	Spectroscopy diagnostic classifier
TS-026	Mesh	PD	Wireless power/data coupling
TS-027	Mesh	PD	3D helical placement extension
TS-028	Mesh	NDA	Acute penetrating array layout
TS-029	Mesh	NDA	High-density cortical grid layout
TS-030	Mesh	NDA	Opto-electrode integration layout
TS-031	Mesh	NDA	Closed-loop stimulation protocol
TS-032	Mesh	TS	Alternate coating fallbacks
TS-033	Mesh	NDA	Electrode material trade study
TS-034	Mesh	NDA	Surgical tooling / technique cluster
TS-035	Vault	TS	Key derivation layer (geometry-bound)
TS-036	Vault	TS	Encryption construction cluster (Vault)
TS-037	Vault	TS	Hardware fingerprinting / noise harvest
TS-038	Vault	TS	Cross-domain integrity checksum bundle
TS-039	Vault	TS	Key schedule / transform cluster
TS-040	Vault	PD	Lattice embedding (post-quantum oriented)
TS-041	ENGENICA	PD	Cycle-based error handling (engineering)
TS-042	Vault	TS	Key mixing schedule (phyllotactic)
TS-043	Vault	NDA	Environmental entropy harvesting
TS-044	Vault	NDA	Multi-party key agreement
TS-045	Vault	NDA	Structured encryption on geometric keys
TS-046	Vault	NDA	Commitment / proof constructions (121-node)
TS-047	Vault	NDA	Signature family (spiral lattice)
TS-048	Core	TS	Cross-domain translation engine
TS-049	Core	TS	Hub multiplexing schedule
TS-050	business ops	TS	Commercial tier partition map

Lane counts (steward register): TRADE SECRET 24 · PATENT-DRAFT 8 · NDA 18. Categories span Wave, Mesh, Vault, Core, ENGENICA, manufacturing, testing, and business ops.

Inventory scope (high level)

The fifty rows above are the bounded inventory discussed with partners. It replaces vague “dozens of secrets” language with a numbered map—still without enabling disclosure.

What we never ship in the static site tree

Aligned with Safe public publish and repo hygiene:

Parameter-level secrets: exact recipes, tolerances, full stack-up tables, complete key schedules.
Private corpus indices, undisclosed skip tables, or vault recipes relied on commercially.
Credentials, production seeds, private monorepo dumps, or paths that telegraph undisclosed filing strategy.
Anything that would let a stranger clone an unreleased product from documentation alone.

External-safe habits (summary)

Replace specifics with ranges, qualitative descriptions, or generic toy examples.
Flag steps that depend on proprietary parameters instead of faking precision.
Use measured language: “designed to,” “may,” “roadmap,” “when benchmarked.”
Match audience: engineer gets architecture; investor gets economics; public gets non-enabling narrative.