Add a valid MIT LICENSE (platform license audit)

[Polichinel]

Add a valid MIT LICENSE to main and development

Neither main nor development contains a LICENSE file.

To do

• Add a canonical MIT LICENSE file to development.
• Merge/propagate it to main.

What "valid MIT" means here

• A root LICENSE file containing the canonical MIT text — the Permission is hereby granted, free of charge… grant through the THE SOFTWARE IS PROVIDED "AS IS"… warranty-disclaimer clause.
• A filled-in copyright line: Copyright (c) 2026 <author names> (use the holder convention already used across the sibling repos — not the [year] [fullname] template placeholder).
• Present so that the platform check "MIT on main or development" passes.

Reference — copy how it is already done

• LICENSE file: https://github.com/views-platform/views-frames/blob/main/LICENSE
• pyproject metadata: https://github.com/views-platform/views-frames/blob/main/pyproject.toml

Repos already compliant (use any as a template): views-frames, views-hydranet, views-models, views-pipeline-core, views-reporting.

---

Filed from a platform-wide license audit on 2026-06-24. 9 of 17 repos lacked a valid MIT license on main/development; this is one of them.

[Polichinel]

Progress (2026-06-24): ✅ canonical MIT LICENSE added to development (PR #48, commit 1b1a661) — byte-identical to the sibling repos, holder Copyright (c) 2026 Dylan Pinheiro and Simon Polichinel von der Maase; license = "MIT" declared in pyproject.toml. The platform check now passes on development.

◻ Remaining: propagate to main. That's a development→main release decision (development is well ahead of main with unrelated merged work — reconciliation, mapper deletion, LFS retirement, etc.), so it should ride the next planned release rather than a LICENSE-only cherry-pick — your call. Leaving this issue open until main has it.

[Polichinel]

Done — a valid MIT LICENSE is present on development. Closing.