Code and data terms
Licenses and agreements have not been adopted.
The agreed direction
The intended model combines public documentation and formats, public source, community participation, and free research and use on one's own systems, including internal business use.
Incorporation into third-party products, customer-facing feeds, or managed fingerprint services is intended to require a separate agreement. The boundary will be defined by activity rather than naming particular vendors. Treatment of free third-party products still needs a decision.
Separate terms for separate material
Code, specifications, documentation, database snapshots, feeds, and contributions need their own scope and permissions. Public access and source availability do not imply unrestricted commercial reuse. Code with product-use restrictions will be described as source available.
Existing third-party rights remain intact. Compatibility with a method does not license its implementation or a database. Independently observed facts and rights in a collection must also be distinguished.
Before publication
The project must inventory ownership and existing terms, define the use-case boundary, draft code and data terms, establish contributor permissions, obtain legal review, and record adoption. Each published artifact will carry or link its applicable terms.