Sample audit report

Trend-Following Strategy v1 - BTC Market Index - 1D

A sample validation report built around a BTC trend-following example. Validation status: PASS - recommended next step: Paper-Trading Recommended Before Live Deployment.

Topline read

Fast orientation before the deeper report sections

This top block intentionally combines confidence scoring and the verdict call, so a customer can understand the big picture in one glance before reading details. In this sample, the strategy clears the core validation bar and earns a genuinely encouraging result before the deeper diagnostics begin.

Validation overview
82
Audit score

This format is best used as a fast orientation layer. It helps a customer grasp where confidence is strongest, where caution still matters, and why a strong report can still lead to a paper-trading next recommendation.

Implementation readiness here is strategy-side only. It reflects execution realism, cost tolerance, timing robustness, and current market alignment. It does not assume the customer has already completed their own paper-trading or operator process.

Statistical edge
88%
Walk-forward stability
79%
Parameter robustness
74%
Market-condition survival
83%
Implementation readiness
58%
Verdict
PASS

Strong BTC edge with stable drawdown profile and credible multi-period behavior

PF 3.24 - 134 trades - 18.88% max drawdown. The strategy held up well on a BTC market index on 1D, benefited from the short side, and avoided the most damaging 2022 bear-market exposure in this sample framing. It passed the core validation bar, but the customer-facing recommendation remains paper-trading before any live capital is considered.

Export options available on customer reports

Real customer reports can be delivered in multiple formats for easier handoff, analysis, and integration into other workflows.

HTMLPDFJSONCSV
Why this audit deserves trust
Benchmark-first crypto route
This sample starts on a BTC benchmark because liquid, decision-relevant markets produce a cleaner first read than random altcoin selection.
Authoritative Python engine
The audit numbers come from the shared Python validation engine. TradingView and Pine can support visual verification, but they are not treated as silent source-of-truth replacements.
Multi-layer evidence stack
The report combines walk-forward splits, nearby parameter checks, hostile-window testing, benchmark context, and implementation-aware judgment before confidence is raised.
Decision-first discipline
A PASS still does not automatically become a live recommendation. The report deliberately separates strong evidence from the question of what should happen next.
Audit provenance

The provenance panel makes the report ID, Strategy ID, methodology snapshot, data source, and benchmark route explicit before anyone acts on the verdict.

Report ID
TA-2026-0047
Strategy ID
STRAT-8C31F0A2
Strategy family
Trend Following Strategy
Submitted strategy key
trend_following_strategy_v1
Primary scope
BTC Market Index - 1D
Benchmark route
Benchmark-first crypto
Data source
Python + shared engine feed
Dataset window
2017-08-17 to 2026-04-04
Walk-forward windows
7
Parameter variants
18
Methodology version
2026.04A
Engine version
v3.0 Bundle A
Evidence Completeness

89% evidence completeness. This sample already includes enough direct evidence to support a serious verdict, but it also shows how the report calls out what is still missing instead of pretending every layer is equally well-grounded.

Evidence layer
Status
Why it matters
Level
Primary backtest metrics
Available
Core return, drawdown, profit factor, win rate, and trade count are present for the main verdict layer.
required
Cross-market comparison
Available
The report can compare how the same strategy family behaves across tested markets instead of assuming identical fit.
required
Walk-forward validation
Available
Unseen-window evidence is included, so the report is not relying on one full-period backtest alone.
required
Parameter robustness
Available
Nearby variants were tested to show whether the edge survives reasonable parameter drift.
required
Hostile windows
Available
Named hostile periods were tested, which helps separate a clean bull-market story from actual survival evidence.
required
Cross-timeframe check
Partial
Helpful robustness context exists, but it remains a supporting layer rather than the main decision anchor on 1D systems.
supporting
Implementation layer
Available
The report still separates validation strength from live-readiness and explains why the next move is not automatic.
required
Benchmark context
Available
Rank is grounded in a comparable benchmark pool rather than being shown as a floating number without context.
required
Direct strategy description
Not supplied
Optional customer context that would improve claim-vs-evidence checks, especially for non-trend systems.
optional
Net return
+5674%
Full period
Profit factor
3.24
Threshold: 1.50
Max drawdown
+18.88%
Within limit
Trades
134
Shorts enabled
How to read large returns

Return here is measured relative to starting capital, so it can exceed 100%. A 100% return means capital doubled. A 300% return means it became four times the starting capital.

Decision summary
Current recommendation
Paper-trade next

This means the validation is strong enough to progress, but the next smart step is a structured paper-trading phase instead of moving straight to live capital. The recommendation is about implementation discipline, not about weakness in the historical result.

Immediate next move: Keep the configuration fixed, document every signal, and use the forward observation phase to decide whether the honest next step is live, refine one rule, or stop widening scope.

