A signal marketplace sounds exciting, but the less glamorous trading journal has to come first.

Without a journal, a signal is just a notification. With a journal, it becomes a record that can be filtered by strategy, symbol, timeframe, side, entry, exit, and lifecycle state.

That record is what makes later marketplace features trustworthy. People need to see the history, not just the pitch.

A signal on its own is too small to trust. It says something happened, but it rarely explains the account state, the intended risk, the stop loss, the take profit plan, the timeframe, or the session.

Quantarya's journal layer gives every signal somewhere to land. The strategy route, external reference, symbol mapping, SL/TP settings, and broker response all become part of the record instead of background noise.

That context is what separates a useful strategy page from a feed of impressive-looking alerts. Users should be able to ask what happened after the signal, not only whether a signal was published.

Quantarya treats a strategy as the core boundary for routing and review.

A strategy can represent one TradingView setup, one execution system, one account family, or one research idea. The exact meaning is flexible, but the boundary should stay clear.

That is why strategy metadata matters: the ID is for machines, while the title, description, tags, image, and organization are for humans trying to understand what they are looking at.

A marketplace will eventually want rankings, filters, and leaderboards. Those numbers are only useful when they are based on complete trade outcomes.

If TP1 is reached and the remaining position later loses money, the trade should not be counted as a clean win. Average profit, average loss, win ratio, and RRR should respect the final result, not the first nice milestone.

That is why lifecycle events, chart context, and broker execution state belong in the journal before they belong in marketing copy.

Manual cleanup can be necessary, but it should not silently rewrite reality.

Quantarya keeps manipulation visible through retained audit rows and warnings when too many recent edits, closes, or deletes happen.

That rule is simple: if a strategy is clean for a while, the warning fades. If it needs constant cleaning, users should know before trusting the numbers.

Once the journal is reliable, the marketplace layer can become more useful. Strategy pages can show results, sessions, symbols, lifecycle quality, missing execution notes, and chart evolution in a way that helps users compare ideas.

That kind of marketplace does not depend on hype. It depends on clean history and honest edge-case handling.

The product direction is simple: build the record first, then build discovery on top of a record that can defend itself.