China Open-Model Visits: Separate Access from Rights
Downloading model weights is not the same as receiving every commercial right. Separate the model, code, data and distribution terms before a pilot recommendation.
Direct answer. Ask which exact components are available, under which current terms and for which intended use. 'Open' describes neither a complete license inventory nor automatic permission for your deployment.
Identify the actual artifacts
For a China open-model company visit, request the model name and version, distribution location, license text and the runtime dependencies used in the demonstration. Do not assume that a community mirror carries the same terms as the original publisher.
Keep legal interpretation with qualified counsel. This article supplies an evidence inventory, not advice that a license permits a particular commercial activity. Terms may change, and a conclusion must refer to the artifact and terms actually reviewed.
Build a component-rights table
| Component | Evidence to request |
|---|---|
| Model weights | Publisher, version and governing terms |
| Runtime code | Dependency and license inventory |
| Data representations | What is disclosed about permitted inputs or training data |
| Distribution | Conditions on modifications and onward supply |
Ask the host what obligations it accepts in the commercial agreement and which remain with the customer. A supplier's verbal description of openness is not a contractual warranty. Keep the demonstration artifact distinct from the proposed production package; additional dependencies may appear later.
Third-party and intellectual-property risk themes in NIST AI RMF Core provide a voluntary rationale for inventorying these questions. They do not interpret a model license or resolve a rights dispute.
Set a practical next step
Before a pilot, have procurement and counsel review the exact versions and intended distribution. An internal sandbox, a hosted customer service and redistribution of a modified package can present different questions. Avoid collapsing them into one yes-or-no label.
Use the company due-diligence checklist to capture artifact references and review owners. Discuss a model-focused immersion when your team can state its proposed use without relying on the word 'open' as a substitute for evidence.