What This Strategy Is
This example currently behaves as a selective trend-following breakout model, not as an all-weather system that should be expected to stay equally credible across all market conditions.
Where It Fits Best
The strongest fit is in orderly higher-timeframe trend conditions where continuation logic stays clean. It is not framed as a strategy that must stay active in every market phase.
Configuration Choice
One shared profile can still be a reasonable starting point, but we highlight when market-specific profiles would be safer than pretending one setup fits everything with equal credibility.
Why this market
BTC is used here as a benchmark-first starting point
This sample starts on a BTC benchmark because it is one of the most liquid and decision-relevant crypto markets. The point is not to show a random symbol. The point is to show how we begin with a market that improves decision quality first, then widens only if the strategy earns broader validation.
Validation path chosen
Single benchmark first
This sample shows the first validation step on a benchmark market before widening to more assets. The point is to establish whether the strategy has credible edge in a decision-relevant market before claiming broader portability.
Why not live yet
Validation strength and live readiness are different
This example is intentionally framed as paper-trade next because implementation discipline, signal monitoring, and forward confidence still matter even after a strong historical validation pass.
Why this sample matters
Same public-facing strategy framing as the homepage
This sample uses the same generic BTC trend-following framing as the public site, so the story stays consistent from first impression to full report view without exposing internal strategy labels.
Validation is separated from deployment advice
The strategy can receive a PASS verdict without us recommending immediate live deployment. That distinction is deliberate and central to how we position the product.
Strong historical evidence still does not remove process discipline
Even a strong result like this is framed as evidence first, then next-step guidance. The report is built to improve decision quality, not to pressure the customer into going live.
Strategy interpretation
Strategy Behavior
This example strategy currently behaves as a selective trend-following breakout model rather than an all-weather system that should be expected to stay equally credible across all market conditions.
Interpretation Confidence
Medium confidence. This sample uses strategy metadata plus observed behavior evidence. In live customer audits, a short optional strategy description improves confidence, especially for non-trend and non-breakout systems.
Interpretation Basis
The current label should be treated as stronger when a strategy description is supplied. Without that context, the product should stay more provisional and avoid pretending every strategy can be classified tightly from metrics alone.
Cross-Market Fit
One strategy can remain viable across multiple assets without behaving identically on all of them. We highlight those differences so the customer understands where the edge looks strongest and where caution increases.
Configuration Recommendation
When one shared configuration no longer looks like the most honest answer across all tested markets, the report can recommend market-specific profiles instead of pretending one setup fits everything with equal credibility.
Example strategy setup
Benchmark family: Crypto benchmark
Validation path: Single benchmark first
Source: hlc3
Poles: 4
Period: 149
Range Multiplier: 1.414
Reduced Lag: false
Fast Response: false
Enable Shorts: true
Commission: 0.1%
Primary finding

This trend-following channel configuration delivered a strong BTC profile in the sample set. Relative to nearby parameter choices, it produced a cleaner balance of return, drawdown, and trade count, and the short side materially improved the profile instead of adding random noise.

Recommended next step

Paper-Trading Recommended Before Live Deployment. A strong historical validation result still does not mean the safest next move is live capital. For customers who want more confidence before that stage, we may offer a selective follow-up implementation review.

Recommendations & improvement plan
1. Keep improvements structural before you touch raw parameters

The finding: The strategy already shows a credible historical edge. That means the next improvement should target structure, not cosmetic retuning.

The hypothesis: If future weakness appears, it is more likely to come from market-condition filtering or implementation handling than from the exact baseline parameter values.

The proposed change: Add one structural refinement at a time, such as a cleaner market-condition filter or stricter implementation rule, before retuning core settings.

Expected impact: Expected impact: cleaner decision quality, lower overfitting risk, and easier cause-and-effect interpretation after the next audit.

Validation plan: Validation plan: re-audit after one single structural change, then compare walk-forward stability, drawdown behavior, and trade-count retention.

Do not change: Do not change the benchmark market, timeframe, and core baseline at the same time. Keep one clean reference version intact so the next audit can still explain what actually improved.

Risk: Risk: if the new filter is too aggressive, trade count can fall enough that the strategy becomes less useful even if the drawdown headline improves.

2. Do not change what already looks robust

The finding: Nearby parameter choices in this sample still look credible enough that the current baseline should remain your anchor.

The hypothesis: Changing multiple robust settings at once would make it harder to tell whether an improvement came from a real idea or from accidental re-optimization.

The proposed change: Do not retune the full core configuration while also adding new filters or changing exits.

Expected impact: Expected impact: cleaner future learning, easier debugging, and less risk of destroying a good baseline while chasing marginal improvements.

Validation plan: Validation plan: keep the baseline intact during paper-trading and note only where real implementation friction appears.

Do not change: Do not replace the stable entry scaffold while you are still trying to learn whether one new filter or exit idea helped. Protect the anchor version first.

Risk: Risk: over-editing can flatten the original edge and make the next audit much harder to interpret honestly.

3. Use paper-trading as an improvement stage, not a waiting stage

