Eve library

V2 — Systems Deep Dive

Guide

Revision 1

On this page

The V2/ product area: the ~93 Nx projects that make up the off-rollback TypeScript service tier wrapping V2, Oshun's competitive fighting game — telemetry/analytics, live-ops, compliance/moderation, content pipelines, and game-system bridges that compose other Oshun domains around the shipped Unreal game without ever touching deterministic match simulation.

What this area is#

"V2" is the competitive fighting game product in the Oshun monorepo. The playable game itself is an Unreal Engine 5 project under V2/ue (the V2Combat C++ module, GAS-driven frame data, rollback netcode); the architecture reference lives under V2/architecture/ and the feature map under V2/features/. This page documents a different layer: the 93 tracked Nx projects that surround that game — 91 TypeScript service libraries under V2/services/, one esports tooling library under V2/tools/esports/, and one React marketing/ops web app under V2/web/.

Every one of the 91 service libraries follows the same shape and the same hard invariant. Each is a thin-to-substantial composition surface: rather than reimplementing a capability, it wires one or more existing Oshun domain packages (Iris, Maat, Kuanyin, Themis, Aphrodite, Aja, Isis, Psyche, Hestia, Maya, Euterpe, Calliope, Lakshmi, Shakti, Nous, Galatea, Sophia, Uzume, Veritas, Hathor, Bellona, Tara, Aje) into a V2-specific surface. The recurring export pattern is a buildV2…Surface(...) / runV2…(...) factory plus a cluster of constants — a …_PACKAGE_NAME, a …_BINDING_ID, a …_ROLLBACK_POLICY, the source-library identifiers it composes, and an event-topic list. The line counts confirm these are real implementations (from ~64 lines for the thinnest adapters to ~2,500 for remote-config-service), not scaffolds.

The central architectural boundary is rollback determinism. A fighting game's match simulation must be bit-deterministic for rollback netcode to work, so network/AI/analytics output may never enter it. Almost every service encodes this explicitly: a ROLLBACK_POLICY constant such as 'off-rollback-only', 'off-rollback-content-gate-only', or 'presentation-only-audio-subtitle', and logic that rejects calls originating in rollback frames. These services are the "everything around the match" tier — telemetry, live-ops, content build, compliance, broadcast — explicitly fenced off from the deterministic core.

How the sub-systems relate#

