Eve library

phase-80.md

Tracker

Revision 1

On this page

Historical task source. The Eve task board holds current task state.

Phase 80: Maya Social Fabric SOTA — MMO Community Formation, Belonging, and Health#

Purpose: Close the gap between multiplayer infrastructure and actual social stickiness by building the systems that help players meet people, find their place, form recurring groups, join healthy guilds, recover from bad social experiences, and remain meaningfully connected over time. This phase focuses on community formation, community health, and AI/NPC-assisted social facilitation, especially for shy, awkward, isolated, or returning players.

Reference Proposal: docs/proposals/MAYA_SOCIAL_FABRIC_COMMUNITY_HEALTH_PROPOSAL.md

Scope: Maya multiplayer TypeScript libraries (social graph, discovery, guild/community, trust & safety, analytics, AI social facilitation), Maya Rust runtime crates for in-world social hosts and world choreography, Lilith companion/community surfaces, Sophia community-health analytics, and Hathor world/event design integration.

Technology:

  • TypeScript libraries (in libs/maya/): Social graph, discovery, LFG community, guild recruitment, mentorship, trust & safety, community health, AI social facilitation, community events
  • Rust crates (in libs/maya/engine-core/crates/): World social runtime, NPC social hosts, bulletin boards, social hubs, event choreography
  • Integration targets: Phase 77 parties/guilds/chat, Lilith companion surfaces, Discord/community bridges, push notifications, analytics warehouse, moderation operations tooling

80.1 Social Identity & Intent Graph (TypeScript)#

Foundational social model above the raw friend list. Tracks who players know, what they want to do, how they like to socialize, and what kind of group experience is most comfortable and useful for them.

80.1.1 Social Graph Core#

  • 80.1.1.1 Create libs/maya/social-graph/ TypeScript library with project configuration
  • 80.1.1.2 Implement PlayerSocialProfile model — relationship edges, social preferences, group comfort, activity interests, languages, platform, timezone, and availability windows
  • 80.1.1.3 Create PlayerIntentState model — "what I want right now" state for questing, raiding, crafting, chatting, role-play, teaching, learning, and exploring
  • 80.1.1.4 Implement real-time presence aggregation across friends, parties, guilds, and platform-connected accounts
  • 80.1.1.5 Create relationship-strength model — friend, recurring squadmate, mentor/mentee, guildmate, alliance partner, blocked, avoided
  • 80.1.1.6 Implement reliability signals — show-up rate, completion rate, disconnect rate, recent endorsement rate, and cooldown history
  • 80.1.1.7 Create comfort and communication controls — no-mic, small group preference, teaching-friendly preference, AI-assisted onboarding, first-timer-safe preference
  • 80.1.1.8 Implement privacy matrix — field-level visibility rules for presence, schedule, profile notes, reputation signals, and guild interest
  • 80.1.1.9 Create feature-view projections for discovery, matchmaking, AI facilitation, and community analytics
  • 80.1.1.10 Implement social graph sync and caching strategy with conflict-safe updates and audit logging

80.2 Discovery & Serendipity Layer (TypeScript)#

Helps players find compatible people, communities, and events even when they do not know exactly what to search for.

80.2.1 Discovery Engine#

  • 80.2.1.1 Create libs/maya/social-discovery/ TypeScript library with recommendation and explainability modules
  • 80.2.1.2 Implement home discovery feed — compatible players, guilds, events, quest groups, and mentor opportunities
  • 80.2.1.3 Create "people you should meet" recommendation engine based on shared intent, schedule overlap, reliability, mutual ties, and complementary roles
  • 80.2.1.4 Implement guild and alliance recommendation engine with culture, activity cadence, role demand, and newcomer friendliness scoring
  • 80.2.1.5 Create event discovery layer — recurring social rituals, public gatherings, guild open houses, teaching runs, and seasonal community events
  • 80.2.1.6 Implement returner resurfacing — re-expose old social ties, former guilds, repeated squadmates, and relevant current communities
  • 80.2.1.7 Create shy-player and low-pressure lanes — small-group, no- mic, first-timer, mentor-led, and "gentle pace" discovery filters
  • 80.2.1.8 Implement recommendation explainability — show why a player, guild, or event is being recommended in plain language
  • 80.2.1.9 Create diversity guardrails — prevent recommendation loops from hardening into closed cliques or repetitive narrow social graphs
  • 80.2.1.10 Implement notification policy engine for discovery nudges with anti-spam limits and social relevance thresholds

