Decision: the engines (barakoCMS core, BaryoVM, the barako CLI) stay MPL-2.0; everything built on them is MIT

Record the licence rule for the barako ecosystem, decided with Arnel on 14 September 2026.

## The rule

"The core, the soul, the bitterness of the coffee stays MPL-2.0. The rest is on the house." The bitterness is the three engines.

- **MPL-2.0:** barakoCMS core (`barakoCMS/`, the API), BaryoVM, and the barako CLI (#801).
- **MIT:** everything built on them: barakoCMS modules, barakoCMS.Testing, barakoCMS.Suite and the module template, barakoBrew, barakoPress, create-barako-app, shots and grind.

Each product changes from its next release. Versions already published keep the licence they shipped with.

## Why

- MPL-2.0 was chosen so improvements come back. That still matters for the engines everything depends on: the API every product calls, the deploy tool and the CLI that act on live systems. It applies per file, so it never reaches MIT code that uses them.
- For everything built on the core, copyleft only adds a procurement conversation (ROADMAP.md already says to state the cost of MPL-2.0 first). MIT removes it for modules, plugins, consoles, sites, the deploy tool and a future paid module (#586).
- A move to MIT stays possible for the engines later; a move from MIT back to copyleft never is.

## Consent

- Modules and barakoBrew move under the existing contributor terms: `CLA.md` clause 2 names MIT, and contributions before 23 August 2026 were made under terms that granted relicensing.
- BaryoVM stays MPL-2.0, so MrBeldum's `vm exec` (BaryoDev/BaryoVM#71) needs no agreement.

## Boundary rule

Code copied from an engine into an MIT package keeps its MPL-2.0 notice. Moving files across the line is deliberate and reviewed.

## Done when

- The rule is a numbered record in `DECISIONS.md`, and the licence sections of `README.md`, `ROADMAP.md`, `docs/compliance-posture.md` and `DEVELOPMENT_STANDARDS.md` describe the split.

Plan page: https://claude.ai/code/artifact/09aef3dd-936d-432a-8056-9ef9bccfe8df

Start by reading the existing licence sections in DECISIONS.md, README.md, ROADMAP.md, docs/compliance-posture.md and DEVELOPMENT_STANDARDS.md. Record the approved MPL-2.0/MIT split as a numbered decision and align those sections with the stated engine boundary, release timing and copied-code notice rule. Done means all five documents consistently describe the decision.

Written by the indexing model from the issue text.