Llama 3.2 Community License Agreement

info Rubric 1 dct:title applied

File name, record identifier and IRI local name agree. The agreement has no SPDX identifier, so no spdx:licenseId triple is written. dct:title is the heading of the document; the short form, the full form and the model-hub tag are in dct:alternative.

major Rubric 2 odrl:target applied

dcmitype:Dataset and dcmitype:Software. The licensed material is defined as "collectively, Meta's proprietary Llama 3.2 and Documentation (and any portion thereof) made available under this Agreement", and Llama 3.2 is defined as "the foundational large language models and software and algorithms, including machine-learning model code, trained model weights, inference-enabling code, training-enabling code, fine-tuning enabling code and other elements of the foregoing": trained weights are data, the code is software, and the documentation travels with both.

major Rubric 3 odrl:permission applied

Clause 1.a grants "a non-exclusive, worldwide, non-transferable and royalty-free limited license under Meta's intellectual property or other rights owned by Meta embodied in the Llama Materials to use, reproduce, distribute, copy, create derivative works of, and make modifications to the Llama Materials." That gives odrl:reproduce, odrl:distribute, odrl:modify, odrl:derive, cc:DerivativeWorks and dalicc:ModifiedWorks. cc:CommercialUse is permitted because the agreement names no limit of purpose and instead writes its commercial limit as a user threshold in clause 2, which is quoted and reported as a gap. dalicc:useForModelTraining is permitted and carries a dalicc:addStatement duty, because clause 1.b.i says in terms that you may use the material "or any outputs or results of the Llama Materials to create, train, fine tune, or otherwise improve an AI model" provided the new model's name begins with the mark. dalicc:networkUseTrigger carries the same clause, which reaches "a product or service (including another AI model) that contains any of them", with the same duties as distribution. dalicc:sublicense is left out in either position: the grant is "non-transferable" but the agreement says nothing about sublicensing.

major Rubric 4 odrl:prohibition applied

Three prohibitions. dalicc:ChangeLicense because the agreement must travel with the material and with any derivative works thereof, and the text gives no leave to put it under other terms. dalicc:promote from clause 5.a, "No trademark licenses are granted under this Agreement, and in connection with the Llama Materials, neither Meta nor Licensee may use any name or mark owned by or associated with the other", with the narrow licence of the mark for the display duty noted in the quoted clause. dalicc:patentRetaliationTermination from clause 5.c, under which litigation alleging that the material or its outputs infringe your rights ends every licence granted by the agreement; the clause is wider than patents and ends the whole agreement, which is what the term allows for.

major Rubric 5 odrl:duty applied

Five duties on odrl:distribute, the same five on dalicc:networkUseTrigger, and one licence-wide duty. cc:Notice comes from clause 1.b.i(A), the duty to "provide a copy of this Agreement with any such Llama Materials". dalicc:addStatement comes from clause 1.b.i(B), the duty to "prominently display “Built with Llama” on a related website, user interface, blogpost, about page, or product documentation". cc:Attribution and dalicc:includeNoticeFile come from clause 1.b.iii, the attribution notice "within a “Notice” text file distributed as a part of such copies". cc:ShareAlike carries the fact that the agreement travels with the material and with any derivative works thereof. The licence-wide duty is dalicc:exportControlNotice, from clause 1.b.iv. The duties hang on dalicc:networkUseTrigger as well because clause 1.b.i reaches "a product or service (including another AI model) that contains any of them".

minor Rubric 6 dalicc:WarrantyDisclaimer applied

Clause 3 goes to dalicc:WarrantyDisclaimer and clause 4 to dalicc:LiabilityLimitation, each whole and verbatim. dalicc:additionalClauses carries the definitions, the acceptance sentence, the grant and the redistribution conditions, the additional commercial terms, the intellectual property clause, the term and termination clause, the governing law clause and one literal that quotes the incorporation clause of the acceptable use policy and gives its address. Curly quotation marks in the source are kept.

minor Rubric 7 cc:jurisdiction applied

cc:jurisdiction is dalicc:worldwide, from the worldwide grant, while dalicc:governingLaw names California: "This Agreement will be governed and construed under the laws of the State of California without regard to choice of law principles". The two are different things and both are stated. dalicc:validityType is dalicc:perpetual, because the term runs from acceptance until terminated rather than for a fixed period, and dalicc:terminatesOnBreach is true from "Meta may terminate this Agreement if you are in breach of any term or condition of this Agreement." No cure period is given.

gap Rubric 8 dalicc:additionalClauses none

The commercial limit is a user threshold, and no term can hold it: "If, on the Llama 3.2 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee's affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights." Neither cc:CommercialUse nor dalicc:fieldOfUseRestriction says "above this size the grant stops". Quoted; the proposed term is dalicc:scaleThresholdCondition, an annotation carrying the measure and the number.

gap Rubric 8 dalicc:fieldOfUseRestriction none

The acceptable use policy is a separate document incorporated by reference: "Your use of the Llama Materials must comply with applicable laws and regulations (including trade compliance laws and regulations) and adhere to the Acceptable Use Policy for the Llama Materials (available at https://www.llama.com/llama3_2/use-policy), which is hereby incorporated by reference into this Agreement." dalicc:fieldOfUseRestriction names the field in a short literal, but there is no term for a policy the licence pulls in by reference and whose content is not in the text. The incorporation clause and the address are quoted in one literal of dalicc:additionalClauses; the proposed term is dalicc:incorporatedUsePolicy, an annotation carrying the address.

gap Rubric 8 dalicc:additionalClauses none

Clause 1.b.i ends with a naming rule that no duty action carries: "If you use the Llama Materials or any outputs or results of the Llama Materials to create, train, fine tune, or otherwise improve an AI model, which is distributed or made available, you shall also include "Llama" at the beginning of any such AI model name." dalicc:rename asks for a name that distinguishes the changed work from the original; this asks for the opposite, a name that ties it to the original. dalicc:addStatement carries the "Built with Llama" line but not the prefix. Quoted; the proposed term is dalicc:derivativeNamingRequirement, a duty action.

info Rubric 9 record none

The consistency check of app.services.composer against dg_default returned an empty conflict list. The cc:ShareAlike duty sits on the acts rather than on the odrl:Set, so it does not meet the dalicc:ChangeLicense prohibition in the rule about whole-work reciprocity.

info Rubric 10 record none

Family: the fourth of the six. From the third edition on the six texts are the same agreement with a different version name: clause 1.b.v, the bar on improving another model, is gone, the built-with line loses the version number, the naming rule reaches a model trained on the outputs, and everything else stands. The four records from the third edition on carry identical statements; they differ only in the identifiers, the titles, the addresses and the quoted version names.

major Rubric 5 odrl:duty applied

The agreement must accompany the Llama Materials and derivative works, but the text does not require a derivative to be licensed under it: clause 1.b.i reads "If you distribute or make available the Llama Materials (or any derivative works thereof), or a product or service (including another AI model) that contains any of them, you shall (A) provide a copy of this Agreement with any such Llama Materials; and (B) prominently display “Built with Llama” on a related website, user interface, blogpost, about page, or product documentation." The record therefore carries a notice duty and not share alike. The cc:ShareAlike duty is removed from the acts it hung on, and the dalicc:ChangeLicense prohibition written on 2026-09-22 is replaced by a dalicc:ChangeLicense permission with the dalicc:compliantLicense duty, as Apache-2.0 carries it: a derivative may be offered under other terms as long as the copy of the agreement and the notice travel with the Llama Materials. The cc:Notice duty the record carries already states that the copy must travel.