80.3 Group Formation, LFG, and Quest Matching (TypeScript)#

Expands Phase 77's baseline party/lobby systems into a community-first group formation layer optimized for recurring human connection, not just queue fill.

80.3.1 Community Group Finder#

  • 80.3.1.1 Create libs/maya/lfg-community/ TypeScript library with listing, scheduling, and post-session modules
  • 80.3.1.2 Implement structured listing schema — activity, objective, role needs, tone, language, platform, voice preference, expected duration, and teaching/learning posture
  • 80.3.1.3 Create community tags — first-timers welcome, speed clear, chill run, lore run, role-play, quiet run, teaching run, mentor-led
  • 80.3.1.4 Implement now vs scheduled listings with RSVP, waitlist, and reminder support
  • 80.3.1.5 Create application vs auto-join workflow with per-listing policy and quick applicant review
  • 80.3.1.6 Implement quest-journal recruitment — spawn group listings directly from quests, objectives, and open-world encounters
  • 80.3.1.7 Create join-in-progress and backfill routing that respects tone, skill expectation, and player comfort constraints
  • 80.3.1.8 Implement ready-up and expectation confirmation flow before launch, including role confirmation and "what this run is" summary
  • 80.3.1.9 Create post-run regroup prompt — queue again, add friend, schedule next run, invite to guild, or bookmark this squad
  • 80.3.1.10 Implement recurring squad templates and saved play windows for players who repeatedly succeed together
  • 80.3.1.11 Create duo/trio completion suggestions — recommend compatible fill-ins rather than only opening to unrestricted public pool
  • 80.3.1.12 Implement AI-assisted listing generation — help awkward or inexperienced players compose clear, inviting listings

80.4 Guild Recruitment & Community Finder (TypeScript)#

Structured tooling for finding the right guild/community fit and letting guilds recruit in a healthy, searchable way.

80.4.1 Recruitment Platform#

  • 80.4.1.1 Create libs/maya/guild-recruitment/ TypeScript library with public profile, application, and recommendation modules
  • 80.4.1.2 Implement GuildRecruitmentProfile — focus, culture, schedule, size, language, role needs, voice expectations, and newcomer friendliness
  • 80.4.1.3 Create guild/community search with filters for activity type, timezone, language, size, intensity, recruiting status, and cross-platform posture
  • 80.4.1.4 Implement applicant pipeline — quick apply, notes, application review, status tracking, and recruiter comments
  • 80.4.1.5 Create provisional membership flow — trial role, limited permissions, onboarding checklist, and probation end review
  • 80.4.1.6 Implement recruiter calendar and office hours for scheduled introductions, interviews, and open houses
  • 80.4.1.7 Create member referral workflow — existing members can vouch for players and route them into the right subgroup
  • 80.4.1.8 Implement public guild/community pages on companion web and in-game surfaces with shareable deep links
  • 80.4.1.9 Create in-world recruitment boards, kiosks, and guild fair booths connected to live recruitment profiles
  • 80.4.1.10 Implement guild recommendation model for solo players, returners, and successful repeated squads

80.5 Guild Operations & Shared Progress (TypeScript)#

Turns guilds from static rosters into active communities with shared work, memory, and visible contribution.

80.5.1 Guild Community Operations#

  • 80.5.1.1 Create libs/maya/guild-operations/ TypeScript library with project boards, calendar, and membership tooling
  • 80.5.1.2 Implement guild project board — tasks, assignees, deadlines, payout/reward rules, and progress tracking
  • 80.5.1.3 Create contribution tracking for combat, logistics, crafting, mentoring, recruiting, event hosting, and community care work
  • 80.5.1.4 Implement newcomer welcome queue — who needs onboarding, first run, first role assignment, and mentor pairing
  • 80.5.1.5 Create guild calendar with RSVP, recurring events, waitlists, reminder workflows, and event ownership delegation
  • 80.5.1.6 Implement guild knowledge base — playbooks, raid guides, etiquette notes, group expectations, and cultural norms
  • 80.5.1.7 Create storage, treasury, and resource-log surfaces with transparent contribution and spend history
  • 80.5.1.8 Implement guild goals and seasonal objectives with member- visible progress and celebration hooks
  • 80.5.1.9 Create guild hall scheduling and open-house management for tours, training sessions, and public recruitment windows
  • 80.5.1.10 Implement officer coverage and succession planning — detect leadership gaps, stalled queues, and absent owners

80.6 Alliances, Coalitions, and Cross-Community Cooperation (TypeScript)#

