Licensing
How MAYAN ALFA materials are licensed, released, and governed.
MAYAN ALFA separates public research materials, public-safe release packages, protected core assets, and controlled archive evidence into distinct licensing and governance layers.
The release record, license file, DOI entry, product page, or written agreement controls over this general page when a more specific and legally consistent rule is stated.
License Matrix
The practical licensing model stays simple by separating unlike materials.
Public papers, public datasets, protected engine materials, and private registry assets are governed separately so reuse stays readable and release-safe.
Rights by material type
- Public papers CC BY-NC-ND 4.0, unless a specific release states otherwise.
- Public CSV datasets CC BY-NC 4.0, unless a specific dataset or DOI record states otherwise.
- MAYAN ALFA core engine All Rights Reserved. Protected source, computation logic, and internal implementation details are not part of the public release layer.
- Observation registry Private. Registry internals, protected archive state, and non-public orchestration materials remain outside public reuse.
Precedence rule
This page is a general public summary. The more specific rule wins whenever a release record, license file, DOI entry, product page, or written agreement states a narrower and legally consistent condition.
Release Channels
Each channel has its own role, boundary, and governance depth.
GitHub and Zenodo carry public-safe materials, while controlled archive layers preserve deeper validation evidence under stricter boundaries.
Public channels
- GitHub Public-safe 10M–10B documentation, reports, graphs, QA summaries, citation metadata, and governance documents.
- Zenodo Archival public-safe 10M–10B documentation and citation packages for DOI continuity.
Controlled access layers
- BRONZE / 10M–100B Research toolkit access layer aligned with the 10M–100B archive plan.
- SILVER / 10M–200B Publication archive access layer aligned with the 10M–200B plan.
- GOLD / 10M–500B Controlled validation archive aligned with the 10M–500B plan, including the selected 100B–500B extension.
Future branch
- Future ultra-scale branch A future ultra-scale archive branch may be added later for higher validation ranges, extended reproducibility packages, and stricter controlled-release governance. It is not part of the current public release.
Central Governance
Centralized governance keeps licensing language, release boundaries, and public claims consistent.
- Core principle Observation-first language: measurements, reproducible reports, bounded comparisons, platform context, and careful interpretation.
- Product boundary GitHub and Zenodo stay public-safe at 10M–10B. BRONZE aligns with 10M–100B, SILVER with 10M–200B, and GOLD with 10M–500B, including the controlled 100B–500B validation extension.
- Governance purpose Central governance protects the project against policy drift, accidental data leakage, unsupported public claims, and inconsistent release interpretation.
Governance Files
Governance files define interpretation, publication limits, and release consistency.
These files are part of the governance layer, not background notes.
Citation and claims
CITATION.cff, CLAIM_BOUNDARY_STANDARD.md, CLAIM_AND_RELEASE_BOUNDARY.md, DISCLAIMER.txt, OBSERVATION_FIRST_POLICY.md
Release and migration
README_MASTER_GOVERNANCE.md, PUBLIC_RELEASE_POLICY.md, MIGRATION_AND_DATA_POLICY.md, THROUGHPUT_PUBLIC_BOUNDARY_NOTE.txt
Rights and protection
LICENSE.txt, LICENSE_MATRIX.md, PROTECTED_CORE_NOTICE.txt, TERMS_OF_USE.txt
Gold governance map
README_GOLD_GOVERNANCE.md, GOVERNANCE_FILE_EXPLANATION.md, RELEASE_CHANNEL_RULES.md
Security and Exclusions
Public workpacks stay bounded, and protected-core materials stay excluded.
Public workpacks may include canonical CSV files, benchmark reports, graphs, audit summaries, public methodology notes, and bounded public benchmark evidence only.
Public workpacks must not include MAYAN C source files, internal computation kernels, secret layers, proprietary heuristics, build binaries, private orchestration internals, full internal backup ZIP files, or controlled ultra-scale reference materials.
GOLD / 10M–500B packages may contain selected 100B–500B validation materials, but they remain controlled archives and still exclude protected core source code unless a separate written license says otherwise.
Public Use and Permissions
Public use is allowed within attribution, boundary, and non-commercial discipline.
Allowed public use
Reading public reports, reproducing public benchmark methodology where possible, citing the project, using public graphs and tables with attribution, and academic or educational discussion.
Not allowed without written permission
Commercial resale, redistribution of controlled or private layers, removal of attribution, authorship claims, presentation of results as guaranteed universal mathematical claims, or use of MAYAN ALFA as a cryptographic assurance tool.
- Attribution Use the project name and author credit as stated in the release.
- Public boundary Public benchmark evidence is bounded to the approved public layer; controlled and private layers stay separate.
- Precedence The release page, license file, DOI record, product page, or written agreement overrides general wording when more specific.
- Permissions Reuse requests must be confirmed in writing when the intended use is not clearly covered by the public license.
