wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[READY][Architecture] #311-B Extract FupOgFakta phase/state engine from lobby into fupogfakta/ #313

New Issue
Open
opened 2026-03-16 19:51:08 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-16 19:51:08 +01:00
Owner
Copy Link

Parent issue: #311

Problem statement

The current implementation places concrete lie -> guess -> reveal -> scoreboard behaviour in lobby/. That means the platform layer currently behaves like the FupOgFakta engine.

Expected value / why now

This restores the intended cartridge boundary so FupOgFakta owns its own rules, transitions, and game-specific state handling.

Acceptance criteria

  • Move FupOgFakta-specific phase/state logic out of lobby/ into fupogfakta/ (or an explicit game-cartridge layer under that app).
  • Keep lobby/ limited to generic session/container concerns and routing/orchestration into the game layer.
  • Preserve the existing playable loop while changing ownership.
  • Update tests to prove canonical round flow still works after the move.
  • PR references #311 and explicitly states what ownership changed.

Scope boundary

  • Not a full plugin ecosystem.
  • Not multi-game UI features.
  • Not an excuse to redesign game rules at the same time.
Parent issue: #311 ## Problem statement The current implementation places concrete `lie -> guess -> reveal -> scoreboard` behaviour in `lobby/`. That means the platform layer currently behaves like the FupOgFakta engine. ## Expected value / why now This restores the intended cartridge boundary so FupOgFakta owns its own rules, transitions, and game-specific state handling. ## Acceptance criteria - Move FupOgFakta-specific phase/state logic out of `lobby/` into `fupogfakta/` (or an explicit game-cartridge layer under that app). - Keep `lobby/` limited to generic session/container concerns and routing/orchestration into the game layer. - Preserve the existing playable loop while changing ownership. - Update tests to prove canonical round flow still works after the move. - PR references #311 and explicitly states what ownership changed. ## Scope boundary - Not a full plugin ecosystem. - Not multi-game UI features. - Not an excuse to redesign game rules at the same time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#313
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?