Gemini research proposes permission checks for model training

A new report proposes excluding Gemini-generated training material from Nemotron adaptation unless a governing agreement expressly permits the workflow. It compares access routes, exceptions and commercial exposure.

· commit 9fd1881

Proposed training permission checks

The report proposes explicit authorization for synthetic training material and review of labels, critiques, evaluations and coding assistance. It also proposes retaining agreement versions and artifact provenance with admission decisions.

docs/GEMINI_COMMERCIAL_RESTRICTIONS_RESEARCH.md

Separate access routes

The report examines consumer, API, Cloud and Workspace restrictions separately. The audit now distinguishes these contracts from privacy guidance and adds contract entries to its source register.

docs/GEMINI_COMMERCIAL_RESTRICTIONS_RESEARCH.md, docs/FRONTIER_LAB_IP_AND_CREATOR_REWARDS_AUDIT.md

Permission, credit and payment

The report proposes separate decisions for permission, attribution and payment. Its proposed handling requires contribution permissions directly from parties able to grant them.

docs/GEMINI_COMMERCIAL_RESTRICTIONS_RESEARCH.md

Gemma licensing comparison

The report compares Gemma licensing separately from Gemini service restrictions. The proposed project target remains Nemotron 3 Ultra; the report presents Gemma as a licensing comparison.

docs/GEMINI_COMMERCIAL_RESTRICTIONS_RESEARCH.md

Documentation index

The README now lists the Gemini report, including its coverage of restrictions, limited exceptions, commercial exposure and Gemma licensing.

README.md

Files in this change

A machine wrote this summary from the change. Read the source before you quote it.

All updates