01
Trade lifecycle
The trading system opens, manages, and closes positions according to its own logic and safeguards.
FinSentinal System
The strategy trades.
The system records.
FinSentinal separates trading decisions from public reporting, so the audience can see what happened without changing how the strategy behaves.
01
Strategy engine
Python and MetaTrader 5 evaluate the market and manage XAUUSD trades according to the system's rules.
→
02
Execution events
Relevant trade lifecycle events are captured for monitoring and public reporting.
→
03
Public feed
Signals, outcomes, and reports become part of the Telegram chronology.
→
04
Source context
Myfxbook remains the external source for the broader account history and current account snapshot.
What is automated
Automation reduces selective storytelling.
The more the reporting layer depends on memory and mood, the easier it becomes to post only the convenient moments. Structured event reporting is intended to make the chronology more consistent.
02
Event detection
The monitoring layer can detect order, entry, update, exit, and cancellation events for structured reporting.
03
Recurring context
Weekly and monthly summaries can place individual trades inside a longer performance and drawdown story.
What stays human
Automation reports. Research still requires judgment.
FinSentinal does not treat automation as a substitute for analysis. Major changes, post-mortems, and strategy research should be explained and tested separately.
Post-mortems
When the data reveals a weakness, the analysis should be public enough to show what was found.
Version discipline
Research changes belong in separate testing before they are promoted to a protected running configuration.
Honest labels
Demo, legacy history, current forward record, and future products should remain clearly separated.
SEE THE SYSTEM IN CONTEXT
Follow on Telegram.
The strategy runs. The history remains open. The next chapter is still being written.