Supports federated community structures so smaller communities can thrive without being forced into megaguild consolidation.

80.6.1 Federation Layer#

  • 80.6.1.1 Create libs/maya/community-federation/ TypeScript library for alliances, guest access, and coalition tooling
  • 80.6.1.2 Implement alliance model — member guilds, shared channels, shared events, and scoped leadership permissions
  • 80.6.1.3 Create guest access system — temporary alliance passes, public subgroup invites, and shared-event participation rights
  • 80.6.1.4 Implement alliance project boards and coalition objectives spanning multiple communities
  • 80.6.1.5 Create temporary coalition system for wars, seasonal pushes, festivals, and large-scale cooperative events
  • 80.6.1.6 Implement diplomatic state model — allied, neutral, limited access, mentor partner, recruitment partner
  • 80.6.1.7 Create alliance discovery and inter-guild referral flows for communities looking for partners rather than members
  • 80.6.1.8 Implement governance and permission templates for alliance- scale community management

80.7 New Player Onboarding, Returner Rescue, and Mentorship (TypeScript)#

Dedicated systems for helping people ease into the ecosystem socially, not just mechanically.

80.7.1 Social Onboarding & Mentorship#

  • 80.7.1.1 Create libs/maya/mentorship/ TypeScript library with onboarding journeys, mentor registry, and returner rescue modules
  • 80.7.1.2 Implement newcomer and returner detection heuristics — account age, content familiarity, inactivity gaps, and social reset status
  • 80.7.1.3 Create social onboarding journeys — first group, first friend, first guild, first event, first repeat squad
  • 80.7.1.4 Implement novice/help channels with question routing, answer triage, and contextual content linking
  • 80.7.1.5 Create mentor registry — specialties, availability, languages, preferred content types, and teaching posture
  • 80.7.1.6 Implement mentor certification and training completion tracking with safety and quality requirements
  • 80.7.1.7 Create escorted first-run flows where mentors can adopt new players into learning groups with clear expectations
  • 80.7.1.8 Implement first-five-social-milestones tracker with gentle prompts and progress recovery after churn
  • 80.7.1.9 Create returner recap experience — what changed, who is still active, which communities fit now, and where to re-enter
  • 80.7.1.10 Implement protected first-timer cohorts and teaching lanes so new players are not pushed into hostile or speed-run environments
  • 80.7.1.11 Create mentor quality model — response helpfulness, completion rate, endorsement rate, complaint rate, and inactivity decay
  • 80.7.1.12 Implement mentor recognition and support — badges, burnout warnings, schedule controls, and community-wide appreciation surfaces

80.8 Shared Spaces, World Rituals, and Social World Design (Rust + TypeScript)#

Designs social contact into the world itself so communities form through places and repeated rhythms, not only through menus.

80.8.1 World Social Layer#

  • 80.8.1.1 Create libs/maya/world-social-runtime/ integration layer spanning TypeScript social services and Rust world systems
  • 80.8.1.2 Implement reusable social hub templates — starter taverns, plazas, camps, guild fairs, training grounds, and public gathering spaces
  • 80.8.1.3 Create interactive quest, bounty, and help boards that show live tasks, public requests, and group-forming opportunities
  • 80.8.1.4 Implement public co-op rituals — campfire buffs, festival performances, shared crafting stations, escort caravans, fishing circles
  • 80.8.1.5 Create guild fairgrounds and recruitment festivals where communities can host booths, tours, and teaching sessions
  • 80.8.1.6 Implement public social memory surfaces — event photos, achievement monuments, guild banners, visitor logs, and commemorative boards
  • 80.8.1.7 Create recurring community event scheduler tied to world calendars, seasonal rituals, and social gathering cadence
  • 80.8.1.8 Implement NPC anchor points and world markers for social onboarding, help routing, and public event assembly
  • 80.8.1.9 Create quiet-space and low-stimulation social zones for hesitant players who want gentler contact
  • 80.8.1.10 Implement world design heuristics and validation checks for social density, bottlenecks, and meeting opportunities

80.9 Reputation, Trust, Reliability, and Compatibility (TypeScript)#

Private and context-aware trust systems that improve match quality and community health without becoming a public popularity caste system.

