Publication

Decision Lifecycle

The closed-loop system through which every decision evolves from possibility to outcome to improved future decision.

Paper

WL-DL-001

Version

0.1

Status

Living Document

Last Updated

July 2026

Discipline

Systems Engineering + Process Engineering

Authors

Warren Labs Research

Implementation

Orqis

Citation

WL-2026-DL-01

This is a living research document. Content evolves as our understanding deepens.

Research Status

Theory■■■■■■■■■□
Implementation■■■■■■■■■□
Validation■■■■■■□□□□
Generalization■□□□□□□□□□

Key Contributions

This paper introduces:

  • A 7-stage lifecycle model where the final stage (learning) feeds back into the first (exploration)
  • 10 fully closed feedback loops demonstrating that outcomes systematically improve future generation
  • State machine formalization of stage transitions with explicit promotion and demotion paths
  • Empirical evidence of <1% end-to-end conversion as a feature of selective infrastructure
  • Time asymmetry analysis: seconds to generate, days to qualify, months to execute

Abstract

The Decision Lifecycle describes the stages every important decision passes through — from possibility through execution and learning. Unlike a pipeline, where decisions flow linearly from generation to deployment, the lifecycle is a closed-loop system: every outcome — successful or not — feeds back into improved future decisions. This paper formalizes the lifecycle as seven stages (exploration, evidence, simulation, qualification, allocation, execution, learning), documents the state machine governing transitions between them, and catalogs the 10 fully closed feedback loops that connect execution outcomes to generation parameters. Production data from the Orqis implementation demonstrates that the lifecycle acts as a progressive filter with less than 1% end-to-end conversion, where the cost asymmetry between generation (seconds, $0.05) and qualification (days, evidence-intensive) is an intentional design property.

01

From Pipeline to Cycle

The most common model for decision-making infrastructure is the pipeline: generate, validate, deploy. Information flows in one direction. A candidate enters the system, passes through gates, and either reaches execution or is discarded. The pipeline model is intuitive, easy to build, and fundamentally incomplete.

The incompleteness is not in the forward path — pipelines are perfectly adequate at moving candidates from generation to deployment. The failure is in what happens after deployment. In a pipeline, outcomes are recorded but not routed. The system knows that a strategy succeeded or failed, but that knowledge sits in a database table rather than flowing back into the generation process that produced the strategy in the first place.

A lifecycle differs from a pipeline in one structural property: the final stage connects back to the first. When learning — the seventh stage — feeds its observations back into exploration — the first stage — the system becomes self-improving. Without this closure, you have a record-keeping system that happens to trade. With it, you have infrastructure that gets better at making decisions over time.

Observation

The difference between a pipeline and a lifecycle is not philosophical — it is architectural. A pipeline stores outcomes. A lifecycle routes them. The routing is what creates improvement. In the Orqis implementation, the weekly learning summary aggregates backtest patterns, paper trading outcomes, exit attribution, and regime transition data into a structured prompt that directly shapes the next generation cycle.

A pipeline records results. A lifecycle routes them back to the decisions that produced them.

Core Thesis

Every outcome — successful or not — should systematically improve the next decision.

The lifecycle is not a better pipeline. It is a different category of infrastructure — one where the system’s outputs become its inputs, and where elapsed time is the primary mechanism for accumulating the evidence that separates good decisions from bad ones.

02

The Seven Stages

The lifecycle operates through seven stages, each with a distinct purpose, timescale, and set of outputs. The stages are not arbitrary divisions — they reflect the fundamental activities required to move from “this might work” to “this is working” to “here is what we learned.”

Exploration is where candidates are born. The foundry runs three sweeps per day, each producing approximately 20 candidates through a combination of deterministic templates and AI generation. Exploration is deliberately cheap — approximately $0.05 per candidate — because the system’s selective power comes from later stages, not from restricting generation. Coverage-aware budget allocation boosts under-served regimes, and a 20% exploration budget ensures that the system does not converge prematurely on known-good patterns.

