Licenses

The material discerndiscern↗A tool that installs and runs an agent development practice in a project. adds to your project has a different license from discern itself. This page explains which terms apply to each part, so you can identify what you are using or redistributing.

The portions discern supplies are available immediately under the Apache License, Version 2.0. These include setup scaffolding, built-in instructions and skills, generated framing, and the entries or marked regions discern maintains in shared configuration.

Your own instructions, mapMap↗The project's account of how its software works and why. pages, skills, configuration, and other authored material keep their existing terms. Provider and third-party material also keep their own terms. For example, an agent fileAgent file↗An instruction file a coding agent reads when it works on the project. can contain both discern's built-in instructions and your project's instructions: the Apache-2.0 grant applies to the portions discern supplied.

The files and ownership inventory identifies those portions for each registered destination. NOTICE states the legal scopeScope↗A named set of project paths used to select work or policy. and attribution.

discern itself uses the Functional Source License, FSL-1.1-ALv2. The project-payload grant does not relicense the executable, source repository, or manual. It also excludes user-selected documentation exports, Git-admin records, temporary output, and provider-local state. discern's software license does not extend into your project's own material.

Run discern licenses to read discern's software license, the project-payload license, NOTICE, and notices for third-party software bundled into the binary.

discern does not add a license file, notice, or legal header to your repository. If you redistribute discern-authored portions, you are responsible for the Apache-2.0 redistribution conditions, including giving recipients a copy of the license and preserving applicable notices.