Licenses

The material discerndiscern↗A tool that lets you hand real work to coding agents and still decide what joins your project. adds to your project comes under a different license from discern itself, and your own code and documents keep the terms they already had. This page shows which license covers each part, and what you're responsible for when you redistribute it.

Say you hand your recipe app's repository to a client, with discern's built-in instructions compiled into its AGENTS.md. The sections below answer the questions that raises: which license covers discern's part of that file, which covers yours, and what handing it over asks of you.

The portions discern supplies to your project are available immediately under the Apache License, Version 2.0. They include:

• setup scaffolding;
• built-in instructions and skills;
• generated framing;
• the entries or marked regions discern maintains in shared configuration.

Your own instructions, map pages, skills, configuration, and other authored material keep their existing terms, and so does material from coding-tool providers and other third parties.

One file can mix the two. The recipe app's AGENTS.md holds discern's built-in instructions beside your project's own, and the Apache-2.0 grant applies only to the portions discern supplied.

The files and ownership inventory shows, for each path discern registers, the license of the portions discern authored. NOTICE states the legal scopeScope↗A named area of your project, such as its documentation, defined by path patterns. and attribution.

discern itself is Fair Source software, under the Functional Source License, FSL-1.1-ALv2. The Apache-2.0 grant for project material doesn't relicense discern's executable, its source repository, or this manual. It also doesn't cover:

• documentation you choose to export;
• discern's records inside Git's administrative directory;
• temporary output;
• provider-local state, such as a coding tool's machine-local settings.

In the other direction, discern's software license doesn't extend into your project's own material.

discern licenses prints discern's software license, the Apache-2.0 license for project material, NOTICE, and the notices for third-party software bundled into the binary.

discern doesn't add a license file, notice, or legal header to your repository, so meeting Apache-2.0's redistribution conditions is your step. If you redistribute the portions discern authored, as you do when you hand the recipe app to your client, you're responsible for those conditions. They include giving recipients a copy of the license and keeping the notices that apply.