Research program
From Product to Rights
This program shows how to move from a product to the rights that protect it. Break the product into the assets that create value, then use the narrowest controls that can do a real commercial job, whether patent, secret, contract, data right, publication, or mark. It matters because a first product can disappear while the underlying principle stays useful.
Which combination of patent, secret, contract, data right, publication, mark, access, and operating control best protects the actual advantage?
Separate the product from the asset
The first product can disappear while the underlying principle remains useful. Map the current product, technical principle, broader insight, alternate implementations, adjacent uses, and possible rights. This prevents one early architecture from setting the permanent boundary of the work.
The same insight may support a product, a platform, a license, an operating method, or several field-specific uses. Each route needs different evidence and control.
Choose the narrowest useful control
Patents, trade secrets, know-how, data rights, contracts, copyright, marks, exclusive supply, standards work, regulatory position, distribution agreements, options, licenses, and assignments solve different problems.
Patent what can be supported and observed. Keep difficult-to-discover process knowledge secret when secrecy is practical. Use contracts for access and duties. Publish what should stay open. Use marks to identify source. Do not collect rights that have no work to do.
Protect what can be observed and proved
A broad right can be weak in practice when use is hidden inside source code, a private model, or an internal process. Review each material element on a spectrum from publicly observable to inferable, discoverable only with access, or effectively hidden.
Record possible evidence from product behavior, outputs, latency, interfaces, documentation, filings, and public technical material. Observability is a commercial screen, not an infringement opinion.
Learn without giving away the option
Customer interviews, pilots, demonstrations, conference talks, papers, websites, repositories, and partner work can disclose more than intended. Plan the learning sequence before the first public act.
Test value through outcomes and buyer behavior where possible. Put decision gates before technical disclosure. Counsel should determine filing and disclosure consequences, especially outside the United States.
Keep an invention provenance record
Record the original human observation, problem framing, contributor roles, material prompts and outputs, alternatives adopted or rejected, experiments, code or design records, customer discoveries, and filing or publication milestones.
The record supports review. It does not decide inventorship. It should be useful enough to maintain during the work rather than reconstructed after memories have faded.
Run Alpha to Patent and Alpha to Operate together
Owning an advantage does not create freedom to build or sell it. Map the product wedge, components, data, standards, platform terms, open-source duties, third-party patents, regulatory permissions, upstream rights, and downstream licenses in parallel with the protection strategy.
The result may call for a license, redesign, narrower field, different supplier, or a decision not to proceed. Freedom to operate remains a legal question for counsel.
Put rights where commerce happens
Geographic filing should follow customers, competitors, manufacturing, deployment, suppliers, licensing prospects, enforcement value, regulation, and cost. A familiar filing list is not a commercial reason.
Open parts of a system when standards, interfaces, reference implementations, or shared formats increase adoption and make the scarce complement more valuable. Keep the reason for each open, licensed, proprietary, secret, or patented layer in the record.
Rights review
A right advances only when its owner, purpose, evidence, cost, observability, dependency, and next decision are clear.
| Asset | Possible control | Question that matters |
|---|---|---|
| Claimable mechanism | Patent | Can it be supported, observed, and used? |
| Hidden operating method | Secret or know-how | Can secrecy be kept? |
| Data and access | Contract and data rights | Is the intended use permitted? |
| Public interface | Publication or standard | Does openness strengthen the complement? |
| Product wedge | Dependency and FTO review | Can it be operated without unacceptable risk? |
Research notes
Alpha to Operate dependency and rights map
This note gives a way to see which rights a product wedge already has and which it still lacks, so gaps surface before a build, sale or license decision. It is an issue map for qualified review, not a freedom-to-operate opinion. Map the rights owned and the rights still needed to build, sell, deploy, manufacture, distribute, or license a product wedge.
Alpha to Rights decision memo
Match each scarce asset to the narrowest control that can protect and commercialize it. This memo helps a reader choose among patent, secret, contract, license and other rights, so the firm acquires a right only when it has a commercial job, not because the right is available.
Commercial discovery and IP optionality checklist
Plan customer learning, demonstrations, and publication without casually surrendering useful options. The checklist places a review before pilots, demos, papers, repositories, and public launches, and favors outcome, problem, and workflow questions that need little technical disclosure. Counsel should decide disclosure and filing consequences.
Infringement observability review
Test whether important use can be observed and evidenced without assuming access to a competitor's private systems. The review places each material element on a spectrum from publicly observable to effectively hidden and records commercial importance, evidence difficulty, and questions for counsel. It is not a claim chart or infringement conclusion.
Invention provenance record
This note gives a reviewable chronology that connects each material choice to the evidence and person responsible, and that can be handed to counsel and diligence teams. The record does not determine inventorship or ownership. Keep a dated record of human insight, source material, AI assistance, experiments, decisions, and claimed contribution.
Open and closed architecture map
Decide which layers should be open, standardized, licensed, proprietary, secret, or patent protected. The map gives a reason for each layer and names the right, duty, owner, field, and exit path for every closed one, so a commodity layer is not closed when control costs more than it returns.
Related
- Evidence, Economics, and Rights
- Invention provenance record
- Alpha to Operate dependency and rights map