Phase 1.2 — Community Validation
Phase 1.2 is Akkadia’s first public validation phase for the community.
The goal is not “showing.” It is to confirm that Akkadia’s core structures still hold up in real external user environments.
If Phase 1.1 (Internal Validation) establishes technical stability, Phase 1.2 validates that stability inside real user flows.
Timeline
- Alpha (Community)
- Target: 2026.Q1
Phase 1.2 runs with a limited-size community and prioritizes usability and problem discovery over feature completeness.
Goals
The key questions in Phase 1.2 are:
- Can external users understand Akkadia and play it?
- Do the basic world/block/contract loops work without heavy explanation?
- Can we operationally handle the issues that surface in a community environment?
In short:
“Can Akkadia work for people outside the internal team?”
This phase validates whether Akkadia works for people outside the internal team.
Scope
In Scope
- Community Alpha release
- Validate account creation and world entry flow
- Confirm baseline world playability
- Block placement and interaction tests
- Limited contract block usage
- Collect bugs and UX issues from real user behavior
- Operate a community feedback loop
Out of Scope
These are not goals for Phase 1.2:
- User-created custom contract blocks
- Applying the ACR token system
- Switching to the Testnet environment
- Economy systems and reward-structure testing
Phase 1.2 is a validation phase, not an expansion phase.
Community Validation Checklist
Core Gameplay
- Users can enter a world successfully
- Basic controls and interactions are understandable
- Movement, camera/view, and interactions behave stably
- No critical progression-blocking bugs during play
Block & Contract Flow
- Basic block placement and removal work
- Block state is saved and restored
- Limited contract blocks are usable
- World state remains safe when contract execution fails
UX & Onboarding
- Users can start playing with minimal guidance
- Confusing points are identified
- Areas requiring UX improvement become clear
Operations
- Server remains stable as community traffic increases
- We can respond to incidents and communicate clearly
- We can collect, triage, and incorporate community feedback
What We Learn in Phase 1.2
Phase 1.2 is not a phase for declaring success. The output is the quantity and types of problems we discover.
- Where users get stuck
- Which features cause misunderstanding
- Which systems are more complex than expected
- Which points are operationally hard to handle
These results become the baseline for moving to Stage 2 — Expansion.
Exit Criteria — Ready for Stage 2
When the following are true, Akkadia moves to Stage 2 (Testnet Beta):
- Baseline play is possible in the community environment
- Critical structural issues are identified and organized
- Operations and community-response flows are established
- Key expansion items for Testnet validation are clearly defined
Notes
- Phase 1.2 is not a “finished Alpha.”
- Friction and limitations may be intentional.
- The goal is to surface the problems that must be exposed before expansion.
Phase 1.2 is Akkadia’s first step beyond internal experimentation—starting validation together with the community.