Skip to content

Implementation Tracks

Related docs: High-Level System Design, Frontend Integration Guide, Implementation Roadmap, Prop Trading Module

Purpose

This document tracks dependency order across backend and frontend work. Use Implementation Roadmap for current shipped/missing status.

Backend Dependency Map

Implementation phasing dependency map

Source diagram: Pump Party Implementation Tracks

Backend Ownership Proposal

The clean handoff is to give Xavier end-to-end ownership of the backend runtime/economy path while Arthur focuses on frontend product completion and strategy-builder polish.

OwnerPrimary laneCurrent boundary
ArthurFrontend product, strategy-builder UX, clone strategy surface, AI prompt/control UXKeep shared API contracts and frontend integrations aligned with backend modules.
XavierUser/Auth, Economy, Prop Trading, Lifecycle orchestration, platform operationsOwn backend e2e correctness from wallet auth through paid audition, prop accounts, races, tickets, settlement, and monitoring.

The client OpenAPI contract is the frontend/backend decoupling layer. Frontend work should import generated-derived payload types from frontend/src/lib/api/client-api-types.ts and route helpers from frontend/src/lib/api/routes.ts rather than duplicating backend route strings or response shapes.

Backend Track Status

Percentages are approximate planning signals, not release gates.

TrackApprox. doneStatusNotes
Data Ingestion100%Backend shippedHyperliquid, Polymarket, DefiLlama storage, scheduled feature channels, and health APIs exist. Prod prep is tracked separately.
Clone Service100%Backend shippedCreate/list/read/update, drafts/versions, graph persistence, entitlements, owner public profiles, public reporting, and report-based moderation exist. Frontend integration remains.
AI Trading Engine100%Backend shippedPrompt v1, provider routing, workflow dry run/backtest, prop-account per-asset cadence/audit, prop-action submission, artifacts, token usage, and topology guardrails exist. Prod prep is tracked separately.
User Service & Auth100%Backend shippedSIWE/JWT/refresh rotation exists. Frontend still needs to replace Privy JWT app auth with Pump Party SIWE sessions; Privy embedded wallets can remain as signers.
Economy V1 (Audition)100%Backend shippedAudition-fee deposit verification, purchase idempotency, and entitlement grants exist. Prod prep is tracked separately.
Prop Trading Engine100%Shipped for v1Prop accounts, safety gates, paper fills, positions, mark-to-market, snapshots, admin controls, and audit logs exist. Race result consumption remains.
Lifecycle V1 (Audition)100%Backend shippedPaid audition submit/evaluate/retry/void, owner-safe routes, and due-audition evaluator worker exist. Frontend status/retry UI remains.
Competition Manager V1 (Arena Entry)100%Backend shippedPromotion Queue and Arena membership tables, read routes, service-token admission sync, worker cadence, approved-profile gates, and admin controls exist. Race launch belongs to later competition lifecycle work.
Platform Operations78%PartialWorker entrypoints, migrations, heartbeat storage, worker health API, ingestion health APIs, backtest queue leases, and Arena Entry cadence exist. Retries, dead-letter handling, alerting, backup checks, reconciliation monitors, and incident dashboards remain.

Frontend Dependency Map

Frontend dependency map

Source diagram: Pump Party Frontend Dependency Map

Frontend Track Status

TrackApprox. doneStatusBackend dependency
Auth UI30%Needs cutoverDirect SIWE endpoints are ready.
Clone management50%PartialClone create/list/read/update APIs exist; frontend needs to wire them through Pump Party auth.
Strategy builder80%PartialGraph save/publish and entitlement enforcement exist; UI needs cleanup against current domain language.
Audition UI15%NextQuote/submit and lifecycle submit/read/retry shapes exist; owner routes are frontend-safe.
Public profile/report UI20%NextPublic profile and report-based moderation routes exist.
Arena/race/ticket UI10%Contract-firstArena/Queue read routes exist; race, ticket, and settlement backend work remains.
Prop account views15%Optional for v1Snapshot, positions, fills, ledger routes exist behind service-token/admin boundaries.

Near-Term Sequence

  1. Wire frontend auth to SIWE and remove Privy assumptions from new screens.
  2. Wire audition-fee quote/submit and entitlement refresh.
  3. Add a frontend-safe path for audition lifecycle routes.
  4. Build audition status and retry UI.
  5. Add public profile submit/read/report UI.
  6. Add Arena/Queue display and operator views for the completed Arena Entry backend.
  7. Implement race lifecycle, ticket accounting, settlement, and payout authorization.