# Licensing and Reuse Review

**Date:** 2026-09-01  
**Nature:** Engineering planning summary, not legal advice.

## Production Selection Update

Phase 0B selected **AI-DnD (MIT)** as the production fork/base. The production strategy therefore remains on a permissive-license path.

The project may reimplement compatible ideas from other projects, but direct source copying must still be reviewed file-by-file and retain applicable notices. GPL/AGPL projects remain concept/reference sources unless a later explicit licensing decision changes that policy.

Maintain third-party notices from the first production milestone.

## Permissive finalists

### AI-DnD
- License: MIT
- Direct modification/forking is generally compatible with a permissive local application, subject to preserving required notices.

### Open Dungeon
- License: MIT
- Same practical advantage for direct reuse.

### ai-adventure
- License: Apache-2.0
- Permissive, but Apache notice/license obligations must be preserved.

These three can plausibly participate in a permissively licensed implementation strategy, subject to checking individual vendored/third-party files.

## Permissive reference projects

Static repository licensing indicates:
- Chronicler: MIT
- Interactive Fiction Framework: MIT
- Gamentic: MIT
- Sonder Engine: MIT
- Corvus Story Core: MIT

If source is copied, retain the applicable notices and verify whether particular directories/files carry separate licenses.

## Copyleft references

### aiMultiFool
- GPL-3.0
- Treat as a concept/reference source unless the final project intentionally accepts GPL obligations.

### LettuceAI
- AGPL-3.0
- Reference only for this project unless there is a deliberate licensing decision.

Mature roleplay ecosystems such as SillyTavern/RisuAI/KoboldAI should have their exact current license verified before any code copying. No direct reuse is currently recommended.

## Media dependencies

Important distinction:
- application code license,
- media runtime license,
- model-weight license
are separate.

For example Gamentic documents:
- its own code under MIT,
- ComfyUI runtime under GPL-3.0,
- model weights under their own terms.

Using a separately running local service through an API is architecturally different from copying its code into the storyteller, but distribution/bundling choices should be reviewed before release.

## Recommendation

Keep the production application's own code on a permissive-license path if possible:
- primary fork from MIT or Apache-2.0,
- copy code only from compatible permissive sources,
- treat GPL/AGPL projects as design references unless a conscious license change is made,
- keep optional media providers as external adapters/services where practical,
- maintain a third-party notices file from the first production milestone.