V1 Short-Term Outcomes
These are the outcomes that define "V1 complete." Each can be demonstrated in a single session.
V1 Proof Loop
Onboarding -> add plant -> record care -> earn energy -> nurture/evolve creature -> play a game
Outcomes
1. Player can login with either passkey or Ethereum wallet
- Passkey: WebAuthn-based sign-in (fast + phishing-resistant)
- Wallet: standard EVM wallet connection
- Done when: User returns after refresh/offline and still has access to their local profile
2. Player can onboard and select element, location, and user info
- Element selection: Water/Earth/Fire/Air
- Location details: home biome label + optional geolocation
- Creature generated based on element and local environment
- Done when: Onboarding is a state machine with explicit steps and can be resumed
3. Player can generate creature based on element and environment
- Inputs: element + biome + plant type
- Output: CreatureCard (name, description, traits, signature move, starter stats)
- V1: curated seed pack or stub generator; LLM behind an interface
- Done when: Creature varies visibly by element and environment
4. Player can nurture creature with earned resources
- Spend energy to increase XP/stats
- Show immediate feedback (progress bar, animation, toast)
- Done when: Creature state changes are persisted locally and reflected in gameplay
5. Players can evolve creature with enough XP
- XP threshold gates new stage with upgraded stats and new signature move
- Done when: Evolution is an explicit action with visible agency
6. Player can add plant from local environment
- Camera capture or upload + manual name tag
- Plant profile: species, nickname, location tag, first photo timestamp, health score
- Done when: Plant is persisted in local inventory with all fields
7. Player can nurture plants with daily photos to earn resources
- Daily photo + quick checklist (watered/pruned/observed/cleaned)
- Streak tracking with soft decay
- Energy reward: +4 base, +6 with streak bonus
- Done when: Care events queue locally and can sync/attest later
8. Player can start game with creature as game piece
- V1 priority: Tic-Tac-Toe (non-AR baseline) + AR mode if available
- Game session includes selected creatures, ruleset, turn state, win/draw detection
- Done when: Pass-and-play works; P2P modes functional
9. Player can join game started by another player
- V1: second player joins on same device or via join code
- Done when: Joining enforces creature selection before first move
10. Player can make game moves on their turn
- Turn enforcement via state machine
- Moves validated by pure rules engine
- Done when: Invalid moves are rejected; turns alternate correctly
11. Player can claim game reward based on result
- Win: +8 energy, Draw: +4, Loss: +2
- Done when: Reward recorded in event log and reflected in deck energy
12. Player can publish and remix UGC with ownership metadata
- UGC local-first, shareable through AT Protocol
- Done when: Each item has content hash, creator identity, and moderation status
13. Community can promote UGC into canonized world content
- Canonization based on attestations and community signals
- Done when: Canon set can be reproduced from attested events and registry state
Assumptions Being Tested
| Assumption | V1 Test |
|---|---|
| People care about plants | Can a new user add a plant + complete 3 care events in their first week? |
| People will like the story | Do users remember their element + creature name/lore and share it? |
| It can gain investment as impact tool | Can we report measurable signals without compromising privacy? |