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

Implement shared commitments between related entities #88

New Issue
Open
opened 2025-12-17 03:21:57 +00:00 by siennathesane · 0 comments
siennathesane commented 2025-12-17 03:21:57 +00:00 (Migrated from github.com)
Copy Link

Description

Implement shared schedule blocks for couples, families, and work teams.

Acceptance Criteria

Scenario: Shared commitments work
  Given two entities have relationship
  When shared commitments exist
  Then couples share meal times
  And families share evening activities
  And work teams share meeting times

Technical Notes

  • Commitment types: Meal, Leisure, Work, Care
  • Relationship bond strength affects commitment frequency
  • Schedule block synchronization
  • Handle conflicts when entity can't fulfill commitment
  • Commitment affects relationship bond

Size: M (4 points)
Priority: P1
Phase: 3 - Schedule System

## Description Implement shared schedule blocks for couples, families, and work teams. ## Acceptance Criteria ```gherkin Scenario: Shared commitments work Given two entities have relationship When shared commitments exist Then couples share meal times And families share evening activities And work teams share meeting times ``` ## Technical Notes - Commitment types: Meal, Leisure, Work, Care - Relationship bond strength affects commitment frequency - Schedule block synchronization - Handle conflicts when entity can't fulfill commitment - Commitment affects relationship bond **Size:** M (4 points) **Priority:** P1 **Phase:** 3 - Schedule System
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/simulation
Milestone
No items
No Milestone v1
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#88
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?