Skip to content

AGENTS.md

Latest commit

 

History

History
43 lines (35 loc) · 2.37 KB

AGENTS.md

File metadata and controls

43 lines (35 loc) · 2.37 KB
Raw

Repository agent instructions

This repository contains draft license text and preliminary legal research. It does not provide legal advice, and an agent's research is not an adoption or licensing decision.

Keep the reusable license separate from adopting projects

Treat this repository like a repository of reusable license text. It does not need a universal software owner. A maintainer or steward of the canonical text controls text publication and versioning only; that role does not by itself make the person a copyright owner, licensor, separate-permission grantor, beneficiary, or enforcement claimant for software placed under the license.

For every adoption or enforcement question, identify the applicable software Contributor or rightsholder separately. Separate written permission can come only from all rightsholders whose authorization is necessary or from someone independently authorized by them; do not assume anyone must offer it. Do not investigate the ownership, contribution history, or source-file headers of the FastLED codebase merely because the license is named FastLED. Those facts are relevant only when the question specifically concerns FastLED adoption, FastLED rights, or enforcement involving FastLED software.

The AI Coding Agent Notice is different: it is generic, reproduced as Exhibit C, and incorporated into the License by Section 11.7. Treat inclusion of the complete notice as an adoption and source-distribution requirement. Do not describe it as an optional FastLED-specific companion. Keep that inclusion condition distinct from the notice's statement that an automated agent is not itself made a contracting party or independent enforcement target.

For any request involving license interpretation, enforcement, infringement, remedies, litigation, statutes, cases, or legal strategy:

  1. Read paralegal-research/AGENTS.md completely.
  2. Check paralegal-research/INDEX.md before searching the web or opening a new GitHub issue.
  3. Treat a matter memo in that index as the canonical research record. GitHub issues are discussion and action mirrors, not the source of truth.
  4. Keep research separate from changes to LICENSE. Do not turn a researched scenario into license text unless the user expressly asks for drafting.
  5. Preserve the attorney-review gate in LEGAL-REVIEW.md.

For non-legal work, follow the repository's existing documentation and tests.