The services cluster into a handful of sub-systems (visible in each project.json's domain:* tag): a telemetry pipeline (telemetry-*) that moves events from the client firehose to a governed warehouse, feeding a layer of analytics surfaces (retention, churn, segmentation, economy, performance, difficulty) that read those warehouse rows; a live-ops stack (feature flags, remote config, season pass, hotfixes, live events, MOTD, patch notes, compensation) that changes the shipped game without a client patch; a compliance / trust-and-safety band (Aphrodite age/consent, Kuanyin moderation, Themis governance/disputes/UGC, EU AI Act); content pipelines (Aja mocap, Isis cosmetics/venue capture, commentary audio/face/lipsync); and a long tail of game-system bridges (minigames, racing, karaoke, arcade cabinets, world-boss raids, photo-mode voting, vault/estate). The analytics-on-top-of-telemetry and live-ops-config dependencies are the densest internal edges (e.g. economy-balance-tuning-interface composes remote-config-service; performance-analytics composes client-performance-telemetry; telemetry-integration-tests drives telemetry-ingestion → telemetry-data-pipeline end to end).

How it fits the wider system#

These projects are the outer ring of the V2 product: upstream of them sit the shared Oshun domain libraries they compose; downstream sits the cooked Unreal client (and its companion app, broadcast tooling, and back-end services) that consumes the manifests, payloads, and event topics they emit. A V2 service never exposes a domain package's internals directly — it adapts them into a V2 binding (content roots like V2/ue/Content/..., event topics like v2.match.crash.reported, manifest contracts named for V2-prefixed Unreal consumers) and stamps the rollback policy that keeps that output out of the simulation. The web app (@oshun/v2-web) and esports tools (@v2/esports-tools) are the operator/presentation face of the same product. Walk the "used by" / "depends on" edges on any node below to see exactly which Oshun domains it bridges and which V2 consumer reads its output.

Entity reference#

@v2/telemetry-ingestion#

The server-side ingestion endpoint (src/telemetry-ingestion.ts, plus telemetry-protobuf.ts): accepts POST /v2/telemetry/ingest, decodes JSON or protobuf TelemetryEventBatch payloads, validates the Phase-72 schema and standard topics, rejects PII payload fields, and queues accepted batches for the firehose. It is the front door of the entire telemetry-* pipeline.

@v2/telemetry-data-pipeline#

Owns the path from the v2-telemetry-firehose to governed warehouse rows (src/telemetry-data-pipeline.ts): models Kafka/Kinesis stream envelopes, re-validates batches via @v2/telemetry-ingestion, and transforms events into the warehouse.v2_telemetry.events row contract that the analytics surfaces read. runTelemetryDataPipelineOnce is the single-pass driver.

@v2/telemetry-data-export-api#

A governed raw-event export API (src/telemetry-data-export-api.ts): queryTelemetryDataExport reads warehouse.v2_telemetry.events through an injectable TelemetryDataExportSource, enforces researcher/analyst/admin authorization plus an approved purpose, applies topic and account-hash scopes, and paginates — the controlled seam for getting raw telemetry out.

@v2/telemetry-event-replay#

Historical replay / re-ingestion tooling (src/telemetry-event-replay.ts): runTelemetryEventReplayOnce pulls historical warehouse rows, verifies payload hashes, reconstructs TelemetryEvent records, groups them into deterministic offline replay batches, and resubmits them — for backfills and reprocessing.

@v2/telemetry-session-reconstruction#

Rebuilds player session timelines (src/telemetry-session-reconstruction.ts) from governed warehouse.v2_telemetry.events rows produced by the data pipeline: groups by sessionId, orders by telemetry sequence, and reconstructs per-session journeys for downstream funnel/behavior analysis.

@v2/telemetry-schema-migrations#

Validates additive-only telemetry schema plans (src/telemetry-schema-migrations.ts): registers new event types, applies optional payload-field defaults, and emits a release-gate report. Breaking changes are forced to a new wire major; minor/patch migrations must stay backward-compatible — the governance gate before emitters add new topics.

@v2/telemetry-privacy-compliance#

Applies consent, GDPR opt-in, CCPA Do-Not-Sell/Share opt-out, retention, and PII redaction to batches before analytics (src/telemetry-privacy-compliance.ts), composing @aphrodite/consent-engine decisions. The privacy gate sitting between ingestion and the analytics layer.

@v2/telemetry-rate-limiting#

Deterministic per-session sampling plus per-session/topic token-bucket limits (src/telemetry-rate-limiting.ts) applied before high-volume events reach production analytics, with explicit critical-override topics that bypass both sampling and limits.

@v2/telemetry-debug-mode#

Development-only verbose debug logging (src/telemetry-debug-mode.ts): debugTelemetryBatch emits one sanitized record per event in dev/test/QA/staging batches when explicitly requested, and is hard-disabled (release-build-disabled) on release/production/shipping builds — an honest fail-closed seam, not a stub.

@v2/telemetry-alerting-rules#

Evaluates aggregate samples against named live-ops alert rules (buildV2TelemetryAlertingRulesSurface, src/telemetry-alerting-rules.ts) such as crash-rate-spike-2x and player-count-drop-20pct, turning telemetry aggregates into operator alerts.

@v2/telemetry-bi-export-connectors#

Converts authorized export results into BI-tool formats (buildV2TelemetryBiExportConnectorsSurface, src/telemetry-bi-export-connectors.ts) — e.g. Grafana JSON data frames — composing @v2/telemetry-data-export-api. The connector layer on top of the governed export API.

@v2/telemetry-integration-tests#

A layer:test library (src/telemetry-integration-tests.ts) whose runTelemetryClientToWarehouseIntegration posts a client batch through the real in-memory ingestion endpoint, converts the queued firehose batch into a Kafka envelope, runs the data pipeline, and asserts the warehouse rows — an honest end-to-end harness across the telemetry chain, not production code.

@v2/ab-test-analysis-pipeline#

A/B test analysis (src/ab-test-analysis-pipeline.ts) composing @iris/analytics-ab for statistical-significance testing, effect-size estimation, and automatic winner detection over hashed-account telemetry; tagged domain:telemetry, binding v2.telemetry.ab-test-analysis-pipeline.

@v2/churn-prediction-model#

A fixed, interpretable logistic churn model (src/churn-prediction-model.ts, version v2-churn-logistic-2026-01): a self-contained logistic regression over hashed-account engagement features, anchored to @iris/analytics DEFAULT_USER_RETENTION_CONFIG.atRiskThresholdDays (surfaced as model metadata), to flag players likely to stop within a 7-day horizon — a real named model with documented coefficients, not Math.random().

@v2/client-performance-telemetry#

Client-side performance aggregation (ClientPerformanceTelemetryCollector, src/client-performance-telemetry.ts): buffers bounded per-session FPS / frame time / CPU / GPU / memory samples and flushes a v2.client.performance.sampled event with summary statistics. The source feeding performance-analytics.

@v2/performance-analytics#

Aggregates the client-performance samples (src/performance-analytics.ts), composing @v2/client-performance-telemetry, into FPS distribution by hardware tier, settings-preset adoption, and hitching frequency — the operator view of client performance.

@v2/crash-analytics-dashboard#

Crash-reliability surface (src/crash-analytics-dashboard.ts) anchored to the @tara/monitoring error-event vocabulary; aggregates V2 session and crash telemetry (v2.match.crash.reported, v2.player.session.started) into crash-rate-by-version/platform/hardware rows and top crash stacks.

@v2/difficulty-analytics#

Per-encounter difficulty surface (src/difficulty-analytics.ts) composing @iris/analytics-realtime for spike-alert snapshots; computes win/loss rate, retry counts, and completion time, and detects difficulty spikes (v2.encounter.difficulty.* metrics).

@v2/engagement-metrics-dashboard#

Engagement surface (src/engagement-metrics-dashboard.ts) using @iris/analytics engagement metric names; converts session telemetry into session-length distribution, sessions-per-week, and time-between-sessions aggregates.

@v2/player-behavior-heatmaps#

Behavior heatmaps (src/player-behavior-heatmaps.ts) composing @galatea/analytics/heatmap-engine for 2D movement/dwell grids from anonymized positional telemetry, adding V2-specific death/linger overlays and 3D voxel extensions.

@v2/player-segmentation#

Player segmentation (src/player-segmentation.ts) composing @iris/analytics metric identifiers; classifies hashed-account telemetry into spend tiers (whale/dolphin/minnow/non_spender), Bartle-style motivation segments, and custom rule segments.

@v2/realtime-player-count-dashboard#

Operational concurrency dashboard (src/realtime-player-count-dashboard.ts): consumes segment samples, keeps only the latest per region/mode/platform segment, and computes current totals and per-segment breakdowns for live concurrency.

@v2/retention-cohort-analysis#

Retention cohorts (src/retention-cohort-analysis.ts) composing @iris/analytics-cohort for daily cohort construction; produces day-1/-7/-30 retention curves segmented by acquisition source.

@v2/session-funnel-analysis#

New-player funnel (src/session-funnel-analysis.ts) composing @iris/analytics-funnel for ordered-journey analysis across tutorial → first mission → open-world entry → first purchase, surfacing drop-off at each step.

@v2/economy-analytics#

Economy analytics surface (src/economy-analytics.ts) anchored to @maat/finance; aggregates economy telemetry into currency earn/spend rates, inflation tracking, and item price-effectiveness metrics.

@v2/economy-analytics-dashboard#

Operator economy dashboard (src/economy-analytics-dashboard.ts), also anchored to @maat/finance: currency supply velocity, average wealth by level, item price trends, and sink/source ratios, with trend/flow-balance typing (rising/falling/stable, source-heavy/sink-heavy/balanced).

@v2/economy-balance-tuning-interface#

Operator tuning UI surface for drop rates, prices, and rewards (src/economy-balance-tuning-interface.ts); composes @v2/remote-config-service validation and staging-preview APIs so economy values change through remote config without a client patch.

@v2/maat-finance-ledger#

A thin but real service bridge (src/maat-finance-ledger.ts, ~66 lines) to @maat/finance economy authority: validates spend/refund, region-aware pricing, and regulatory caps before V2 mirrors approved changes into the in-engine currency ledger, with a constrained offline-approval path when authority is unavailable.

@v2/maat-balance-dashboard#

Fighting-game balance dashboard surface (src/maat-balance-dashboard.ts) that deliberately composes existing Maat packages (@maat/intelligence for pick-rate / win-rate-on-hit / win-rate-on-block detection) rather than a standalone V2 stack.

@v2/shakti-ruleset-bridge#

Adapts @shakti/fighting-ruleset-bridge output for V2 balance authoring (src/shakti-ruleset-bridge.ts, ~179 lines): emits deterministic CSV rows for V2BalanceImporter, carries Shakti reference-card metadata for Sophia codex ingestion, and rejects rollback-frame calls.

@v2/feature-flag-service#

Live-ops feature flags (src/feature-flag-service.ts, ~900 lines): builds validated flag snapshots, evaluates per-account rollout buckets, supports a client SDK and kill-switch policy, and emits compact toggle payloads that change shipped features without a client patch.

@v2/remote-config-service#

The largest service in the area (src/remote-config-service.ts, ~2,515 lines): builds validated remote-config snapshots, resolves per-client values, tracks immutable config versions, and publishes rollback snapshots when a bad config ships — the configuration backbone several other live-ops services compose.

@v2/game-mechanics-ab-testing#

Live-ops A/B framework for game mechanics (src/game-mechanics-ab-testing.ts): deterministic hashed-account assignment to weighted variants, exposure / engagement / retention event recording, and statistical-significance reporting.

@v2/season-pass-service#

Season-pass progression (src/season-pass-service.ts, ~1,517 lines): an XP-based track with free and premium lanes, per-level rewards, server-authoritative XP grants, duplicate-grant idempotency, and a no-patch client payload.

@v2/dlc-content-delivery-service#

DLC / expansion delivery (src/dlc-content-delivery-service.ts): publishes downloadable content packs (fighter packs, story expansions, cosmetic packs), verifies entitlement before download, and returns unlock state, with defined endpoint and pack-kind enums.

@v2/hotfix-delivery-service#

Hotfix delivery (src/hotfix-delivery-service.ts): publishes signed manifests for small data-only patches (balance tweaks, exploit fixes, data corrections) that ship without platform certification.

@v2/hotfix-testing-pipeline-service#

Pre-deploy hotfix gate (src/hotfix-testing-pipeline-service.ts): evaluates automated regression results for a hotfix and grants deployment approval only when every required test is present and passed — missing/blocked/failed required tests block the hotfix.

@v2/limited-time-game-mode-service#

Limited-time mode scheduling (src/limited-time-game-mode-service.ts): a server-authoritative schedule that enables/disables game modes, publishes active queue and ruleset IDs, and marks event-exclusive modes without a client patch.

@v2/live-event-content-delivery-service#

On-demand live-event content manifests for maps, cosmetics, and NPC dialogue (src/live-event-content-delivery-service.ts): plans downloads only for missing event assets, uses content hashes for cache decisions, and rejects malformed bundles.

@v2/live-event-scheduling-service#

Server-authoritative live-event windows (src/live-event-scheduling-service.ts): defines start/end times, enables event modes and rewards only during the active window, all without a client patch.

@v2/live-ops-analytics-service#

Live-ops aggregate analytics (src/live-ops-analytics-service.ts): computes event-participation rates, season-pass completion rates, and hotfix effectiveness from server-authoritative aggregates, publishing only normalized metrics (never raw player identifiers).

@v2/maat-live-service-calendar#

A thin wiring (src/maat-live-service-calendar.ts, ~66 lines) of V2 live-ops planning to @maat/strategy as the source of truth for ranked seasons, Crown Points pools, and scoring rules.

@v2/message-of-the-day-service#

MOTD push (src/message-of-the-day-service.ts): validates authored messages, filters active windows, applies client targeting, preserves per-account dismissal, and emits compact payloads for events/downtime/patch notes — no client patch required.

@v2/patch-notes-service#

Structured patch notes (src/patch-notes-service.ts): publishes notes and the in-game payload, enforcing required categories (balance, bug fixes, new content) on every release.

@v2/player-compensation-service#

Player compensation (src/player-compensation-service.ts): grants items and currency to players affected by bugs/outages via incident-scoped, evidence-backed, approval-gated, server-authoritative campaigns.

@v2/aja-studio-mocap-pipeline#

Studio mocap path for Vicon/OptiTrack shoots (src/studio-mocap-pipeline.ts): treats the hardware as recording-only and owns software cleanup, contact/root repair, and V2-skeleton retarget through @aja/motion-pipeline-sdk and @aja/neural-retargeting, writing to V2/ue/Content/Animation/Mocap/Studio.

@v2/aja-markerless-capture-pipeline#

Pickup-session markerless mocap (src/markerless-capture-pipeline.ts) replacing planned Move.AI/Plask usage with in-house @aja/depth-sensing and @aja/human-mesh-recovery, on a fixed content-build-only rollback policy.

Binds accepted Aja motion to the Bellona frame-snap path (src/livelink-export.ts): @aja/neural-retargeting clip → @bellona/mocap resample/snap onto integer 60 Hz frames, emitting a v2.mocap.frame_snap.livelink_ready event under a cooked-animation-only policy.

Wires Aja capture consent to the (forthcoming) Themis NIL ledger contract (src/consent-nil-ledger.ts): @aja/consent-management records per-performer consent/withdrawal and cascades revocation to @themis/likeness within a 15-min SLA constant — an honest cross-domain seam to a not-yet-shipped package.

@v2/aje-faction-governance#

Optional fan-token-gated faction governance (src/aje-faction-governance.ts): builds an @aje/governance Snapshot voting space, but the surface stays blocked unless the player opts in and the platform cert-ban table (V2/legal/platform-cert-bans.json) clears fan_token_gated_gameplay — a fail-closed gate, not an always-on feature.

@v2/aje-web3-cosmetic-ownership#

Opt-in Web3 cosmetic ownership (src/aje-web3-cosmetic-ownership.ts): composes @aje/identity (wallet/DID binding) and @aje/nft (cosmetic ownership metadata) under an off-rollback-opt-in-cosmetic-only policy, gated behind the same platform cert-ban clearance.

@v2/aphrodite-age-gate#

Replaces the standalone V2 age gate with the @aphrodite/age-verification backend driver (src/aphrodite-age-gate.ts, ~82 lines): controls gore tier and other age-gated content under an off-rollback-content-gate-only policy.

Replaces standalone V2 consent handling with @aphrodite/consent-engine (src/aphrodite-consent-surfaces.ts, ~68 lines): per-feature consent (telemetry and others) on an off-rollback-consent-surface-only policy.

@v2/aphrodite-licensed-likeness-safety#

Binds licensed-fighter likeness checks (src/aphrodite-licensed-likeness-safety.ts) to @aphrodite/performer-sovereignty and @aphrodite/performer-autonomy, consuming the Themis NIL ledger stamp by contract string — the likeness-safety gate for partner-IP fighters.

@v2/eu-ai-act-surface#

EU AI Act compliance surface for V2's Adaptive AI / AI Director (src/eu-ai-act-surface.ts): composes @psyche/action-safety (classifier transparency, opt-out) and @nous/safety (Model Card hosting), pointing at the adaptive-AI model card and a registry of shipping AI surfaces, on a disclosure-and-audit-only policy.

@v2/themis-privacy-dsr-routing#

Data-subject-request compliance surface (src/themis-privacy-dsr-routing.ts): composes @themis/privacy for access/erasure/portability/rectification with @oshun/data-residency for route zone, residency headers, and per-region queue selection.

@v2/iris-commentary-orchestration#

The TypeScript contract behind the V2AICommentary Unreal plugin (src/v2-ai-commentary.ts, ~614 lines): calls createMatchCommentaryStream from @iris/conversation-orchestration, forces determinismMode: "off-rollback-only", and rejects cues marked unsafe for rollback — the core AI-commentary brain.

@v2/calliope-commentator-personas#

Validates the launch commentator roster authored as @calliope/persona-live AI artists (src/commentator-personas.ts): loads V2/ue/Content/V2/Audio/Commentary/commentator-personas.json and verifies each persona has cleared @iris/voice clone metadata, brand metadata, and signed talent provenance — a cook-time validation gate.

@v2/euterpe-commentary-ducking#

Commentary mix ducking (src/commentary-ducking.ts): consumes dynamic-music context from @euterpe/accompany, computes sidechain ducking with @euterpe/master gain math, and emits Unreal audio-modulation metadata for the V2.DynamicMusic bus under an audio-mix-only policy.

@v2/psyche-commentary-face-animation#

Commentator face animation (src/commentary-face-animation.ts): converts @iris/voice phoneme timing into @psyche/avatar-lipsync visemes, layers @psyche/avatar-expressions ARKit curves, and produces Unreal export metadata.

@v2/isis-commentary-lipsync-pipeline#

AI-commentary lipsync contract (src/commentary-lipsync-pipeline.ts) replacing the prior Audio2Face gap: uses @isis/visual-dubbing for audio ingest, phoneme extraction, visual dubbing, lip-sync quality validation, and Unreal curve export.

@v2/kuanyin-first-line-moderation#

Primary moderation path (src/kuanyin-first-line-moderation.ts, ~520 lines) replacing Two Hat / Community Sift / Hive AI / AWS Rekognition with @kuanyin/precognition and @kuanyin/foundation; Hive AI and Rekognition are retained only as named media fallbacks — an honest first-line/fallback split.

@v2/kuanyin-community-harmony#

Crew / faction / Battle-Hub community-health surface (src/kuanyin-community-harmony.ts) composing @kuanyin/community-harmony for temperature scoring, tension detection, faction formation, intervention triggers, raid detection, defense mode, and new-user throttles.

@v2/kuanyin-mindful-friction#

Pre-send moderation friction (src/kuanyin-mindful-friction.ts): routes report submissions and flagged-message sends through @kuanyin/mindful-friction (pause-and-breathe overlays, Samma Vaca reflection gates) before content is released.

@v2/kuanyin-performer-protection#

Licensed-fighter likeness shielding (src/kuanyin-performer-protection.ts): composes @kuanyin/performer-protection (real-time shield, performer blindness, boundary enforcement, emergency lockdown, dashboard rules) with the forthcoming @themis/likeness NIL ledger stamp.

@v2/themis-community-governance#

Crew / clique / stable / faction governance (src/themis-community-governance.ts): composes @themis/community sports-club governance managers so V2 publishes rule votes, member reputation standing, and constitution-amendment outcomes from one contract.

@v2/themis-dispute-resolution#

DSA Statement-of-Reasons, moderation appeals, and tournament-result disputes (src/themis-dispute-resolution.ts): composes @themis/dispute-resolution for machine-readable notices, appeal routing, reviewer queues, and auditor-backed records.

@v2/themis-originality-shields#

Public-UGC accept-gate for custom championships, decals, logos, and music swaps (src/themis-originality-shields.ts): composes the Themis Originality Shields family (@themis/music-shield, visual-shield, text-shield, video-shield, design-shield).

@v2/oshun-identity-binding#

Consumes @oshun/identity as the canonical account state (src/oshun-identity-binding.ts, ~81 lines): V2 keeps no publisher-account root of its own — PSN, Xbox Live, Nintendo Account, and Steam are linked credentials on one Oshun identity.

@v2/cross-product-entitlement#

Adapts signed @oshun/identity entitlement claims into V2 grants (buildV2CrossProductEntitlementSurface, src/cross-product-entitlement.ts, ~64 lines): V2 receives only claim decisions and redacted grant IDs (never raw source-product activity) for Lilith/Shakti/Calliope cross-product titles.

@v2/oshun-adapter#

The Node-side event-bus adapter (src/adapter.ts, events.ts, platform.ts, quality-gate.ts, reaction-sink.ts): lets V2 react to approved Oshun event-bus messages without letting network output enter deterministic gameplay simulation. The most structurally elaborate of the platform-glue services and the generic ingress other adapters lean on.

@v2/iris-accessibility#

Wires @iris/accessibility into V2's main client and companion surfaces (src/iris-accessibility.ts, ~78 lines): caption streaming, dyslexia-friendly typography, cognitive assistive UI, screen-reader bridge semantics, and native UE accessibility hooks.

@v2/iris-realtime-translation#

Spectator-chat translation and commentary localization (src/iris-realtime-translation.ts): composes @iris/voice via createVoiceCallTranslation, registers participants and locale receivers, and returns delivery transcripts for chat, commentary subtitles, broadcast overlays, and companion surfaces.

@v2/psyche-caption-streaming#

Real-time match captions (src/psyche-caption-streaming.ts) through @psyche/caption-streaming: owns the session plan for in-match HUD captions, spectator overlays, replay transcripts, companion second-screen captions, and broadcast observer captions.

@v2/psyche-ai-director-hints#

Adapter between V2AdaptiveAI and @psyche/behavior-prediction (src/psyche-ai-director-hints.ts): non-rollback modes consume live per-player tendency hints; rollback-with-CPU modes sample hints at match load and serialize them — the rollback-safety boundary for AI Director input.

@v2/shakti-style-classification#

Adapts @shakti/sota-critical combat-style classification into AI Director matchup hints for V2AdaptiveAI (src/shakti-style-classification.ts): classifies each player as boxer / kickboxer / striker / grappler / submission-specialist.

@v2/isis-cosmetic-pipeline#

Content-build contract for V2Mode_Cosmetic variants (src/cosmetic-pipeline.ts): wires @isis/3d-generation (base mesh) and @isis/ai-texturing (PBR textures/material variants) into a cosmetic build path.

@v2/isis-venue-capture-pipeline#

Real-world venue capture for V2 stages and race tracks (src/venue-capture-pipeline.ts): wires @isis/gaussian-splatting through capture ingest, preprocessing, splat training, and optimization for the resulting stage assets.

@v2/hathor-npc-adapter#

Bridge from open-world encounter hooks to Hathor @hathor/llm-npc (src/npc-bridge.ts + npc-dialogue-cache.ts): accepts only specific overworld contexts (World Tour, Tekken Force, Devil Within, DJ street, MyCAREER backstage, SC Chronicles), forces rollbackPolicy: "off-rollback-only" and deterministicGameplay: false, and caches generated dialogue under V2/ue/Content/Generated/NPCDialogue.

@v2/hestia-cooking-minigame-bridge#

Cook-time bridge for the cooking-simulator minigame (src/hestia-cooking-minigame-bridge.ts): composes @hestia/ai-ml recipe generation, @hestia/cooking sessions, @hestia/education walkthroughs, @hestia/ingredients coverage, and @hestia/pantry sourcing.

@v2/maya-minigame-suite-bridge#

Authoring-only bridge for the minigame suite — pinball, air hockey, mini-golf, darts, pool (src/maya-minigame-suite-bridge.ts): reuses Maya @maya/games projectile physics, @maya/physics readiness, @maya/scene graph readiness, and @maya/client input bindings.

@v2/karaoke-rhythm-combat-bridge#

Authoring-only karaoke / rhythm-combat fusion bridge (src/karaoke-rhythm-combat-bridge.ts, ~920 lines): composes @euterpe/genesis procedural backing tracks, @euterpe/accompany adaptive scoring, @euterpe/protect streamer-safe swap/originality checks, and Calliope persona inputs.

@v2/tekken-bowl-arcade-cabinet-bridge#

Cook-time bridge for Tekken Bowl and Battle Hub arcade cabinets (src/tekken-bowl-arcade-cabinet-bridge.ts): reuses @maya/games projectile primitives for the bowling-lane probe and @maya/client plugin loading for per-cabinet plugins; V2 owns the actual Unreal gameplay and Fighter-Coin gating.

@v2/racing-ecosystem-bridge#

Authoring-only racing bridge (src/racing-ecosystem-bridge.ts): composes Galatea kinematics/whole-body control for vehicle-as-articulated-body driver probes, Saraswati EV powertrain primitives for hybrid/electric modeling, and Maya Genesis terrain/urban readiness for tracks.

@v2/world-boss-community-raid-bridge#

Post-match composition surface for world-boss and community-raid events (§134, src/world-boss-community-raid-bridge.ts, ~1,172 lines): produces the server-side raid manifest consumed by V2Mode_WorldBoss, V2Mode_AsyncRaid, and V2Mode_CommunityChallenge.

@v2/photo-mode-tournament-voting-bridge#

Photo-Mode tournament submission moderation plus community/jury voting (§133, src/photo-mode-tournament-voting-bridge.ts, ~964 lines): produces the v2.photo-mode-tournament-voting-manifest consumed by V2PhotoMode, V2ReplayTheater, V2CommunityHub, and V2CompanionApp.

@v2/per-account-vault-estate-bridge#

Control-plane composition surface for per-account vault inheritance and estate transfer (§137, src/per-account-vault-estate-bridge.ts, ~1,111 lines): produces the estate-transfer manifest consumed by V2Vault, V2Profile, V2OnlineServices, and V2CompanionApp.

@v2/lakshmi-responsible-play-spend-insight#

Responsible-play spend insight (src/responsible-play-spend-insight.ts): uses @lakshmi/transactions to normalize/categorize purchases, @lakshmi/budgeting for budget pace and cap exposure, and @lakshmi/behavioral for opt-in impulse prompts, nudges, and weekly reflection summaries.

@v2/concordia-substrate#

V2-owned composition boundary for the planned Concordia substrate (src/concordia-substrate.ts, ~1,173 lines). The @concordia/* library does not exist yet, so this directly wires @nous/cooperative-bargaining, @nous/preference-inference, @nous/agreement-search, @nous/concordia-sealed-memory, @iris/concordia-assistant, @kuanyin/concordia-restorative, and @oshun/config to handle anti-cheat appeals, tournament disputes, and crew conflicts — substantial real code standing in for a not-yet-built domain, honestly labelled as such.

@v2/nous-anti-cheat-classifiers#

Binds fair-play telemetry to the Nous anti-cheat classifier suite (src/nous-anti-cheat-classifiers.ts, ~169 lines): V2 publishes labeled training examples on @oshun/event-bus topics and @nous/training owns the smurf / win-trading / cheat training loop.

@v2/sophia-release-candidate-ingestion#

Cook-time bridge (src/sophia-release-candidate-ingestion.ts + a cli.ts and an ingest Nx target) that pushes the frame-data spreadsheet and release-candidate patch-notes corpus through @sophia/ingestion before a cook starts; intentionally off rollback authority and producing a manifest.

@v2/esports-tools#

The esports tooling library under V2/tools/esports/ (esports-broadcast-pipeline.ts, arena-led-projection-integration.ts, veritas-esports-fact-checking.ts): wires @uzume/broadcast as the primary broadcast pipeline, @uzume/lumina + @uzume/prism for arena LED/projection mapping (buildV2ArenaLedProjectionIntegration), and @veritas/fact-checking for post-match claim verification — all presentation/operations, never feeding rollback simulation.

@oshun/v2-web#

The V2 marketing/ops web app (V2/web/, Vite + React): src/App.tsx renders a roster/modes/changelog/press-kit surface from src/data/marketingData.ts (the Fighter roster mirrors the canonical V2LaunchRosterData.cpp, original-IP only) and a build-target report from src/data/buildReportData.ts; tested with Vitest and Playwright (e2e target). The product's public/operator face, not a gameplay service.