Fork as exit
Forking is part of Monolythium’s governance philosophy: a community should be able to leave rather than depend on protocol-level voting. That principle is not the same as a presently exercisable source-code right.
Current boundary
Section titled “Current boundary”mono-core is internal and unpublished. The public cannot inspect, clone, rebuild, or fork the current node implementation today. Public documentation, a historical whitepaper, a registry entry, or an SDK does not substitute for the implementation source.
This page does not grant a license. The license file attached to an exact future publication will control whether and how that artifact may be copied, modified, or redistributed.
What would make the exit real
Section titled “What would make the exit real”A practical fork path requires all of the following to be published and independently verifiable:
- the implementation source and the history needed to audit it;
- binding license terms that permit the intended use;
- reproducible build and release provenance;
- public network and genesis specifications; and
- a documented way to form an independent network without private Foundation material.
Those gates are not complete. Until they are, “fork as exit” is a design commitment, not a claim that users can fork the running implementation now.