# Clear license boundaries between MIT and Enterprise features

## Summary

I'm trying to use LiteLLM in compliance with its licenses. The root `LICENSE` says code outside `enterprise/` is MIT-licensed. But I found that many features documented as "Enterprise" have their gating logic and, in many cases, their entire implementation in MIT-licensed files. So I can't determine which features I can legally use without a subscription. I'm asking for clear, physically-enforced boundaries.

## The Problem

The root `LICENSE` draws a clear rule:

> All content that resides under the "enterprise/" directory [...] is licensed under the license defined in "enterprise/LICENSE". > Content outside of the above mentioned directories [...] is available under the MIT license.

So I should be able to look at any file path and know its license. But the current codebase doesn't follow this boundary:

### Category A: Enterprise feature gating in MIT files (25+ files)

A grep for `premium_user`, `_premium_user_check`, and `not_premium_user` shows that the enforcement mechanism for enterprise features lives almost entirely in MIT-licensed files:

| MIT file | What it gates | |---|---| | `litellm/proxy/co…