studio/marathon
2
0
Fork 0
Code Issues 121 Pull Requests Actions Packages Projects Releases Wiki Activity

Define v0 Core Tech Validation Demos #124

New Issue
Closed
opened 2025-12-17 04:12:05 +00:00 by siennathesane · 0 comments
siennathesane commented 2025-12-17 04:12:05 +00:00 (Migrated from github.com)
Copy Link

Description

This is a tracking issue for v0 Core Tech Validation demos. V0 is desktop-only validation of fundamental engine capabilities before moving to iPad hardware.

V0 Validation Goals

Desktop-only validation that proves:

  1. CRDT state synchronization works correctly
  2. Full game state persists to SQLite and rehydrates
  3. Session lifecycle management is robust
  4. Networking can be toggled (offline mode works)
  5. Entities can be defined in data files

Related Issues

  • #128: SQLite Schema Design and Migration System
  • #129: CRDT Sync Validation Demo
  • #130: Persistence Validation Demo
  • #131: Session Lifecycle Management Demo
  • #132: Networking Toggle Validation Demo
  • #133: Data-Driven Entity System Demo

Success Criteria

Scenario: V0 validation is complete
  Given all validation demos are implemented
  When each demo runs successfully
  Then v0 technical foundation is proven

Technical Notes

  • Desktop only (macOS)
  • No iPad/iOS in v0
  • Headless/CLI acceptable (no visual requirements)
  • Focus on data validation, not gameplay
  • All demos should be automatable where possible

Additional Context

This tracking issue coordinates the v0 validation work. Close this issue when all related issues are complete and v0 goals are validated.

## Description This is a tracking issue for v0 Core Tech Validation demos. V0 is desktop-only validation of fundamental engine capabilities before moving to iPad hardware. ## V0 Validation Goals Desktop-only validation that proves: 1. CRDT state synchronization works correctly 2. Full game state persists to SQLite and rehydrates 3. Session lifecycle management is robust 4. Networking can be toggled (offline mode works) 5. Entities can be defined in data files ## Related Issues - #128: SQLite Schema Design and Migration System - #129: CRDT Sync Validation Demo - #130: Persistence Validation Demo - #131: Session Lifecycle Management Demo - #132: Networking Toggle Validation Demo - #133: Data-Driven Entity System Demo ## Success Criteria ```gherkin Scenario: V0 validation is complete Given all validation demos are implemented When each demo runs successfully Then v0 technical foundation is proven ``` ## Technical Notes - Desktop only (macOS) - No iPad/iOS in v0 - Headless/CLI acceptable (no visual requirements) - Focus on data validation, not gameplay - All demos should be automatable where possible ## Additional Context This tracking issue coordinates the v0 validation work. Close this issue when all related issues are complete and v0 goals are validated.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/audio
Spatial audio engine, sound playback, audio mixing, music systems, 3D audio positioning
 area/content
Art assets, models, textures, audio files, dialogue trees, narrative content, game data
 area/core
Foundation systems, memory management, math libraries, data structures, core utilities
 area/docs
Documentation, technical specs, RFCs, architecture decisions, API docs, tutorials, guides
 area/infrastructure
Deployment pipelines, hosting, cloud services, monitoring, logging, DevOps, releases
 area/networking
iroh P2P, CRDT sync, gossip protocol, network replication, connection management
 area/platform
iOS/macOS platform code, cross-platform abstractions, input handling, OS integration
 area/rendering
Graphics pipeline, Bevy rendering, shaders, materials, lighting, cameras, meshes, textures
 area/rfc
RFC proposals, design discussions, architecture planning, feature specifications
 area/simulation
Agent systems, NPC behaviors, AI, game mechanics, interactions, simulation logic
 area/tooling
Build systems, CI/CD pipelines, development tools, code generation, testing infrastructure
 area/ui-ux
User interface, menus, HUD elements, input feedback, screen layouts, navigation
 dependencies
Pull requests that update a dependency file
 epic
Large body of work spanning multiple features
 rust
Pull requests that update rust code
No Label area/core area/docs
Milestone
No items
No Milestone v0
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_admin siennathesane
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: studio/marathon#124
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?