Phase 1.1 — Internal Validation
Phase 1.1 is Akkadia’s most fundamental and most important validation phase.
The goal is not external exposure, but to validate internally that Akkadia’s core structures actually work and can be maintained.
In this phase:
- Failure is acceptable
- Structural changes and refactors are expected
- Reliability matters more than feature completeness
Timeline
- Status: In Progress
- As of: February 2026
Phase 1.1 does not lock in a fixed end date. Instead, we move to Phase 1.2 once we satisfy the Exit Criteria below.
Goals
The core goals of Phase 1.1 are:
- World and data structures remain consistent over time
- Block- and contract-based interactions work reliably and repeatedly
- Critical structural risks are removed before opening community testing
In short:
“Break everything that can break before external users enter.”
Scope
In Scope
- World creation and basic entry flow
- World boundary and movement restriction logic
- Block placement / removal / state changes
- Save / load pipeline
- Chunk loading and unloading
- Basic contract block authoring / placement / execution
- Client–server–on-chain integration
- Minimal UI/UX required to play
Out of Scope
These are not required outcomes for Phase 1.1:
- Economy systems (market, trading, reward structures)
- Full ACR token rollout
- Quest and event systems
- Content variety expansion (biomes, item types)
- Long-term balancing for live operation
Validation Checklist
Core Gameplay & Flow
- World creation → entry → movement → interaction loop works end-to-end
- World state restores correctly on reconnect
- No critical soft-lock states during play
World Persistence & Data Integrity
- Block placement/removal reflects immediately
- Saved world state remains consistent after reconnect
- No data loss or duplication during chunk load/unload
- Reproducibility of the same position/state is ensured
- Access control to inactive areas is applied consistently
On-chain Interaction
- Basic contract block authoring flow works
- Contract block placement/execution is repeatable without interruption
- World state does not break on transaction failure/delay
- On-chain call failures do not crash the client
Client Stability
- No crashes during connect/load/reconnect
- Stable input & camera control (e.g., pointer lock)
- No memory leaks during long sessions
- Performance degradation does not make the game unplayable
Infrastructure & Runtime
- Server process remains stable over long uptime
- Safe failure behavior on client/server version mismatches
- Basic logging and error tracing are available
- Deployment/restart procedures in test environment are validated
Known Risks (Expected)
In Phase 1.1, these risks may be intentionally surfaced:
- World state inconsistency
- Contract execution delays
- Performance degradation
- Need for data migrations
The goal of this phase is to find these problems early and make them reproducible.
Exit Criteria
We exit Phase 1.1 when:
- World save/load and block mutations are reliable enough
- Core contract block loop is stable and repeatable
- Critical crash/data-integrity issues are removed
- Stability is sufficient to open community testing
- Phase 1.2 validation items are clearly defined
Notes
- Phase 1.1 is not meant to be shown externally.
- Changes and refactors in this phase are intended.
- Issues and data gathered here become the baseline for Phase 1.2 (Community Validation).
Phase 1.1 is the foundation of Akkadia. The more solid this phase is, the faster and more safely every later stage will move.