don
/
neon-sprawl
mirror of https://github.com/ViPro-Technologies/neon-sprawl
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
neon-sprawl/docs/decomposition/epics/epic_08_social_guild.md

3.4 KiB
Raw Blame History

Epic 8 - Social, Guild/Corp, and Cooperative Features

Source Anchors

Ownership and success (Level 1)

  • Ownership focus: Social Systems + Online Services
  • Success criteria: Players can easily form long-term social bonds and group structures that improve retention.

Objective

Enable party assembly for cooperative play, player trade and marketplace settlement supporting crafting economy, chat with moderation hooks, and later guild/corp progression tied to faction/social goals.

Module Breakdown

E8.M1 - PartyAndMatchAssembly

  • Responsibility: Party creation/invite/ready-state flow for cooperative activities.
  • Key contracts: PartyState, InviteEvent, RolePreference
  • Dependencies: E1.M3
  • Stage target: Pre-production

E8.M2 - GuildCorpProgressionState

  • Responsibility: Guild/corp membership, rank permissions, and shared progression tracks.
  • Key contracts: GuildState, GuildRolePolicy, GuildProgressionEvent
  • Dependencies: E8.M1, E7.M3
  • Stage target: Production

E8.M3 - PlayerTradeAndMarketplace

  • Responsibility: Listing, trade, purchase, and settlement flows for player economy.
  • Key contracts: MarketListing, TradeOffer, SettlementEvent
  • Dependencies: E3.M3, E3.M5
  • Stage target: Pre-production

E8.M4 - ChatModerationAndReporting

  • Responsibility: Channel chat, report pipeline, moderation action logs and escalation hooks.
  • Key contracts: ChatMessageEvent, PlayerReport, ModerationAction
  • Dependencies: E9.M4
  • Stage target: Pre-production

Implementation Slices (Backlog-Ready)

Slice 1 - Party invites and baseline sync

  • Scope: E8.M1 for invite, accept, leave, and party-scoped instance hooks if needed.
  • Dependencies: E1.M3
  • Acceptance criteria:
    • Party membership consistent server-side; UI reflects state.
  • Telemetry hooks: party_formed, party_disbanded, invite failures.

Slice 2 - Direct trade and listing MVP

  • Scope: E8.M3 minimal trade window plus optional listings with fees tuned by E3.M5.
  • Dependencies: E3.M3, E3.M5
  • Acceptance criteria:
    • Duplication and cancel-edge cases covered; settlement atomic on server.
  • Telemetry hooks: trade_completed, listing_created, purchase_completed, fraud flags.

Slice 3 - Chat and reporting

  • Scope: E8.M4 with rate limits, report reasons, and audit log export path to E9.M4.
  • Dependencies: E9.M4
  • Acceptance criteria:
    • Moderation can trace message id to action history in test.
  • Telemetry hooks: chat_message_sent, player_report filed, moderation_action.

Slice 4 - Guild/corp progression (production)

  • Scope: E8.M2 with ranks, permissions, and shared contracts tied to E7.M3.
  • Dependencies: E8.M1, E7.M3
  • Acceptance criteria:
    • Corp progress cannot be griefed by solo permission bypass.
  • Telemetry hooks: guild_progression_event, permission denials.

Risks and Mitigations

  • Risk: Marketplace enables RMT/exploit duplication.
    • Mitigation: Server settlement; integrity signals; economy policy alerts.
  • Risk: Chat toxicity unsustainable for solo ops.
    • Mitigation: Channel controls, strong report pipeline before scaling users.

Definition of Done

  • Pre-production delivers party, trade/market MVP, chat/reporting aligned to operational plan.
  • Production gates guild features behind social health metrics.