80.9.1 Trust & Compatibility#

  • 80.9.1.1 Create libs/maya/community-reputation/ TypeScript library with reliability, endorsement, and compatibility modules
  • 80.9.1.2 Implement private reliability model — show-up behavior, completion behavior, reconnect behavior, and repeated cooperation success
  • 80.9.1.3 Create endorsement system — helpful, patient, clear leader, great teacher, reliable teammate, welcoming host
  • 80.9.1.4 Implement teaching-friendly and first-timer-safe trust markers surfaced to appropriate players and contexts
  • 80.9.1.5 Create avoid/block preference system across parties, guilds, discovery, AI suggestions, and notifications
  • 80.9.1.6 Implement compatibility scoring — schedule, role complement, communication style, tone, reliability, and comfort match
  • 80.9.1.7 Create probation and recovery workflows after disruptive social behavior with clear appeal and improvement paths
  • 80.9.1.8 Implement anti-brigading and anti-harassment protections for endorsements, reporting, and reputation effects
  • 80.9.1.9 Create fairness audits to detect exclusionary or biased reputation outcomes across cohorts and regions
  • 80.9.1.10 Implement selective trust-signal surfacing in discovery and group recommendations without exposing raw sensitive scores

80.10 Communication, Moderation, and Community Safety (TypeScript)#

Adds proactive safety, community onboarding, and moderator operations around the baseline communication systems from Phase 77.

80.10.1 Trust & Safety Operations#

  • 80.10.1.1 Create libs/maya/trust-safety/ TypeScript library with onboarding, moderation, case, and policy modules
  • 80.10.1.2 Implement community onboarding and rules acceptance before participation in public chat, guild onboarding, and official communities
  • 80.10.1.3 Create channel and role self-selection flows so newcomers only see relevant conversations, interests, and event categories
  • 80.10.1.4 Implement automated text moderation for profanity, spam, scams, raid behavior, and suspicious recruitment abuse
  • 80.10.1.5 Create voice safety pipeline with optional speech-to-text evidence generation, escalation triggers, and privacy-aware retention
  • 80.10.1.6 Implement moderator case management — report intake, evidence bundles, action history, escalation state, and reviewer notes
  • 80.10.1.7 Create guild, alliance, and event-host moderation roles with scoped permissions and audit trails
  • 80.10.1.8 Implement situational safety nudges — cooldown prompts, reminder banners, expectation clarifications, and de-escalation notices
  • 80.10.1.9 Create cross-surface report syncing across in-game chat, guild pages, companion surfaces, and community integrations
  • 80.10.1.10 Implement evidence retention and privacy rules for reports, voice incidents, and community safety investigations
  • 80.10.1.11 Create regional language policy support and localized moderation configuration
  • 80.10.1.12 Implement community safety dashboards and alerting for raid attacks, toxicity spikes, spam outbreaks, and moderator backlog

80.11 Leadership, Governance, and Community Operations (TypeScript)#

Operational tooling for community leaders, ambassadors, moderators, and mentor networks.

80.11.1 Community Leadership Layer#

  • 80.11.1.1 Create libs/maya/community-governance/ TypeScript library for leadership workflows, councils, and governance notes
  • 80.11.1.2 Implement officer and lead role templates with scoped permissions for recruitment, events, moderation, mentoring, and logistics
  • 80.11.1.3 Create delegated event ownership and staffing flows so community work is distributable rather than founder-bottlenecked
  • 80.11.1.4 Implement governance notes, polls, and lightweight decision logging for guilds, alliances, and official communities
  • 80.11.1.5 Create ambassador program tooling for trusted guides, community greeters, and ecosystem-facing helpers
  • 80.11.1.6 Implement volunteer moderator and mentor staffing schedule management with coverage tracking and gap alerts
  • 80.11.1.7 Create leadership burnout and overload dashboards — overdue queues, unanswered asks, pending reports, and idle responsibilities
  • 80.11.1.8 Implement succession planner — role handoff, backup owners, emergency coverage, and archive transfer
  • 80.11.1.9 Create culture templates — casual, role-play, hardcore, teaching-focused, family-safe, newcomer-friendly
  • 80.11.1.10 Implement official community operations runbooks for onboarding, incident response, event hosting, and cross-team escalation

80.12 Recognition, Status, and Prosocial Incentives (TypeScript)#

Recognition systems for the community behaviors that actually make an MMO feel alive and welcoming.