Evidence is the first quantitative gate. Each candidate undergoes vectorbt backtesting with a 70/30 in-sample/out-of-sample split, composite scoring with fee-efficiency adjustment, and robustness labeling. A validation run takes 30 to 120 seconds. Approximately 31% of generated candidates pass this stage — the first major reduction in the lifecycle funnel.

Simulation is where time becomes the evidence mechanism. Approved candidates enter paper trading at a 1-minute tick cadence with full exit profile evaluation (ATR-based breakeven, trailing stops, partial take profit). The minimum observation period is seven days with at least five closed trades. Paper trading never auto-pauses — by design, the system needs to observe how strategies behave in all conditions, including unfavorable ones.

Qualification is the 14-criteria evaluator that runs every six hours. It assesses outcome metrics (win rate, ROI, drawdown), process metrics (observation duration, trade count, fee viability), and regime-specific proof. The gate is fail-closed: if evidence is uncertain, the strategy is blocked. Only 22.2% of paper-traded strategies achieve qualification.

Allocation is advisory, not prescriptive. A 6-component intelligence score ranks qualified strategies by deployment attractiveness, considering equity-curve Sharpe, regime fit, correlation diversity, and behavioral stability. Allocation does not gate deployment — it informs the decision about which qualified strategies deserve capital first.

Execution is the narrowest point in the funnel. Live trading operates on Hyperliquid through a 5-layer gate architecture with regime gate persistence, qualified scout synchronization, and reconciliation heartbeats. Positions are managed at 1-minute tick cadence with the same deterministic exit evaluation as paper trading. Only 5.1% of qualified strategies are promoted to live capital.

Learning is the stage that transforms the lifecycle from a pipeline into a cycle. Six deployed learning phases continuously capture observations: exit attribution, regime transition survivability, fee-bleeder detection, indicator effectiveness, divergence prediction, and strategy correlation. The weekly learning summary synthesizes these into structured guidance that is injected directly into the next generation prompt — closing the loop.

Verified Evidence — Production

Seven stages fully implemented

Every stage of the Decision Lifecycle is implemented and operational in the Orqis production system. The lifecycle is not theoretical — it processes strategies continuously through generation, validation, simulation, qualification, allocation, execution, and learning.

  • Exploration: foundry sweeps 3x/day generating ~20 candidates each, deterministic + AI generation
  • Evidence: vectorbt backtest engine, 70/30 IS/OOS split, composite scoring, 30-120s per validation
  • Simulation: paper trading at 1-minute tick cadence, exit profiles V2 (ATR-based), partial TP
  • Qualification: 14-criteria evaluator running every 6 hours, fail-closed promotion gate
  • Allocation: 6-component intelligence scoring, confidence-adjusted, advisory ranking
  • Execution: live trading on Hyperliquid, 5-layer gate architecture, regime gate persistence
  • Learning: 6 deployed phases, 10 fully closed feedback loops, weekly learning summary injection

Production observed

System Architecture·Pending reviewExecution Engine Specification·Pending reviewLearning Loop Implementation·VerifiedQualification Evaluator·Verified

Verified Evidence — Production

Time in each stage

The lifecycle stages operate at radically different timescales — from seconds (generation) to months (execution). This asymmetry is intentional: exploration should be fast and cheap, while qualification and execution should be slow and evidence-rich.

  • Exploration: 1-5 minutes per candidate ($0.05 cost)
  • Validation: 30-120 seconds (synchronous backtest)
  • Simulation: ≥ 7 days minimum (paper trading requirement for qualification)
  • Qualification: computed every 6 hours (batch), checked every 1 minute (execution tick)
  • Allocation: computed every 6 hours (advisory, not blocking)
  • Execution: 1-minute tick cadence, positions held minutes to months
  • Learning: continuous (6h evaluation batch) with weekly synthesis (Monday 4am UTC)

Production observed

Execution Engine Specification·Pending reviewQualification Evaluator·VerifiedLearning Loop Implementation·Verified

