[Patents/IP] Perform an internal patent-risk review before material commercialization

[KeyffMS]

Decision

SightAdapt will not require or plan an external patent freedom-to-operate opinion. Patent risk is handled through an internal public-source review, product-scope controls and explicit maintainer risk acceptance.

The project must not claim that SightAdapt is patent-free, patent-cleared, non-infringing or covered by an FTO opinion.

Current state

The current free/open-source alpha has no defined paid launch, enterprise warranty, indemnity, commercial territory set or large-scale deployment requiring a separate review project now. The technical feature map and internal review procedure are documented in docs/legal/PATENT-FTO-GATE.md.

Internal review criteria for a future material commercial scope

• Define activities, territories, channels, customers and representations.
• Review the technical feature map for the exact release.
• Search relevant public patent databases and technical sources.
• Record potentially relevant families, owners, dates, status and territories where identifiable.
• Record uncertainty where claim interpretation or status cannot be resolved internally.
• Decide whether to accept risk, narrow/remove a feature, exclude a territory/use, seek a license or block the launch.
• Preserve a repository-safe maintainer decision and re-review triggers.
• Avoid patent-clearance and non-infringement claims.

Reopening triggers

Reopen this Issue when a concrete material commercial scope exists, a major rendering/capture/automation mechanism changes, or a patent assertion/licensing request is received.

Implementation

• PR Document patent FTO commercialization gate #133 created the technical feature map and commercialization gate.
• PR Replace external audit gates with maintainer risk decisions #139 replaced the external-opinion requirement with an internally achievable public-source risk review.

Closing as not planned for the current free/open-source alpha stage; the internal process remains available when a concrete trigger occurs.

[KeyffMS]

PR #133 records the current non-commercial decision, technical feature map and mandatory professional FTO gate. No patent attorney opinion has been obtained and the repository does not claim patent clearance. Closing this issue as not planned for the current free/open-source alpha stage. Reopen this issue before paid licensing, enterprise warranties/indemnities, investor non-infringement representations, major commercial deployment or a material rendering/capture/automation change.

[KeyffMS]

Wynik audytu uzupełniającego — 2026-07-30

Ocena: zadanie merytoryczne nie zostało wykonane; ponownie otwarte.

Repozytorium zawiera techniczną mapę funkcji i bramkę komercjalizacji, ale nie przeprowadzono wyszukiwania claim-oriented, analizy aktywnych roszczeń, mapowania claimów ani profesjonalnej opinii FTO. Zamknięcie jako not planned było uczciwe dla etapu alpha, lecz nie realizowało target state tego Issue.

Pozostałe prace

• zdefiniować planowane działania komercyjne, terytoria, klientów, kanały, skalę i żądane gwarancje;
• zlecić kwalifikowanemu patent attorney/professional wyszukiwanie rodzin i analizę aktywnych claimów;
• przygotować claim mapping oraz warianty design-around/licensing dla ryzyk materialnych;
• przechowywać opinię i claim charts poza publicznym repozytorium;
• dodać niepoufny rekord decyzji dla dokładnej wersji, aktywności i terytoriów.

Issue pozostaje bramką przed płatną dystrybucją, enterprise warranties/indemnities, investor representations i dużym wdrożeniem komercyjnym.

[KeyffMS]

Triage priority — P2

Reason: no professional patent freedom-to-operate review has been performed. The current free/open-source alpha model does not yet trigger the commercial gate, but the issue remains an explicit prerequisite for paid or warranted use.

Close only when:

• commercial activities, territories, customer types and exact product scope are defined;
• qualified patent counsel completes the required claim/status/territory analysis;
• a non-confidential decision record is tied to the exact reviewed version and activity;
• mandatory design-around, licensing or scope conditions are completed.

Escalation: immediately move to P0 before paid licensing, enterprise warranties/indemnities, investor non-infringement statements or major commercial deployment.