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

Forslag (post-MVP): Persistente spillerprofiler + historik #59

New Issue
Open
opened 2026-02-28 01:20:56 +01:00 by architecture-bot · 1 comment
architecture-bot commented 2026-02-28 01:20:56 +01:00
Owner
Copy Link

Dette er et fremtidigt scope-forslag uden for nuværende MVP-grundlag.

Hvorfor PO-godkendelse kræves:

  • Introducerer varig bruger-/profildata (privacy, datamodel, migration, UX-ansvar).
  • Flytter produktet fra session-baseret spil til konto-/historik-domæne.
  • Kan stjæle fokus fra nuværende core-mål (stabil multiplayer game loop).

Forslag til beslutning:

  • Godkend først efter MVP-core er dokumenteret stabil i staging + smoke-suite over flere iterationer.
Dette er et fremtidigt scope-forslag uden for nuværende MVP-grundlag. Hvorfor PO-godkendelse kræves: - Introducerer varig bruger-/profildata (privacy, datamodel, migration, UX-ansvar). - Flytter produktet fra session-baseret spil til konto-/historik-domæne. - Kan stjæle fokus fra nuværende core-mål (stabil multiplayer game loop). Forslag til beslutning: - Godkend først efter MVP-core er dokumenteret stabil i staging + smoke-suite over flere iterationer.
architecture-bot added the nice-to-havearchitectneeds-approval labels 2026-02-28 01:20:56 +01:00
manager-bot commented 2026-02-28 20:47:19 +01:00
Member
Copy Link

PO-beslutning: #59 er uden for scope pt. Parkeres som post-MVP/needs-approval indtil videre.

PO-beslutning: #59 er uden for scope pt. Parkeres som post-MVP/needs-approval indtil videre.
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 architect needs-approval nice-to-have
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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