Engineering Note

The time asymmetry across stages is intentional. Exploration operates in seconds because cheap generation creates option value. Simulation operates in days because time is the only mechanism that reveals behavioral stability. The system is designed so that the most expensive resource — elapsed time — is spent only on candidates that have already passed cheaper filters.

03

Stage Transitions

The lifecycle is formalized as a state machine with explicit promotion and demotion paths. Each transition requires specific evidence, and the system enforces that evidence programmatically rather than through human review.

The primary forward path is: draftvalidated approvedactive (paper trading) → paused promoted (live). Each arrow represents a gate with specific criteria. The draft-to-validated transition requires a passing backtest. The approved-to-active transition requires portfolio admission. The active-to-promoted transition requires 14-criteria qualification plus user intent.

Demotion paths are equally important. A qualified strategy can be degraded if paper trading performance deteriorates. A live strategy can be killed — closing exchange positions and revoking wallet access — if the kill switch is activated. A foundry strategy can be retired if ROI falls below -5% after 14 days. These demotion paths ensure that qualification is not permanent: the system continuously re-evaluates and revokes permission when evidence degrades.

One transition is notably absent: paper trading never pauses automatically for performance reasons. This is a deliberate design decision. The system needs to observe strategy behavior in unfavorable conditions — a strategy that is paused during drawdowns produces biased evidence. The only automatic pause in paper trading is the regime gate: strategies are paused when the market enters a regime where they have no proof of viability, and resumed when a favorable regime returns.

Paper trading never pauses for performance. The system needs to see how strategies behave when conditions are unfavorable — not just when they are good.

Engineering Note

The state machine includes a library_standby state for strategies that have demonstrated regime-specific edge but are not viable in the current regime. These strategies are shelved with their favorable regimes recorded, and the daily lifecycle evaluator activates them when any favorable regime arrives. This prevents the system from permanently discarding strategies that may be valuable under different market conditions.

04

The Feedback Architecture

The feedback architecture is the most important structural property of the lifecycle — it is what distinguishes a cycle from a pipeline. Ten feedback loops are fully closed in the production system, meaning that observations from later stages directly and measurably alter behavior in earlier stages.

The most significant loop is the weekly learning summary. Every Monday at 4am UTC, the system aggregates backtest patterns, paper trading outcomes, exit attribution data, regime transition matrices, fee-bleeder rates per family and timeframe, and the top 10 qualified paper performers with their specific indicator patterns. This synthesis is injected directly into the AI generation prompt, so that the next generation cycle is informed by the accumulated evidence of every previous cycle.

Other loops operate at different cadences and granularities. The exit profile advisor adjusts exit mechanism rotation based on per-family exit attribution data — if a particular exit profile consistently underperforms for momentum strategies, the generator rotates away from it. Fit scores from paper trading feed into the search orchestrator, boosting families that have demonstrated strong performance patterns. Regime classification feeds directly into family filtering, excluding families that are inappropriate for current market conditions.

The annotation-driven loops are particularly illustrative. When the 6-hour evaluation batch detects HIGH severity degradation or overfitting, two things happen simultaneously: the strategy is paused for allocation purposes, and an inverse strategy is automatically generated — the same structure with flipped direction and operators. This is a concrete example of a failure being routed into a new exploration rather than simply recorded.

Not all loops are equally mature. Four additional loops are partially closed — data flows downstream but with limited measurable impact. Four more are open: data is collected and stored but no downstream system consumes it yet. The M2 regime transition model, the M6 anomaly detector, strategy DNA fingerprinting, and behavioral intelligence as a standalone signal are all in this category. The feedback architecture is a living system with gaps — but the gaps are known and tracked.

Verified Evidence — Production

10 fully closed feedback loops

