Add the MIT License approved by the team

[sahilsinghthefirst]

Task [license] | GEML Goals 6-12 workshop plan | Size: S | Revised: 2026-07-26

Authoritative scope revision: This body supersedes the earlier production-scale wording. Goals 1-5 and their 250k-v1 corpus, EML trees, DAGs, motifs, and reports are immutable inputs: do not regenerate or modify them. The project is targeting a resource-bounded MathNLP workshop submission. Preserve failures, unsupported cases, invalid outputs, and timeouts as explicit rows.

Dependencies

Decision: the team has approved the MIT License. No further license-family choice is required.

Objective

Add the canonical MIT License with the correct copyright holder/year and expose it consistently in project/package metadata.

Exclusive file ownership

Owned paths - edit only these paths:

• LICENSE
• pyproject.toml - license metadata only
• README.md - license section/link only

Read-only dependencies:

• Existing authorship/copyright records
• Repository/package metadata outside the license fields

Tasks

• Add the unmodified canonical MIT License text with the team-approved copyright attribution.
• Set SPDX/package metadata to MIT and add a concise README link/statement.
• Check dependency and artifact notices for any required third-party attribution; report conflicts rather than changing licenses.
• Confirm generated/released artifacts reference the repository license where appropriate.

Acceptance criteria

• LICENSE contains canonical MIT text and the approved attribution.
• Repository, package metadata, README, and release checklist consistently say MIT.
• No incompatible third-party material is silently relicensed.
• License detection tools identify the project as MIT.

Validation

• Run package metadata validation and the repository-wide standard validation commands.
• Verify the public repository license detector after merge.

No individual test, lint, or smoke command may exceed approximately 30 minutes. Production experiment cells may run longer only when sharded, resumable, checkpointed, and independently auditable.

Out of scope

• Relicensing third-party dependencies/artifacts, legal advice, contributor agreements, or changing unrelated root files.

PR checklist

• I edited only the owned paths above and did not change another issue's contracts.
• I used only current repository specifications, the complete issue, authoritative public mathematical sources, and official library documentation.
• Tests use tiny hand-written or temporary fixtures and do not require outputs/ or production artifacts.
• I retained and reported every failure, timeout, unsupported input, and validation error.
• I recorded configuration hashes, exact seeds, commit/package/hardware metadata, and any scientific assumption or metric change.
• I ran python -m pytest, python -m ruff check ., and python -m ruff format . --check before handoff.

Clean-room rule: Do not inspect or reuse the prototype repository, its code, tests, schemas, helpers, architecture, or commit history. Stop and ask when a shared or scientific interface is ambiguous.