LeanCert Python SDK Licensing Notice

Copyright (c) 2026 Alejandro Radisic. All rights reserved except where an
applicable license expressly provides otherwise.

Post-Baseline SDK Material
--------------------------

The authoritative file-level classification for this repository is
`LICENSE_SCOPE.toml`. Material governed by the LeanCert Evaluation License is
identified there explicitly; unmatched or overlapping paths are manifest
errors and receive no license merely by omission. The manifest records commit
716cb2d (tagged `v0.3.2-apache-final`) as the historical boundary used to
classify mixed-origin files. The evaluation license is available at:

    LICENSES/LeanCert-Evaluation-1.0.txt

That license permits defined non-production evaluation, testing, education,
and non-commercial research. It does not permit production use, commercial
product development, client services, or network-service deployment without
a separate written commercial license. This is a source-available license,
not an open-source license.

Commercial licensing information is available in `COMMERCIAL.md`.

Earlier and Separately Licensed Material
----------------------------------------

* Python SDK material available at or before commit 716cb2d, including the
  versions tagged `v0.3.0`, `v0.3.1`, and `v0.3.2-apache-final`, remains
  available under the Apache License, Version 2.0. Those previously granted
  rights are not revoked or restricted by this notice. A copy of that license
  is available at `LICENSES/Apache-2.0.txt`.
* LeanCert Core and LeanCert Bridge are separate projects distributed under
  the Apache License, Version 2.0. Bundled copies remain governed by their own
  license and notice files.
* Third-party components remain governed by their respective licenses.

No Contributions During Provisional Period
------------------------------------------

The project is not accepting third-party code contributions to the v1
overhaul while these terms are provisional. Please do not submit code unless
the copyright owner has agreed to contribution terms in writing.

Licensing inquiries may be made through the contact information published on
the repository owner's GitHub profile.