The finding: The next recommendation is not to sit still. It is to gather forward evidence about signal handling, execution discipline, and confidence under live market conditions.

The hypothesis: The most valuable remaining uncertainty is no longer raw backtest quality. It is whether the strategy still feels clean enough when followed bar by bar.

The proposed change: Log entries, exits, odd signals, and any implementation friction while keeping the rules fixed.

Expected impact: Expected impact: faster identification of whether the right next move is go live, refine one rule, or stop widening scope.

Validation plan: Validation plan: review the paper-trading log after a meaningful signal sample or a fixed observation window, then decide whether another audit is warranted.

Do not change: Do not let paper-trading become a hidden re-optimization phase. Keep the rules locked while you collect the forward evidence.

Risk: Risk: if the rules change during forward observation, the paper-trading evidence becomes much less useful.

4. Define the no-go line before any live step

The finding: A strong historical report still needs a clear stop condition, otherwise every next tweak can feel justified indefinitely.

The hypothesis: Without a pre-defined no-go line, it becomes too easy to rationalize weak forward evidence or keep tuning a version that no longer deserves implementation attention.

The proposed change: Decide in advance what would stop progression, such as repeated weak live-signal quality, a sharp robustness drop in the next audit, or failure of the locked paper-trading phase.

Expected impact: Expected impact: better research discipline, faster decision-making, and less risk of confusing persistence with real edge.

Validation plan: Validation plan: treat the paper-trading review as a formal gate, not an open-ended waiting room.

Do not change: Do not move the no-go line after the fact. Decide it before forward observation starts, otherwise the whole gate becomes weaker.

Risk: Risk: if the stop line is vague, the project can drift into endless optimization without improving trust.

Claim vs Observed Behavior
Claimed strategy type
No direct strategy description was supplied in this sample. Without a customer claim, the report can only infer behavior from metrics, validation evidence, and the submitted strategy family.
Observed behavior read
The evidence still reads as a selective trend-following breakout profile with directional exposure concentrated in cleaner continuation phases rather than in every market condition.
Claim vs evidence
Because no explicit claim was supplied here, this section stays provisional. In a real audit, a short strategy description makes it easier to confirm whether the observed behavior matches what the customer thought they built.
Strategy ID & iteration compare

This is the first saved audit under this Strategy ID. Submit a revised version of the same strategy later to see what genuinely improved, what stayed flat, and what got worse.

Field
Previous
Current
Change
Strategy key
No earlier version submitted
trend_following_strategy_v1
Compare unlocks on the next version
Historical verdict
No earlier version submitted
PASS
Compare unlocks on the next version
Current recommendation
No earlier version submitted
Paper-Trading Recommended Before Live Deployment
Compare unlocks on the next version
Primary return
No earlier version submitted
+5674%
Compare unlocks on the next version
Profit factor
No earlier version submitted
3.24
Compare unlocks on the next version
Max drawdown
No earlier version submitted
-18.88%
Compare unlocks on the next version
Walk-forward pass rate
No earlier version submitted
71.4%
Compare unlocks on the next version
Sensitivity pass rate
No earlier version submitted
77.8%
Compare unlocks on the next version
Trades
No earlier version submitted
134
Compare unlocks on the next version
What the next version unlocks
The next audit with the same Strategy ID will compare this baseline against the newer version across verdict, recommendation quality, return, drawdown, walk-forward stability, and sensitivity.
Why this matters
A first audit is useful on its own, but a second version turns the report into a true development tool by showing what actually moved instead of relying on memory or storytelling.
Benchmark Context

The comparable benchmark pool is large enough for this stage that rank is a useful orientation signal. It still does not replace the direct evidence stack in the report.

Benchmark family
Benchmark-first crypto
Comparable benchmark pool
12 strategies
Visible benchmark rows in report
5
Customer rank
2 / 12
Benchmark confidence
High
Strategy
Score
Avg PF
Avg DD
Avg Return
Assets Pass
macro_filter_breakout_v3
91
3.61
-16.20%
+6280%
3 / 3
trend_following_strategy_v1
82
3.24
-18.88%
+5674%
3 / 3
breakout_filter_v2
78
2.87
-21.40%
+4318%
2 / 3
btc_trend_channel_v4
73
2.52
-24.10%
+3527%
2 / 3
adaptive_trend_core_v2
69
2.21
-28.60%
+2874%
2 / 3
Full report includes the full audit stack
Verdict summary - provenance - metrics - walk-forward view - sensitivity analysis - stress tests - implementation framing - iteration compare - written recommendation
View full sample ->
Benchmark-first case
Shows how we start on a liquid benchmark before widening scope.
Decision-first report
Shows what the strategy is, where it fits, and the best next move instead of only metrics.
Shared vs split aware
Shows the kind of interpretation layer that can later justify one shared profile or separate market-specific profiles.

Ready to get a verdict on your own strategy?

Submit your strategy - EUR 99

Delivered within 24 hours - PASS / CAUTION / FAIL