80.12.1 Prosocial Recognition#

  • 80.12.1.1 Create libs/maya/community-recognition/ TypeScript library with badges, ceremonies, and memory systems
  • 80.12.1.2 Implement mentor, helper, recruiter, and reliable leader badges with anti-farming rules and quality thresholds
  • 80.12.1.3 Create guild and alliance milestone celebrations — anniversaries, project completions, public contributions, social growth
  • 80.12.1.4 Implement thank-you notes, commendations, and lightweight appreciation surfaces for players and leaders
  • 80.12.1.5 Create newcomer graduation moments — first raid, first guild role, first event host, first successful mentorship cycle
  • 80.12.1.6 Implement social memory book entries, monuments, and timeline highlights for groups and communities
  • 80.12.1.7 Create invisible labor recognition — logistics, moderation, welcoming, answer triage, and conflict resolution work
  • 80.12.1.8 Implement incentive guardrails so recognition strengthens culture without turning kindness into a leaderboard grind

80.13 External Community Surfaces & Companion Experiences (TypeScript)#

Extends community participation outside the client so social planning can happen before players log in and continue after sessions end.

80.13.1 Companion Community Platform#

  • 80.13.1.1 Create libs/maya/community-companion/ TypeScript library for companion web/mobile APIs and shared UI data models
  • 80.13.1.2 Implement companion community finder — guild browsing, event discovery, mentor search, and repeat-squad resurfacing
  • 80.13.1.3 Create synchronized event calendar across in-game, web, mobile, and notification surfaces
  • 80.13.1.4 Implement public guild/community profile pages with share cards, join/application flows, and event previews
  • 80.13.1.5 Create shareable deep links for listings, events, guild pages, and mentorship sessions
  • 80.13.1.6 Implement community notification preference center — reminders, discovery nudges, returner briefs, mentor asks, and event RSVP
  • 80.13.1.7 Create Discord and external community bridges for mirrored announcements, event sync, and identity-safe routing
  • 80.13.1.8 Implement external RSVP, waitlist, and attendance confirmation flows for scheduled social events
  • 80.13.1.9 Create community APIs and webhooks for partner surfaces, moderation ops, and ecosystem tooling
  • 80.13.1.10 Implement privacy and connected-account controls for sharing presence, profiles, and recruitment status outside the client

80.14 Community Analytics, Health Modeling, and Experimentation (TypeScript)#

Measures whether the ecosystem is producing durable, positive social relationships rather than just traffic.

80.14.1 Community Health Intelligence#

  • 80.14.1.1 Create libs/maya/community-health/ TypeScript library with metrics definitions, scoring, and intervention interfaces
  • 80.14.1.2 Implement community health warehouse schemas for social events, group formation, guild lifecycle, moderation, and mentoring
  • 80.14.1.3 Create first-friend, first-repeat-squad, and first-guild metrics with cohort breakdowns
  • 80.14.1.4 Implement guild funnel analytics — application, trial member, retained member, active contributor, leader path
  • 80.14.1.5 Create LFG funnel analytics — listing views, joins, completions, regroup conversions, and churn after failed runs
  • 80.14.1.6 Implement safety and trust analytics — report rates, resolution time, appeal rate, recurring harm patterns, and protected cohort outcomes
  • 80.14.1.7 Create isolation-risk and returner-risk models to detect players drifting out of the social graph
  • 80.14.1.8 Implement experimentation framework for discovery surfaces, onboarding journeys, group prompts, and recognition mechanics
  • 80.14.1.9 Create community health dashboards for product, live ops, moderation, guild leaders, and mentor coordinators
  • 80.14.1.10 Implement intervention playbooks — when to recommend mentors, resurface old ties, offer AI wingman mode, or route to lower- pressure communities

80.15 AI Social Facilitation Agents & Companions (TypeScript + Rust)#

Transparent, opt-in AI systems that help players ease into the ecosystem, understand the social landscape, and make the first move toward human connection.

80.15.1 AI Social Facilitation Stack#

  • 80.15.1.1 Create libs/maya/social-facilitation/ TypeScript library with agent orchestration, policy, and memory interfaces
  • 80.15.1.2 Implement SocialCompanionProfile — player comfort level, preferred intervention style, coaching intensity, and opt-in boundaries
  • 80.15.1.3 Create explicit AI opt-in settings for social coaching, group suggestions, introductions, rehearsal mode, and live facilitation
  • 80.15.1.4 Implement AI group suggestion engine — recommend compatible listings, mentors, guilds, and low-pressure social spaces
  • 80.15.1.5 Create social wingman introduction generator — produce concise, disclosed introductions that help shy players join a group
  • 80.15.1.6 Implement rehearsal mode — practice greetings, guild applications, raid joins, and voice etiquette in a safe AI conversation
  • 80.15.1.7 Create party concierge summaries — explain who is in the group, what the tone is, what the objective is, and what the player should expect
  • 80.15.1.8 Implement quiet-player participation nudges during live group play — suggest moments to ask, respond, emote, or contribute
  • 80.15.1.9 Create mentor assistant that routes novice questions, summarizes context, and helps mentors manage repeated asks
  • 80.15.1.10 Implement returner rescue assistant — summarize changes, re-surface old ties, and recommend the best current re-entry path
  • 80.15.1.11 Create temporary AI companion slot-fill mode that keeps a player moving while still nudging toward eventual human group formation
  • 80.15.1.12 Implement post-session follow-up assistant — suggest friend requests, replay scheduling, thank-you notes, or guild invitations
  • 80.15.1.13 Create disclosure, consent, and safety policy engine — never impersonate humans, never force interaction, always respect privacy
  • 80.15.1.14 Implement memory and boundary controls — reviewable social memory, retention windows, and per-context disable switches
  • 80.15.1.15 Create evaluation suite for comfort, participation, friendship formation, retention, false-positive intervention rate, and AI trustworthiness

