Developer guide

Build and ship cTrader platform work without the owner vault, funded terminals, or owner-only guides.

Staff deploy path — demo dry-run first, then pull requests.

You are building

The cTrader platform vehicle for the Portfolio Book: symbols, schedule, sizing, guards, dry-run evidence. Not strategy search. Not MetaTrader. Not funded accounts.

Day-one path (do in order)

Clone the private pack: github.com/FinelyCred/jireh-ctrader-track-a. Ask the owner for invite if you cannot see it.
Read pack docs in this order: What you are building → Day One → MT5 vs cTrader status → Composer operating manual.
Run formula check: python tools/ops/check_ctrader_tickvalue_math.py → expect OK ctrader tickvalue math.
Attach JirehProfits_PortfolioBook on a demo chart: Dry Run = true, Smoke Test On Start = true, Require License = false. Use absolute paths to fixtures/.
Grade the probe. Continue only on PASS_SINGLE_DIGIT_OR_TENS. Stop on FAIL_PER_LOT_SUSPECT.
Open pull requests for platform work. Owner merges into full EAS cTrader.

How to use AI (Composer)

Plan when the change spans files or touches sizing / guards.
Composer for small, checkable edits only.
You re-read every diff and run the listed check. Two failed cheap loops → stop and ping the owner.
Never invent numbers. Never weaken a guard to go faster.

Never touch

Owner guide / owner-engineer workflow docs
Credential vault, prop portals, funded terminals
Production signing keys / live HMAC
Full EAS until Checkpoint 2+

Desk links

Team & training · Staff school · Projects

Jireh Profits

Loading module…