XENOr is a deterministic, simulation-first research stack. If you are landing cold on GitHub, start with xenor-site for the public overview, then move into xenor-core, xenor-sim, and xenor-engine depending on which layer you need.

The current public stack is active, but not uniformly production-ready.

• Active public surfaces: xenor-site, xenor-core, xenor-sim, xenor-engine
• Experimental native lab: xenor-native
• Archived historical repo: xenor-sale
• Experimental and research-stage work is labeled in each repository README

1. xenor-site / https://xenor.xyz The canonical public surface and the best first stop for newcomers.
2. xenor-core The core logic layer.
3. xenor-sim The validation layer built around xenor-core.
4. xenor-engine The canonical deterministic substrate.
5. xenor-native The experimental native lab for low-level incubation work that may later graduate into xenor-engine.
6. xenor-sale Archived historical work kept only as launch research context.

This profile repository is the GitHub entry point for the XENOr stack. Its job is to point first-time visitors to the right repository quickly and to make the active vs experimental vs historical boundaries obvious.

• xenor-site is the canonical public surface
• xenor-core is the core logic layer
• xenor-sim is the validation layer on top of xenor-core
• xenor-engine is the canonical deterministic substrate
• xenor-native is the experimental native lab
• xenor-sale is archived historical work and not part of the active path

• Open https://https://xenor-web.vercel.app/ first if you want the public overview.
• Open xenor-core next if you want the main protocol logic.
• Open xenor-sim if you want to see how validation runs are modeled around xenor-core.
• Open xenor-engine if you want the canonical deterministic substrate and replay/snapshot work.
• Open xenor-native only if you want the experimental native lab and low-level incubation work.

• This profile repo is a navigation surface, not a product or protocol repo.
• It should not duplicate architecture detail that already lives in xenor-site, xenor-core, xenor-sim, or xenor-engine.
• It should make the stack easier to enter, not act as a parallel documentation site.

• xenor-site — canonical public surface and first stop
• xenor-core — core logic layer
• xenor-sim — validation layer
• xenor-engine — canonical deterministic substrate
• xenor-native — experimental native lab
• xenor-sale — archived historical work

No standalone contributing guide is currently published in this repository. Use issues or pull requests directly for navigation or wording fixes.

No standalone license file is currently published in this repository.