80.16 NPC Social Hosts & World Choreography (Rust + TypeScript)#

In-world NPCs, bulletin boards, and public rituals that route players toward compatible humans and create repeated contact opportunities.

80.16.1 World Social Hosts#

  • 80.16.1.1 Create maya-community-runtime Rust crate for NPC social host behaviors, bulletin boards, and event choreography integration
  • 80.16.1.2 Implement tavern keepers, faction officers, and bulletin board stewards that surface live community opportunities and joinable tasks
  • 80.16.1.3 Create caravan leaders, public trainers, and festival hosts that repeatedly gather compatible players around shared activities
  • 80.16.1.4 Implement guild fair and seasonal event routing — NPCs can direct players to open houses, teaching sessions, and recruitment windows
  • 80.16.1.5 Create live bulletin board integration with active player listings, guild asks, escort needs, and public event schedules
  • 80.16.1.6 Implement NPC gossip and rumor signals that subtly surface where activity and community energy currently exist
  • 80.16.1.7 Create recurring world choreography scheduler — social timing for campfires, parades, ceremonies, markets, hunts, and gatherings
  • 80.16.1.8 Implement quiet-space NPC guidance — route anxious or overwhelmed players to gentler social on-ramps and smaller gatherings
  • 80.16.1.9 Create AI-to-NPC-to-human handoff patterns so personal guide agents can route players into disclosed world-based introductions
  • 80.16.1.10 Implement playtests and telemetry loops measuring whether world social hosts increase real human social formation and repeat contact

Phase 80 Summary — Maya Social Fabric SOTA#

New Systems:

System Area Section Tasks
Social Graph Core 80.1.1 10
Discovery Engine 80.2.1 10
Community Group Finder 80.3.1 12
Recruitment Platform 80.4.1 10
Guild Community Operations 80.5.1 10
Federation Layer 80.6.1 8
Social Onboarding & Mentorship 80.7.1 12
World Social Layer 80.8.1 10
Trust & Compatibility 80.9.1 10
Trust & Safety Operations 80.10.1 12
Community Leadership Layer 80.11.1 10
Prosocial Recognition 80.12.1 8
Companion Community Platform 80.13.1 10
Community Health Intelligence 80.14.1 10
AI Social Facilitation Stack 80.15.1 15
World Social Hosts 80.16.1 10
TOTAL Phase 80 167

Community Outcomes After Phase 80#

Capability Before Phase 80 After Phase 80
Social discovery Basic friends/guild awareness Intent-aware player, guild, event, and mentor discovery
Group formation Parties/lobbies/matchmaking Structured, social-first LFG with recurring squad support
Guild recruitment Basic guild functionality Searchable community finder, trial roles, referrals, open house
New player integration Ad hoc Mentored first-group/first-guild pathways
Returner recovery Minimal Returner rescue, social recap, old-tie resurfacing
Community safety Baseline moderation Onboarding gates, automated safety, case management, health ops
Community leadership Officer basics Governance, staffing, succession, burnout prevention
Recognition Limited Mentor/helper/recruiter/invisible-labor recognition
Companion surfaces Fragmented Unified web/mobile community finder and event planning
Community analytics Sparse Social health intelligence and intervention playbooks
AI social support None Transparent AI wingman, concierge, mentor assistant, rescue
World-based social design Incidental NPC hosts, bulletin boards, rituals, social hubs

Combined with Phase 77's multiplayer infrastructure and Phase 79's living world systems, Phase 80 makes Maya capable of supporting not just massively multiplayer play, but massively multiplayer belonging.