Project Readiness
Readiness before public access.
NewGenEngine is not announcing a fixed public test calendar at this stage. Public exposure follows technical readiness, validation, documentation alignment, and the quality of released evidence.
Rollout principle
Public access expands in proportion to verified maturity.
NewGenEngine does not present open availability, public onboarding, or fixed test windows before the visible system surface is ready.
Readiness-guided
No fixed public date
Broader visibility is tied to validated behavior and controlled disclosure, not to a calendar that could misrepresent the real operational state.
Evidence-based
GitHub first
GitHub is the stable public archive for project status, reports, and selected technical evidence. Social channels explain updates and direct attention toward those materials.
Closed by default
No implicit onboarding
Early access and onboarding remain closed until they are explicitly opened. Temporary or placeholder flows do not represent public service availability.
Readiness criteria
Conditions required before broader public participation.
Readiness is evaluated across technology, evidence, operations, and public communication.
- Public documentation explains NewGen L1, E2 Compute Hub, and NewGen AI without mixing their authority boundaries.
- Evidence notes are short, sanitized, and connected to observable runtime behavior.
- NewGen L1 and E2 validation shows finality-confirmed state tracking, bounded job lifecycle behavior, and execution evidence anchored to NewGen L1.
- Operational and security-sensitive details remain private by default.
- Public claims avoid speculative token messaging, premature mainnet claims, and scale claims not supported by evidence.
Maturity of system layers
Different layers can become public at different speeds.
The public explanation stays accurate: chain and compute are closer to exposure, while AI remains real with controlled disclosure.
NewGen L1
Closer to public exposure
The canonical layer is the strongest public anchor because runtime progress, finality-related behavior, adaptive economics, and snapshot/state-sync evidence can be shown cleanly.
E2 Compute Hub
Closer to public exposure
The compute layer can be introduced through finality-confirmed block tracking, node lifecycle, bounded job execution, and job finality evidence anchored to NewGen L1.
NewGen AI
Controlled Disclosure
The proprietary AI layer is described accurately as an internal stack in progress, not as a released public model before the supporting evidence is ready.
Current public route
Status and Evidence are the public entry points.
Until broader public access opens, the public route goes through the available documentation and selected Evidence publications.