Stage 1 — Validation

What We Validate

In Stage 1, we answer:

• Can a world be created, persisted, and loaded again reliably?
• Do block- and contract-based interactions work consistently within real gameplay flows?
• Are we operationally ready to support an initial community test?

To validate this, Stage 1 is split into two phases.

Phase Structure

Phase 1.1 — Internal Validation (Pre-Alpha)

This phase is run by the internal team. We stress-test core system stability (architecture, persistence, on-chain integration) and intentionally surface structural issues early.

• Failure is allowed; fast iteration is expected
• The goal is to expose structural problems as early as possible

👉 Go to Phase 1.1 — Internal Validation

Phase 1.2 — Community Validation (Alpha)

This is the first public Alpha for the community. We validate playability and operability under real user conditions.

• External users can play
• Validate traffic/load, UX, and operational baselines
• Run an issue collection and improvement loop

👉 Go to Phase 1.2 — Community Validation

Timeline (Target)

• Internal Validation: In progress (as of 2026.02)
• Community Alpha: Target 2026.Q1

Dates are targets and may change depending on stability and operational verification.

Exit Condition

Stage 1 ends when:

• Core internal validation is complete
• Sustained play is possible in the community environment
• Enough data and criteria have been gathered to expand into Stage 2 (Expansion)

Stage 1 is not “completion.” It is the foundation required to start the next stage safely.

What Comes Next

After Stage 1, Akkadia moves to Stage 2 — Expansion, where on-chain functionality and user creation are expanded on the official Testnet.