THE HANDBOOK
PHILOSOPHY · ARCHITECTURE · ENGINES
Version 1.0 · Giblets Creations · March 2026
Foreword
I built CCE in three weeks on a phone.
That sentence sounds like a boast. It isn't. It's a statement of constraint — and of what constraint produces when you refuse to let it be an excuse.
I didn't have a trading desk. I didn't have a quant team, a Bloomberg terminal, or a cloud budget. I had a Samsung S24 Ultra, Termux, a Node.js runtime, and a set of principles I'd been refining for years across entirely different domains.
The principles came first. They always do. I've applied the same thinking to 3D printing, robotics, embedded systems, and IoT. The domain changes. The underlying pattern doesn't: understand the environment, define the states, build the transitions, test everything, never override the system.
This handbook documents the philosophy behind every design decision, the architecture that ties everything together, and each of the eleven engines that comprise the platform. It does not document the proprietary signal logic — the specific thresholds and weights that constitute the edge. That is the one thing that stays closed.
Everything else is here.
James Gilbert
Giblets Creations
About This Handbook
This handbook is the complete documentation of the Cascade Compounding Engine (CCE) — its philosophy, architecture, and the eleven engines that comprise the platform.
CCE is not a trading bot. It is an autonomous trading operating system built entirely on a mobile device. Eleven independent engines run across three ecosystems, coordinated by an intelligence layer that watches, alerts, and analyses. All of it runs on a Samsung S24 Ultra, managed by PM2, with no cloud dependency and no third-party custody.
DEVELOPER DOCUMENTATION
This handbook serves as the strategic blueprint. For implementation details, signal logic references, and raw engineering notes for every aspect of the program, refer to the technical documentation hosted in the repository.
Browse /docs on GitHub1. The Three Pillars
CCE is built on three foundational principles that govern every line of code, every state transition, and every design decision. These pillars are not aspirational. They are enforced.
1.1 Environment First, Action Second
Most trading systems ask: "Where is price going?" This is the wrong question. Price prediction is a game with no winners over the long term. CCE asks a different question: "What is the environment?"
The environment — volatility, sentiment, trend structure, macro conditions — determines whether any action is appropriate. In a hostile environment, the correct action is inaction. In a favourable environment, the correct action is deployment.
1.2 No Prediction. No Emotion. No Exceptions.
CCE does not predict. It observes, filters, and responds. Prediction is opinion. Opinion is emotion. Emotion loses money.
The system has no opinion on whether Bitcoin will go up or down. It has conditions. When conditions are met, it acts. When conditions are not met, it does not act. There is no grey area. There is no discretionary override.
1.3 Transparency by Default
A trading system you cannot understand is a system you cannot trust. Every engine's logic is documented. Every state transition is logged. Every market condition that influenced a decision is recorded. The architecture is public. The philosophy is public.
2. The Cascade Principle
The name 'Cascade Compounding Engine' encodes the system's core operational principle. There are two interlocking dimensions to the cascade: cascade as structure, and cascade as compounding.
Every engine in CCE is structured as a sequential cascade of states. Entry to later states requires confirmation at each earlier stage. No engine skips states. No engine jumps from resting to maximum deployment on a single signal.
3. Engine Typology
3.1 Strategic Engines — Weather Vanes
Strategic engines are patient. They wait for macro conditions to align before deploying capital. They do not care about 5-minute price moves. They care about 4-hour, daily, and weekly structure.
3.2 Tactical Engines — Waterwheels
Tactical engines are active. They harvest opportunity continuously, regardless of macro environment. They operate on shorter timeframes and rely on mechanical, repeatable patterns.
3.3 Observer Engines — Memory
Observer engines are passive. They do not trade. They watch, record, and alert. They are the platform's intelligence layer.
4. The Intelligence Layer
CCE's intelligence layer is a three-stage pipeline that transforms raw observations into actionable intelligence. A fourth stage — G.O Orchestrator — is planned for a future phase.
- O.E Observer: Runs every 15 minutes. Takes a snapshot of all states. Builds the dataset.
- O.E Sentinel: Runs every 15 minutes. Detects anomalies and sends alerts.
- O.E Strategist: Runs every hour. Analyses patterns and recommends allocation.
5. Local-First Sovereignty
CCE runs locally. Your API keys never leave your device. The system is yours. No third party can take it down, change its behaviour, or access your funds. This is not merely a technical choice — it is a philosophy.
6. S.E Crypto
Status: 🟢 Live | Cycle: 4 Hours
S.E Crypto is the flagship engine. It monitors the cryptocurrency market and deploys capital through a sequence of states that correspond to phases of the crypto market cycle. In extreme fear environments (Fear & Greed below 20), S.E Crypto holds cash. Not because it predicts further decline — because the environment does not support deployment.
7. S.E Forex
Status: 🔵 Dry Run | Cycle: 1 Hour
S.E Forex is a mean-reversion engine. It waits for price to reach statistical extremes during liquid sessions. It does not act during off-hours or in low-volatility drifts.
8. S.E REIT
Status: 🔵 Dry Run | Cycle: 24 Hours
S.E REIT monitors the interest rate environment. It is built on the lag between Federal Reserve policy shifts and the repricing of Real Estate Investment Trusts.
9. S.E Stocks
Status: 🔵 Dry Run | Cycle: 24 Hours
S.E Stocks is a volatility-aware engine. It refuses to deploy when VIX is elevated. It operates only in low-volatility trending regimes where the market rewards participation.
10. S.E Commodities
Status: 🔵 Dry Run | Cycle: 24 Hours
A cross-asset confirmation engine. It requires a specific cascade sequence: Oil moves → Gold follows → Copper follows. If the sequence breaks, the engine retreats.
11. S.E EGP
Status: 🔴 Caution | Cycle: Weekly
A regime-based engine for the managed float of USD/EGP. It classifies policy into three regimes: Quiet Accumulation, Devaluation Surge, and Policy Divergence.
12. T.E Grid
Status: 🟢 Active | Cycle: 5 Min
Mechanical grid trading. It does not predict direction. It places orders above and below price and harvests volatility as BTC oscillates.
13. T.E Momentum
Status: 🔵 Dry Run | Cycle: 2 Hours
Captures confirmed directional moves on BTC/ETH/SOL. Requires EMA structure, RSI momentum, and Volume confirmation simultaneously.
14. T.E Breakout
Status: 🔵 Dry Run | Cycle: 1 Hour
Detects Bollinger Band squeezes (volatility compression) and enters on the subsequent high-volume expansion.
15. T.E LCE
Status: 🔵 Dry Run | Cycle: 5 Min
Liquidation Cascade Engine. Detects forced selling events via liquidation data and enters to ride the immediate continuation. "Other traders' pain is your signal."
16. O.E Observer
The platform's memory. Runs every 15 minutes to snapshot all engine states and market conditions. Builds the dataset that powers the Strategist.
17. O.E Sentinel
The platform's immune system. Detects anomalies — broken correlations, engines stuck in states, policy divergence. Sends alerts but never trades.
18. O.E Strategist
The analytical brain. Scans the Observer's dataset for patterns and generates allocation recommendations. Precursor to the future G.O (Grand Orchestrator).
19. Runtime & Process Management
CCE runs on Node.js v22 within Termux on Android. PM2 manages the `cce-bot` (trading) and `dashboard` (web) processes, ensuring 24/7 uptime and auto-restart.
20. State Machine Design
Every engine is a Finite State Machine (FSM). This ensures deterministic behaviour. Given the same inputs, the engine always makes the same transition. No hidden logic.
21. Data Storage
Uses `sql.js` for pure JavaScript SQLite. Each engine has its own isolated database file, preventing corruption in one engine from affecting others.
22. Dashboard & Interfaces
A local web dashboard (`localhost:3000`) provides real-time state visualization. 'Forge HQ' is the PWA version for mobile home screens.
23. Safety Systems
- Pre-Flight Tests: 31 checks run on every boot. If one fails, the platform will not start.
- Circuit Breakers: Daily loss limits stop an engine from trading if it hits a drawdown threshold.
- Dry Run Default: All engines default to simulation mode. Live trading requires explicit configuration.