caishen

Caishen Trading Platform

RISE Framework Specification - Master Index

Version: 1.0
Document ID: caishen-rise-spec-v1.0
Last Updated: 2025-01-31
Attribution: Guillaume D.Isabelle

Overview

Caishen is a comprehensive Fractal Breakout Trading Platform that enables traders to:

• Analyze market data through chaos theory indicators (Bill Williams methodology)
• Identify fractal breakout opportunities
• Create and manage strategic entry orders (BDBO - Bill Williams Divergent Bar Breakout)
• Track trading timelines and execute automated strategy management

This document serves as the master index for all RISE framework specifications that describe the Caishen platform architecture and behavior in a codebase-agnostic manner.

---

Core Creative Intent

What Caishen Enables Users to Create:

• Strategic entry orders based on fractal breakout patterns
• Visual analysis of market chaos indicators across multiple timeframes
• Automated strategy lifecycle management with state machine logic
• Historical trading data snapshots for review and learning

Desired Outcomes:

1. Users naturally identify high-probability trading opportunities through visual chart analysis
2. Entry orders are placed at fractal breakout levels with proper risk management
3. Strategy states advance automatically based on market price action
4. Complete audit trail of trading decisions and market snapshots

---

Service Architecture

The platform follows a Domain-Driven Service Architecture with clear separation of concerns:

┌─────────────────────────────────────────────────────────────────┐
│                    PRESENTATION LAYER                           │
│  ┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐ │
│  │  WinForms UI    │  │  Express API    │  │  Console Apps   │ │
│  │  (Charting)     │  │  (REST/JSON)    │  │  (CLI Tools)    │ │
│  └─────────────────┘  └─────────────────┘  └─────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│                    SERVICE LAYER                                │
│  ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐  │
│  │   ADS   │ │   SDS   │ │   PDS   │ │   CDS   │ │   IDS   │  │
│  │Analysis │ │Strategy │ │ Price   │ │ Chaos   │ │Indicator│  │
│  │ Data    │ │  Data   │ │  Data   │ │  Data   │ │  Data   │  │
│  │ Service │ │ Service │ │ Service │ │ Service │ │ Service │  │
│  └─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘  │
│  ┌─────────┐ ┌─────────┐ ┌─────────┐                          │
│  │  BITT   │ │   SE    │ │   THS   │                          │
│  │Timeline │ │ SEngine │ │Historic │                          │
│  │ Service │ │ (Chart) │ │Snapshot │                          │
│  └─────────┘ └─────────┘ └─────────┘                          │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│                    DATA LAYER                                   │
│  ┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐ │
│  │   SQL Server    │  │    MongoDB      │  │  JSON Files     │ │
│  │   (Entities)    │  │  (TimeSeries)   │  │   (CDB DTOs)    │ │
│  └─────────────────┘  └─────────────────┘  └─────────────────┘ │
└─────────────────────────────────────────────────────────────────┘

---

Specification Index

Core Services

Spec ID	Component	Description	Link
01	ADS	Analysis Data Services - Chart data creation and analysis	01-ads-analysis-data-services.md
02	SDS	Strategic Data Services - Entry order management	02-sds-strategic-data-services.md
03	PDS	Price Data Services - Market data processing	03-pds-price-data-services.md
04	CDS	Chaos Data Services - Fractals and chaos indicators	04-cds-chaos-data-services.md
05	IDS	Indicator Data Services - Technical indicators	05-ids-indicator-data-services.md
06	BITT	Timeline Services - Market charting timeline	06-bitt-timeline-services.md
07	SE	SEngine - Charting engine core	07-se-charting-engine.md
08	THS	Timeline History Services - Snapshots	08-ths-history-services.md

Data Schemas

Spec ID	Component	Description	Link
10	Data Schemas	Core data entities and relationships	10-data-schemas.md
11	DTO Contracts	Service data transfer objects	11-dto-contracts.md

UI Components

Spec ID	Component	Description	Link
20	Charting UI	WinForms charting components	20-charting-ui-components.md
21	Strategy UI	Order entry and strategy management	21-strategy-ui-components.md

API & Integration

Spec ID	Component	Description	Link
30	Express API	REST API for chart data access	30-express-api.md
50	JGT Bridge	Integration with JGT ecosystem	50-jgt-bridge.md

Workflows

Spec ID	Component	Description	Link
40	Fractal Breakout	End-to-end fractal breakout workflow	40-fractal-breakout-workflow.md

---

Key Concepts

POV (Point of View)

A POV represents a specific market instrument at a specific timeframe. Format: {Instrument}_{Timeframe} (e.g., EUR-USD_H4)

CDB (Chaos Data Builder)

The ChaosDataBuilder is the central data structure containing all chaos indicator values for a given POV at a point in time.

BDBO (Bill Williams Divergent Bar Breakout)

A BDBO Strategy represents a fractal breakout entry order with defined breakout price, direction, and state machine logic.

CRSI (Currency Relative Strength Index)

CRSI provides relative strength comparison across currency pairs for a base currency.

Timeframe Context (CTX)

Standard timeframes: m5, m15, H1, H2, H3, H4, H6, H8, D1, W1, M1

---

Creative Advancement Patterns

Pattern 1: Chart Analysis → Strategy Creation

User views chart → Identifies fractal breakout → Creates BDBO strategy → System monitors

Pattern 2: Price Update → Strategy Execution

Price updates → CDB recalculates → BDBO states advance → Orders execute

Pattern 3: Historical Review → Learning

User loads snapshot → Reviews past decision → Analyzes outcome → Improves strategy

---

Implementation Technology Stack

Original Implementation (C#/.NET):

• .NET Framework 4.8
• Entity Framework (SQL Server)
• WinForms UI
• WCF Services

Target Implementation (Python/TypeScript):

• Python: Core services, data processing, indicators
• TypeScript: Web UI, REST API
• PostgreSQL or MongoDB: Data persistence
• FastAPI or Express: API layer

---

Next Steps for Implementation

1. Review each individual RISE spec for detailed behavior
2. Implement data schemas first (Spec 10)
3. Build indicator calculations (Spec 05)
4. Create CDS/CDB core (Spec 04)
5. Develop strategy state machine (Spec 02)
6. Build API layer (Spec 30)
7. Create UI components (Specs 20-21)
8. Integrate end-to-end workflow (Spec 40)