EasyNet Axon is released in stages. The protocol contracts, SDK surfaces, conformance material, and implementation files present in this repository are public so that integrations can be built, behavior can be reproduced, and design claims can be examined. This repository is not a representation that every component, deployment service, research prototype, or evaluation asset in the wider EasyNet system has been released.
The staged boundary serves four practical purposes.
Tagged source releases create an auditable record of the protocol and its authorship. Holding back unstable implementation mechanisms until they are ready for review reduces the risk that early research is absorbed elsewhere without clear attribution while still establishing public priority for the interfaces being evaluated.
Every public surface creates a long-lived compatibility and support obligation. The project therefore opens bounded, testable interfaces rather than turning each research iteration into many indefinite environment, deployment, and legacy-platform commitments. This keeps maintenance proportional to the available research capacity.
Unpublished mechanisms, evaluation harnesses, and experiment details may remain private while peer review is in progress where a venue's anonymity or prior- disclosure policy requires it. Release decisions follow the policy applicable to the work rather than assuming one rule for every venue.
Additional implementation layers are released when real production agentic workflows can exercise their security, recovery, and operational contracts. Prematurely publishing an unsupported control plane would create adoption and maintenance signals that do not yet test the research question.
Apache-2.0 applies to the files and artifacts that are actually distributed under that license. This scope statement adds no restriction to those rights. Components or materials that are not present in a public distribution are not implicitly licensed by the existence of this repository.