Perpetual Futures Engine · Master Document Index
| Version: v1.0 |
Status: Active |
Language: English (translated from Chinese) |
Updated: 2026-04-08 |
Authoritative source: ../zh/index.md
Document Structure
| Directory |
Purpose |
mvp/ |
MVP Architecture & Implementation Specification |
prd/ |
Product Requirements Documents (PRD) |
scenarios/ |
Business Scenario Records |
trading/ |
Trading Process Flows |
MVP — Implementation Specification
The MVP (Minimum Viable Product) specification covers design principles, architecture, cost/revenue analysis, development planning, launch strategy, and acceptance criteria for the three-phase rollout.
| File |
Title |
Purpose |
| 00-revision-summary.md |
Revision Summary |
Overview of MVP design changes, document structure, and key decisions |
| 01-architecture-baseline.md |
Architecture Baseline |
Core design principles, two-domain architecture, interface contracts, and consistency strategies |
| 02-domain-architecture.md |
Domain Architecture |
Detailed responsibility scope, unidirectional dependencies, message queue design, and reconciliation |
| 05-launch-rollback.md |
Launch & Rollback Manual |
Canary strategies, control matrix, alerts, degradation levels, and rollback procedures |
| 06-acceptance.md |
Acceptance Checklist |
Phase-by-phase verification items, performance targets, test coverage, and sign-off criteria |
Reading Order: Start with 00-revision-summary → 01-architecture-baseline → then phase-specific docs (02, 03, 04, 05, 06)
Core Architecture Principles
Platform is the sole risk controller and liquidation authority. Hyperliquid (HL) is only an execution channel.
| Principle |
Description |
| Dual Routing |
≤$10K → Platform internalized (INTERNAL); >$10K → Hyperliquid (HYPERLIQUID) |
| Dual Position |
INTERNAL and HYPERLIQUID positions can coexist for the same user |
| Unified Liquidation |
All liquidation decisions made by Platform, regardless of position location |
| Data Reuse |
Prices, funding rates, leverage, and listed assets all sourced from HL |
PRD — Product Requirements
Scenario Records
Trading Process Flows
Glossary
| Term |
Definition |
| INTERNAL |
Platform internalized position — not opened on HL |
| HYPERLIQUID |
Position routed to and executed on Hyperliquid |
| Internalization (B-Book) |
Platform acts as user’s counterparty |
| Client Loss (客损) |
User loss = platform’s counterparty gain |
| Routing Threshold |
Notional value cutoff (default $10,000) |
| Net Exposure |
Platform’s accumulated directional risk per asset (INTERNAL only) |
| Calculation Drift |
Difference between Platform’s calculated PnL and HL’s actual PnL |
| Aggregation |
Moving assets from user deposit addresses to platform hot wallet |
| Hot Wallet |
Online-signing wallet for daily withdrawals |
| Cold Wallet |
Offline-signing wallet for large fund storage |