# Licensing And Packaging

## Current Public Posture

This repository is public for discovery, evaluation, and discussion, but it is not currently released under a permissive open-source license.

Current stance:

- public visibility: yes
- source available for evaluation: yes
- automatic redistribution rights: no
- automatic commercial reuse rights: no
- custom licensing path: yes

The repository-level [LICENSE](../LICENSE) intentionally keeps the public posture conservative.

## Why Use This Posture

This suite is currently more valuable as a productized capability package than as a fully open commodity asset.

That matters because the repo is not just "content." It contains:

- workflow topology
- stage sequencing logic
- downstream packaging assumptions
- validation assets
- commercialization potential

If you are still exploring packaging, consulting, licensing, or white-label opportunities, a conservative public license buys you time.

## Recommended Packaging Layers

### Layer 1: Public Showcase Repo

Purpose:

- discovery
- credibility
- audience building
- inbound interest

What stays public:

- repo overview
- skill catalog
- example output
- validation story
- promo page

### Layer 2: Private Commercial License

Purpose:

- internal team use
- client delivery
- commercial game pipeline use

Typical additions:

- private support
- adaptation guidance
- internal enablement
- versioned updates

### Layer 3: Bespoke Workflow Package

Purpose:

- genre-specific customization
- studio-specific terminology
- integration into an existing design pipeline
- validator or output adaptation

Typical additions:

- custom stage tuning
- custom example pack
- revised downstream contracts
- new reference templates

## Suggested License Boundaries

If you keep this repo public while monetizing it, make these boundaries explicit:

- public viewing is allowed
- evaluation is allowed
- copying into commercial internal workflows requires permission
- redistribution, resale, bundling, or white-labeling requires permission
- custom commercial licenses are negotiated separately

## Practical Commercial Models

Best fits for the current maturity level:

- paid private license
- consulting plus enablement
- custom workflow adaptation
- workshop plus template bundle

Less suitable right now:

- low-price self-serve SaaS
- mass-market consumer subscription
- open-core with thin paid upsell

## When To Change The License

Consider moving to a more open model only if:

- the real revenue comes from services, not exclusivity
- you want broad community adoption faster than tight control
- you already have a stronger private premium layer
- you are ready for forks, derivatives, and repackaging pressure

Until then, the current public-but-protected posture is coherent.