Observation-First Intelligence
Our Method
The V2 intelligence pipeline: how we observe, fuse, and report - with constitutional honesty.
Intelligence, Not Signals
Most crypto platforms lead with signals: buy this, sell that. We don't. Our product is intelligence - the understanding of what's happening on-chain and in the market, fused from multiple independent engines.
A signal is a single output. Intelligence is the process that produces it, with full provenance, evidence, and constitutional guardrails. When we say a token is in ACCUMULATION state, we can show you exactly which engines contributed, what their source mode was, and what evidence they found.
That's the product. Not “buy SOL at $180.”
Pipeline Architecture
The 8-Gate Pipeline
Data flows through eight gates from ingestion to observation. Each gate adds processing, validation, or enforcement.
Developer Engine
Monitors developer activity, code commits, wallet behaviour, and team transparency. Healthy development is a positive signal; abandoned or suspicious activity is flagged.
Liquidity Engine
Evaluates liquidity depth, pool composition, and slippage characteristics. Low liquidity is a risk factor; deep, healthy pools support stability assessments.
Smart Money Engine
Tracks known smart money wallets, accumulation patterns, and distribution events. Identifies when informed capital is entering or exiting positions.
Market Structure Engine
Analyses price action, volume profile, support/resistance levels, and market regime. Determines whether the market structure supports or contradicts other engine findings.
Timing Engine
Evaluates whether current conditions are favourable for observation. Considers momentum, time-of-day patterns, and recent volatility to assess timing quality.
Safety Engine
Hard safety checks: rug-pull indicators, contract risks, team red flags, and liquidity manipulation detection. A safety veto overrides all other engines - AVOID means avoid.
Evidence Fusion
Resolves all engine outputs into a single intelligence state. Conflicting evidence is surfaced honestly - CONFLICTED is shown rather than pretending clarity that doesn't exist.
Constitutional Review
Enforces the honesty rules: UNKNOWN over fabrication, transparent source modes, no unvalidated claims, no BUY/SELL language. The constitution is the final gate before observations reach you.
Evidence Resolution
Confidence & Evidence Fusion
When engines disagree, the fusion layer doesn't average or hide the conflict. Instead:
Conflicting evidence
CONFLICTED
with the specific conflicts displayed
Insufficient evidence
INSUFFICIENT_EVIDENCE
not a guess
Safety veto
AVOID
regardless of what other engines say
Unknown data
UNKNOWN
not fabricated
The constitutional rules that govern this process:
UNKNOWN over fabrication
If we don't have data, we say UNKNOWN. Never make up numbers.
Transparent source modes
Every piece of data is tagged LIVE/MOCK/DEGRADED/UNKNOWN. MOCK is never hidden.
No unvalidated claims
Performance metrics shown only as "projected" or "backtested," never as verified outcomes.
No BUY/SELL language
Observations describe states, not actions. ACCUMULATION ≠ "buy now."
Full provenance
Every observation shows which engines contributed, their source mode, and their evidence.
Data Provenance
Source Mode Transparency
Every engine in the pipeline tags its output with a source mode. This tells you where the data came from:
Real data from real providers. Production-grade intelligence.
Synthetic data. Used for testing and development. Never presented as live intelligence.
Partially live. Some engines running on fallback data. Less reliable than LIVE.
Source mode cannot be determined. Treated as unreliable until confirmed.
Currently, the V2 Lab runs primarily in MOCK mode as we validate the pipeline. This is clearly labelled throughout the interface and will never be disguised as LIVE data.
Transparency
What We Show vs. What We Don't
✓ We Show
- Intelligence states (OBSERVING, ACCUMULATION, etc.)
- Source mode (LIVE, MOCK, DEGRADED, UNKNOWN)
- Which engines contributed evidence
- Constitutional verdicts (AVOID, OBSERVE, MONITOR)
- Conflicting evidence explicitly labelled
- Backtested performance as “backtested”
✗ We Don't Show
- Buy or sell recommendations
- Entry/exit zones or price targets
- Win rates as validated outcomes
- MOCK data disguised as LIVE
- Guaranteed returns or profit promises
- Anything we can't trace to evidence
Methodology
How Metrics Are Calculated
Every metric on FlowForge is calculated from verified observation data, not trade results. Here is exactly how:
How Observation Accuracy is calculated
3 steps
How Expectancy is calculated
3 steps
How Profit Factor is calculated
3 steps
FlowForge provides observational intelligence for educational purposes. Trading cryptocurrencies involves substantial risk.Read disclaimer →