License and IP posture
The binding license for any Monolythium artifact is the license delivered with that exact artifact. Marketing copy and this documentation cannot add rights that its license does not grant.
Findings
Section titled “Findings”| Question | Current answer |
|---|---|
| Is the node implementation public? | No. mono-core is internal and unpublished. |
| Can an external reviewer rebuild or fork the node from public source? | No. There is no public core source tree today. |
| Does an SDK or whitepaper license cover the core implementation? | No. Separate artifacts do not extend their terms to unpublished code. |
| Is a future core license guaranteed by this page? | No. Only a binding license shipped with a future publication can establish those rights. |
Diligence method
Section titled “Diligence method”For every artifact, capture its immutable revision, release provenance, and license-file digest. Review dependency licenses separately. Treat repository descriptions, future-open-source statements, and historical license summaries as non-binding until the exact source and terms are published.
Public security summaries may describe outcomes, but internal review notes, custody material, incident procedures, and private repository contents remain outside the public documentation boundary.
Consequence for “fork as exit”
Section titled “Consequence for “fork as exit””Forking remains a governance principle. It becomes an independently usable exit only after the implementation, sufficient build material, and applicable license are public. See Fork as exit and Public repositories.