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

Implement tools as institutional resources #108

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

Description

Institutions own tools that workers can use (bakery owns ovens, blacksmith owns anvils).

Acceptance Criteria

Scenario: Institutional tools work
  Given institution owns tools
  When workers need tools
  Then workers can use institutional tools
  And bakery workers use bakery ovens
  And non-workers cannot use institutional tools
  And tool quality affects institution output quality

Technical Notes

  • Institution owns tool entities
  • Workers have access rights to institutional tools
  • Tool assignment: workers claim tools from institution
  • Tool sharing: multiple workers can't use same tool simultaneously
  • Tool quality affects institution reputation
  • Tool maintenance as institutional task

Size: S (2 points)
Priority: P2
Phase: 9 - Tools & Capabilities

## Description Institutions own tools that workers can use (bakery owns ovens, blacksmith owns anvils). ## Acceptance Criteria ```gherkin Scenario: Institutional tools work Given institution owns tools When workers need tools Then workers can use institutional tools And bakery workers use bakery ovens And non-workers cannot use institutional tools And tool quality affects institution output quality ``` ## Technical Notes - Institution owns tool entities - Workers have access rights to institutional tools - Tool assignment: workers claim tools from institution - Tool sharing: multiple workers can't use same tool simultaneously - Tool quality affects institution reputation - Tool maintenance as institutional task **Size:** S (2 points) **Priority:** P2 **Phase:** 9 - Tools & Capabilities
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 v3
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#108
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?