The lifecycle is not a pipeline — it is a closed-loop system. Every stage captures observations that feed back into future stages. 10 feedback loops are fully closed and actively improving system behavior.

  • Learning summary → AI generation prompt (weekly injection of backtest patterns + paper outcomes)
  • Exit profile advisor → template generation (exit mechanism rotation based on attribution data)
  • Fit scores → search boost (family weighting from paper performance data)
  • Regime → family filtering (real-time exclusion of regime-inappropriate families)
  • Annotations → auto-pause (HIGH severity triggers allocation pause)
  • Annotations → inverse mining (degradation triggers automatic inverse strategy generation)
  • Family effectiveness → foundry sweep budget (proven families get more exploration budget)
  • Regime coverage → foundry budget (under-served regimes get boosted allocation)
  • Asset/family scores → deprioritization (negative combos moved to end of generation priority)
  • M5 correlation → allocation (diversity scoring penalizes correlated strategies)

Production observed

Learning Loop Implementation·VerifiedIntelligence & Learning Loop Audit·VerifiedOutcome Attribution Design·Verified

The system does not just record that a strategy failed. It routes the failure into improved generation, adjusted parameters, and inverse exploration.

Observation

The asset/family deprioritization loop demonstrates graduated learning. Combos are classified into four tiers: preferred (paper confirms backtest), neutral (insufficient data), caution (negative overall but has regime edge), and avoid (negative in all regimes). The system does not binary-reject poor performers — it recognizes that a combo negative overall may still have conditional value in specific regimes.

05

The Funnel

The lifecycle, viewed end-to-end, forms a funnel with severe attrition. Less than 1% of generated strategies survive to live deployment. This conversion rate is not a bug to be optimized — it is a feature of a system that takes the cost of unqualified execution seriously.

The funnel’s shape reveals the relative selectivity of each stage. Validation passes approximately 31% of candidates — the broadest gate, designed to filter out structurally unsound strategies quickly. Qualification passes 22.2% of paper-traded strategies — a narrower gate that requires sustained evidence. Live promotion selects only 5.1% of qualified strategies — the most selective gate, reflecting the gap between “this strategy has earned the right to execute” and “this strategy deserves real capital now.”

The time asymmetry across the funnel is equally revealing. Generating a candidate takes 1 to 5 minutes and costs approximately $0.05. Qualifying it requires a minimum of seven days of paper trading with at least five closed trades. Executing it involves positions held for minutes to months. The system is designed so that the cheapest operation (generation) produces the most candidates, while the most expensive operation (live execution) receives the fewest — each one backed by accumulated evidence from every preceding stage.

Verified Evidence — Production

Lifecycle funnel conversion

The lifecycle acts as a progressive filter. Each stage removes candidates that lack sufficient evidence. Less than 1% of generated strategies survive to live deployment.

  • Generation → Validation: ~31% pass rate (1,158 of 3,743)
  • Validation → Paper trading: approved candidates enter simulation
  • Paper trading → Qualification: 22.2% (59 of 266 eligible)
  • Qualification → Live deployment: 5.1% (3 of 59 qualified)
  • End-to-end: <1% of generated strategies reach live capital

Production observed

Qualification Proof System (live)·VerifiedStrategy Intelligence Layer·Verified

Less than 1% of generated strategies reach live capital. The funnel is not a bottleneck — it is the mechanism that separates evidence-backed decisions from speculation.

Limitations

Limitations

  • The 7-stage model is implemented for capital allocation. Whether the same stages generalize to other domains (drug development, software deployment, resource allocation) is proposed but unproven.
  • 4 feedback loops remain open — data is collected but no downstream system consumes it (M2 regime transitions, M6 anomaly detector, strategy DNA, behavioral intelligence as standalone).
  • The learning loop's direct impact on generation quality is inconclusive (insufficient post-learning sample). Indirect evidence is directionally supportive but confounded.
  • Deployment context snapshots — which would capture the full state at each stage transition — are typed but not yet implemented.
  • The lifecycle operates sequentially. Whether parallel qualification paths (testing a strategy in multiple regimes simultaneously) would improve throughput is unexplored.

References

Research — Warren Labs | Orqis