Flow Archive
Historical snapshots of corporate flow states.
LRAC V3.2 Forward Checkpoint — July +5.04% Realization and August Expansion Signal
Flow Observatory completed a new LRAC V3.2 live research checkpoint at the beginning of September 2026. The July 2026 signal completed its August realization cycle with a +5.04% official portfolio return, while the newly calculated August 2026 state remained in expansion and produced another full-mode, beta-neutral 2L/2S signal.
2026-07 — Expansion Regime Confirmed
Lambda-C was recalculated for July 2026 and the market environment remained classified as expansion.
Target month: 2026-07
Regime: expansion
LRAC V3.2 reproduced the same previously frozen July portfolio without changing its selection, weights, exposure limits or portfolio structure.
Mode: full
Gross target: 1.5
Long ETFs:
XLF
XLV
Short ETFs:
XLU
XLC
Requested shape: 2L/2S
Effective shape: 2L/2S
Zero-weight ETFs: none
Frozen July Portfolio
XLF +0.1975430962
XLV +0.5524569038
XLU -0.5524569038
XLC -0.1975430962
The portfolio remained structurally clean:
Beta exposure: 0.000000
Dollar exposure: approximately 0.000000
Realized gross: 1.5
The requested 2L/2S structure and the effective 2L/2S structure were identical, with no solver-selected ETF collapsing to an effectively zero weight.
2026-07 → 2026-08 — Official Realized Performance
August 2026 had now fully closed, allowing the V3.2 tracker to calculate the official realized result of the July signal.
Signal month: 2026-07
Realized month: 2026-08
Mode: full
Effective shape: 2L/2S
Portfolio return: +5.04%
Previous capital: 97.60
Capital: 102.51
Drawdown: 0.00%
Beta exposure: 0.000000
Dollar exposure: approximately 0.000000
Realized gross: 1.5
The +5.04% result moved the V3.2 live equity record above its initial 100.00 reference level and established a new recorded capital high of 102.51.
Why This Observation Matters
The July result is particularly important from a research-methodology perspective because the portfolio had already been generated and frozen before its August realized performance was known.
At the previous checkpoint, the exact same July signal existed with its 2L/2S structure, gross exposure and weights fixed, while the tracker explicitly refused to calculate performance because August had not yet closed.
The September checkpoint therefore records a forward realized observation rather than a portfolio reconstructed after seeing the subsequent return.
A frozen V3.2 full-mode sector-flow signal produced a +5.04% realized return while maintaining approximately zero beta exposure and zero dollar exposure.
This is supportive forward evidence for the LRAC sector-flow hypothesis, but it is not sufficient on its own to establish persistent alpha or prove the strategy.
Current V3.2 Live Sequence
2026-03 → 2026-04
Accepted · Reduced Mode
Return: -0.60%
2026-04 → 2026-05
Accepted · Full Mode
Return: -1.52%
2026-05 → 2026-06
Accepted · Full Mode
Return: +0.62%
2026-06
Rejected
Reason: beta_exposure_breach
Official traded return: none
2026-07 → 2026-08
Accepted · Full Mode
Regime: expansion
Return: +5.04%
Current recorded capital:
102.51
2026-08 — Expansion Persists
Lambda-C was then calculated for August 2026. The market remained in the expansion regime for a second consecutive monthly signal cycle.
Target month: 2026-08
Regime: expansion
Under the unchanged V3.2 architecture, the engine again accepted a full-mode portfolio with the expansion gross target of 1.5.
Mode: full
Gross target: 1.5
Long ETFs:
XLV
XLE
Short ETFs:
XLU
XLY
Requested shape: 2L/2S
Effective shape: 2L/2S
Zero-weight ETFs: none
August Portfolio Weights
XLV +0.6058308554
XLE +0.1441691446
XLU -0.1441691924
XLY -0.6058308076
Exposure controls remained intact:
Beta exposure: approximately 0.000000
Dollar exposure: 0.000000
Realized gross: 1.5
The portfolio again retained all four effective positions, with requested and effective portfolio shapes remaining identical.
August Performance Remains Pending
The August 2026 signal will be evaluated using September 2026 realized monthly returns. At the time of this checkpoint, September had only just begun.
The V3.2 tracker therefore correctly refused to produce an official performance record.
Signal month: 2026-08
Realized month: 2026-09
Status:
MONTH NOT CLOSED
Official performance:
SKIPPED
The official 2026-08 → 2026-09 realized result can only be evaluated after September has fully closed.
Research Interpretation
This checkpoint adds an important forward observation to the Flow Observatory evidence record.
The July portfolio was generated before its realized result was available, remained unchanged through the observation period and subsequently produced a +5.04% return. At the same time, the portfolio maintained the beta-neutral and dollar-neutral structure required by the V3.2 mandate.
The result should therefore be treated as meaningful supportive evidence, but not as proof of a stable or persistent return advantage. The live sample remains small and future observations may differ materially.
Equally important, no V3.2 parameter was changed in response to the positive July result. Lambda-C weights, quality filters, beta limits, gross targets and portfolio-construction rules remain frozen.
The purpose of the live phase is not to optimize after every result. It is to observe how an unchanged decision architecture behaves through different market states.
Next Checkpoint
The August signal will remain frozen throughout September. No rule or parameter adjustment will be made based on the July +5.04% result.
After September 2026 fully closes, the next Flow Observatory checkpoint will:
- calculate the official 2026-08 → 2026-09 realized V3.2 performance,
- recalculate Lambda-C for September 2026,
- determine whether the expansion regime persists or changes,
- generate the next V3.2 signal using the unchanged engine,
- continue accumulating forward evidence without hindsight-driven parameter modification.
LRAC V3.2 Live Checkpoint — June Rejection Closure and July Expansion Signal
On August 5, 2026, Flow Observatory completed the next monthly LRAC V3.2 live research checkpoint. The session formally closed the June 2026 rejected-signal cycle and generated a new full-mode signal for July 2026 under an expansion regime.
2026-06 — Rejected Signal Cycle Closed
Lambda-C was recalculated for June 2026 and the market regime remained classified as transition.
Target month: 2026-06
Regime: transition
LRAC V3.2 then evaluated the June portfolio candidate using the current production research engine:
z_etf/10_lrac_live_engine_etf_v32_FIXED.py
The candidate failed the V3.2 beta-exposure mandate:
Mode attempted: full
Gross target: 0.8
Beta exposure: -0.106604
Beta exposure limit: ±0.10
Dollar exposure: approximately 0.00
Realized gross: 0.8
Decision: REJECTED
Reason: beta_exposure_breach
The rejection was therefore confirmed as an intentional risk-control decision. The portfolio exceeded the permitted beta boundary and was not admitted into the official traded-performance record.
June Tracker Audit
With July 2026 now closed, the V3.2 tracker was able to complete its audit of the June signal cycle.
Signal month: 2026-06
Rejected signal detected: yes
Reason: beta_exposure_breach
Official performance: SKIPPED
Audit status: WRITTEN
Audit reason:
rejected_signal_exists:beta_exposure_breach
Because the June signal had already been rejected before entering the market, no realized portfolio return was calculated for the June → July period.
This is an important distinction in the V3.2 research record: the absence of an official return is not missing data and is not a failed performance calculation. It is the direct consequence of the engine's risk mandate preventing the trade.
2026-07 — Regime Shift to Expansion
The July 2026 Lambda-C calculation produced a meaningful regime change.
Previous regime: transition
July 2026 regime: expansion
Under the V3.2 architecture, expansion permits a higher full-mode gross target. The engine successfully constructed and accepted a complete 2-long / 2-short portfolio.
Target month: 2026-07
Regime: expansion
Mode: full
Gross target: 1.5
Long ETFs:
XLF
XLV
Short ETFs:
XLU
XLC
Requested shape: 2L/2S
Effective shape: 2L/2S
Zero-weight ETFs: none
July Portfolio Weights
XLF +0.1975430962
XLV +0.5524569038
XLU -0.5524569038
XLC -0.1975430962
The resulting exposure audit was structurally clean:
Beta exposure: 0.000000
Dollar exposure: approximately 0.000000
Realized gross: 1.5
Requested shape: 2L/2S
Effective shape: 2L/2S
Unlike some earlier reduced-mode observations, no selected ETF collapsed to an effectively zero weight. The requested and effective portfolio structures were therefore identical.
July Performance Is Not Yet Known
The July signal will be evaluated using August 2026 realized monthly returns. Because August had not closed at the time of this checkpoint, the V3.2 tracker correctly refused to calculate official performance.
Signal month: 2026-07
Realized month: 2026-08
Status:
MONTH NOT CLOSED
Official performance:
SKIPPED
The official July-signal performance review can therefore occur only after August 2026 has fully closed, beginning in September 2026.
Current LRAC V3.2 Live Sequence
2026-03
Accepted · Reduced Mode
Realized return: -0.60%
2026-04
Accepted · Full Mode
Realized return: -1.52%
2026-05
Accepted · Full Mode
Realized return: +0.62%
2026-06
Rejected
Reason: beta_exposure_breach
Official traded return: none
2026-07
Accepted · Full Mode
Regime: expansion
Gross: 1.5
Realized result: pending August close
Operational Validation
The August 5 checkpoint also provides an important operational confirmation for the V3.2 engine.
The fixed live engine has now successfully passed both principal decision paths:
- Rejected path: June 2026 was rejected for a beta exposure breach and the rejection was successfully persisted and audited.
- Accepted path: July 2026 produced a valid full-mode 2L/2S portfolio with zero measured beta exposure and the intended expansion gross target.
This confirms that the July 4 rejected-signal writer correction did not alter the accepted-signal construction logic and that both branches of the V3.2 live workflow are functioning within the current research architecture.
Research Interpretation
The August 5 checkpoint should not be interpreted as new evidence of investment alpha. The July signal has not yet produced an observable realized result.
Its importance is instead architectural and evidential.
June demonstrated that V3.2 can refuse exposure when its beta mandate is violated. July demonstrated that the same frozen engine can subsequently move into an expansion regime, accept a complete portfolio, and increase gross exposure according to its predefined regime rules.
The value of this checkpoint is not that the engine traded more. It is that the same fixed decision architecture was able to say “no” in June and “yes” in July for independently determined structural reasons.
Next Checkpoint
No V3.2 parameters will be modified as a result of this observation.
The July 2026 signal will remain frozen and will be evaluated only after August has fully closed. The next monthly research checkpoint will therefore:
- close the 2026-07 → 2026-08 realized performance cycle,
- recalculate Lambda-C for August 2026,
- determine the August market regime,
- generate the next V3.2 signal using the unchanged engine,
- continue accumulating forward live evidence without hindsight parameter adjustment.
LRAC V3.2 Live Validation Update — May Closure, June Risk Rejection and Engine Audit Fix
On July 4, 2026, Flow Observatory completed a new live validation checkpoint for the LRAC V3.2 sector-flow research engine. The session confirmed the realized result for the May 2026 signal cycle, established the June 2026 beta-risk rejection, and corrected a rejected-signal audit bug in the V3.2 live engine.
2026-05 Signal Cycle — Official Realized Result
The May 2026 LRAC V3.2 signal was accepted in full mode under a transition regime. The portfolio structure was:
Mode: full
Regime: transition
Gross target: 0.8
Long:
XLY
XLF
Short:
XLU
XLP
Requested shape: 2L/2S
Effective shape: 2L/2S
Beta exposure: approximately 0.00
Dollar exposure: approximately 0.00
Realized gross: 0.8
The following realized month, June 2026, closed with an official LRAC V3.2 portfolio return of:
2026-05 → 2026-06
Portfolio return: +0.62%
Previous capital: 97.89
Capital: 98.49
Drawdown: 1.51%
This result became part of the official V3.2 live performance record.
2026-06 Signal Cycle — Beta Guard Rejection
The June 2026 V3.2 signal generation process produced a full-mode candidate under a transition regime. However, the resulting portfolio exceeded the defined beta exposure mandate.
Target month: 2026-06
Mode attempted: full
Reason: beta_exposure_breach
Beta exposure: -0.106604
Beta exposure limit: ±0.10
Dollar exposure: approximately 0.00
Realized gross: 0.8
Decision: REJECTED
The rejection is considered an intended risk-control outcome rather than a failed signal-generation event. V3.2 correctly prevented a portfolio from entering the official live track record after the beta mandate was breached.
Rejected-Signal Writer Bug Fix
During the first June 2026 V3.2 run, the engine encountered an audit-layer error while attempting to write a rejected signal.
NameError: shape_audit is not defined
The issue was isolated to the rejected-signal writer. The portfolio decision logic itself had already identified the beta exposure breach correctly, but the audit writer failed while recording the rejected result.
The fix introduced:
- a safe optional
shape_auditargument, - a fallback shape-audit structure for rejected signals,
- safe requested-long and requested-short fallback fields,
- stable rejected-signal persistence without affecting accepted-signal generation.
After the fix, both validation paths were retested:
2026-05
Status: ACCEPTED
Mode: full
Result: unchanged
2026-06
Status: REJECTED
Reason: beta_exposure_breach
Result: correctly written
Operational File Decision
From this checkpoint onward, the primary LRAC V3.2 live engine file will be:
z_etf/10_lrac_live_engine_etf_v32_FIXED.py
The earlier file:
z_etf/10_lrac_live_engine_etf_v32.py
will remain preserved as the previous engine version for research-history and audit purposes.
Live Tracking Timing
Flow Observatory continues to separate signal generation from realized performance measurement. A signal month is evaluated using the following month's completed market data.
Signal month: 2026-06
Realized month: 2026-07
Official evaluation timing:
after July 2026 has fully closed
Therefore, the next clean review of the June 2026 signal cycle will occur in August 2026, after the July monthly data are complete.
Since the June 2026 V3.2 signal was already rejected by the beta guard, the August review will primarily serve as a clean tracker and audit checkpoint rather than an official traded-return update.
Current V3.2 Live Record
2026-03 → 2026-04
Mode: reduced
Status: accepted
Return: -0.60%
2026-04 → 2026-05
Mode: full
Status: accepted
Return: -1.52%
2026-05 → 2026-06
Mode: full
Status: accepted
Return: +0.62%
2026-06
Mode attempted: full
Status: rejected
Reason: beta_exposure_breach
Research Interpretation
The July 4, 2026 checkpoint strengthens the Flow Observatory research architecture in three ways.
First, V3.2 demonstrated that its live performance pipeline can close accepted signals and record realized returns consistently.
Second, the June 2026 rejection confirmed that the beta guard remains active and can prevent structurally undesirable exposure from entering the official track record.
Third, the rejected-signal audit bug was corrected without changing the accepted-signal logic or the V3.2 portfolio construction rules.
The July 4, 2026 checkpoint did not introduce a new strategy. It strengthened the reliability, auditability and operational discipline of the existing LRAC V3.2 research engine.
LRAC V3.2 Reduced Mode — Research Validation Memo
Flow Observatory / Lambda-C Sector Flow Engine
Date: May 2026
Version: Research Memo v1.0
1. Executive Summary
Flow Observatory’s ETF-based LRAC engine evolved from V3.1R Momentum Quality into V3.2 Reduced Mode after validation showed that the V3.1R system was disciplined but overly selective.
The main weakness of V3.1R was not the beta guard or the exposure mandate.
Those controls worked well. The key issue was the
not_enough_filtered_sectors rejection rule. In several months,
V3.1R rejected signals because it could not form a full 2-long / 2-short
structure, even though the underlying sector-flow information still
contained usable relative strength.
V3.2 addresses this by introducing a reduced-gross, reduced-shape mode. When a full 2L/2S signal is unavailable, V3.2 attempts smaller structures such as 1L/1S, 1L/2S, or 2L/1S, while preserving the same beta, dollar, and gross exposure discipline.
In the 2023-01 → 2026-04 validation window, V3.2 improved total return, Sharpe, acceptance coverage, and random benchmark percentile, while only slightly increasing max drawdown.
2. Background: From V3.1R to V3.2
V3.1R introduced three important improvements over the earlier LRAC engine:
-
Momentum Quality Filter
Long candidates needed positive rolling momentum and acceptable current-return range. Short candidates needed negative rolling momentum and acceptable current-return range. -
Mandate Guards
Signals were rejected if they breached beta exposure limit, dollar exposure limit, or gross exposure tolerance. -
Rejected Signal Audit
Invalid or unsafe signals were written separately instead of contaminating official performance records.
This made V3.1R safer and cleaner. However, validation revealed that the system often refused to trade not because the signal was dangerous, but because it could not form a full symmetric 2L/2S portfolio.
3. V3.1R Validation Result
Initial V3.1R validation over the 2023-01 → 2026-04 window produced the following results:
| Metric | V3.1R |
|---|---|
| Tested months | 40 |
| Accepted months | 18 |
| Rejected / invalid months | 22 |
| Rejection rate | 55.00% |
| Total return | +1.25% |
| Max drawdown | 4.05% |
| Hit rate | 44.44% |
| Annualized Sharpe | 0.1454 |
| Avg abs beta exposure | 0.0070 |
| Avg abs dollar exposure | 0.0000 |
V3.1R was therefore highly disciplined, but conservative.
The rejection reasons were:
| Rejection Reason | Count |
|---|---|
not_enough_filtered_sectors |
17 |
beta_exposure_breach |
5 |
This indicated that most rejected months were not rejected because of beta exposure breach, but because the system could not form a full 2L/2S structure.
4. Shadow Audit: Were Rejected Months Actually Dangerous?
A shadow audit was performed to test what would have happened if rejected months had been force-traded.
| Shadow Test | Return |
|---|---|
| Force-equal all-month return | +20.21% |
| Force-solver all-month return | +6.41% |
| Force-equal rejected-only return | +18.72% |
| Force-solver rejected-only return | +5.09% |
This suggested that rejected months still contained useful sector-flow information. However, raw returns alone were not enough. Some of this performance could have come from market beta.
5. Beta-Adjusted Shadow Audit
To isolate whether the rejected-month performance came from genuine sector-flow information or from market exposure, beta-adjusted shadow returns were calculated:
The key result:
| Rejection Reason | Months | Solver Return | Solver Beta-Adjusted Return | Solver Beta |
|---|---|---|---|---|
not_enough_filtered_sectors |
17 | +8.84% | +8.17% | 0.1970 |
beta_exposure_breach |
5 | -3.45% | -1.94% | 0.8469 |
This was the decisive finding. The beta_exposure_breach
rejection appeared justified. These months had high beta exposure and
negative solver performance.
But the not_enough_filtered_sectors rejection looked too strict.
Even after beta adjustment, the rejected months remained strongly positive.
This indicated that V3.1R was likely missing valid sector-flow opportunities.
6. V3.2 Design Decision
V3.2 was created to solve this specific problem.
The goal was not to weaken the risk controls. The goal was to preserve V3.1R’s discipline while allowing the system to express weaker but still valid sector-flow structures.
V3.2 Rule
If full 2L/2S mode is available:
If full 2L/2S mode is unavailable because of
not_enough_filtered_sectors:
Reduced mode attempts smaller shapes:
1L/2S
1L/1S
Reduced mode uses lower gross exposure:
| Regime | Full Gross | Reduced Gross |
|---|---|---|
| Expansion | 1.5 | 0.8 |
| Transition | 0.8 | 0.4 |
| Stress | 0.4 | 0.2 |
The same mandate guards remain active:
abs(dollar_exposure) <= 0.01
gross tolerance respected
Thus, V3.2 does not become aggressive. It becomes more adaptive.
7. V3.2 Candidate Backtest Result
The V3.2 candidate was tested over the same 2023-01 → 2026-04 window.
| Metric | V3.1R | V3.2 Candidate |
|---|---|---|
| Accepted months | 18 | 24 |
| Rejected / invalid months | 22 | 16 |
| Rejection rate | 55.00% | 40.00% |
| Total return | +1.25% | +3.99% |
| Max drawdown | 4.05% | 4.45% |
| Hit rate | 44.44% | 45.83% |
| Annualized Sharpe | 0.1454 | 0.3097 |
| Random benchmark percentile | 66.90% | 80.80% |
V3.2 improved return by +2.73 percentage points while increasing max drawdown by only +0.40 percentage points.
This suggests that V3.2 recovered useful opportunities without materially damaging risk control.
8. Reduced Mode Contribution
V3.2 accepted 6 reduced-mode months:
2024-02
2024-04
2024-11
2025-08
2026-03
Reduced-only performance:
| Metric | Value |
|---|---|
| Reduced months | 6 |
| Positive reduced months | 3 |
| Negative reduced months | 3 |
| Reduced-only total return | +2.70% |
| Reduced beta-adjusted return sum | +3.37% |
| Avg reduced beta-adjusted return | +0.56% |
The beta-adjusted result is especially important. It indicates that reduced-mode contribution was not simply caused by market beta exposure.
9. Reduced Months Detail
| Signal Month | Realized Month | Regime | Effective Shape | Return | Beta-Adjusted Return | Main Pair |
|---|---|---|---|---|---|---|
| 2023-08 | 2023-09 | Transition | 1L/1S | +1.61% | +1.15% | Long XLE / Short XLU |
| 2024-02 | 2024-03 | Expansion | 2L/1S | -1.10% | -1.10% | Long XLI,XLC / Short XLU |
| 2024-04 | 2024-05 | Transition | 1L/1S | -1.48% | -1.02% | Long XLE / Short XLK |
| 2024-11 | 2024-12 | Expansion | 1L/1S | +1.96% | +1.99% | Long XLC / Short XLV |
| 2025-08 | 2025-09 | Expansion | 1L/1S | +2.36% | +2.32% | Long XLY / Short XLP |
| 2026-03 | 2026-04 | Transition | 1L/1S | -0.60% | +0.02% | Long XLU / Short XLC |
Best reduced month:
Return: +2.36%
Beta-adjusted return: +2.32%
Worst reduced month:
Return: -1.48%
Beta-adjusted return: -1.02%
10. Interpretation
V3.2 appears to improve the LRAC framework in three ways:
1. Better Signal Coverage
V3.2 reduces the rejection rate from 55% to 40%.
This means the system can act in more months while still avoiding unsafe beta-exposure breaches.
2. Better Use of Incomplete Flow Structures
V3.1R required full symmetry. V3.2 recognizes that a market does not always present clean 2L/2S structures.
Sometimes a smaller 1L/1S or 2L/1S relationship carries valid information.
3. Preserved Risk Discipline
V3.2 increases average beta exposure from 0.0070 to only 0.0167, while reduced-mode average beta exposure remains 0.0458.
Both remain comfortably below the 0.10 mandate threshold.
This suggests that V3.2 improves adaptability without becoming uncontrolled.
11. Remaining Risks
V3.2 is not yet a proven production strategy. It is a stronger research candidate.
Key risks remain:
-
Small Sample Size
Only 40 months were tested, with only 6 reduced-mode months. -
Reduced Short-Leg Risk
Negative reduced months were mostly caused by short legs moving against the system. -
Potential Overfitting
V3.2 was designed after observing V3.1R rejection behavior. It should be monitored live before further optimization. -
Benchmark Context
V3.2 should not be compared directly with SPX as a return-maximizing long-only benchmark. Its relevant comparison is against matched long/short random portfolios, simple momentum, and earlier LRAC versions.
12. Decision
V3.2 should become the current primary Flow Observatory ETF research candidate.
It should not yet be marketed or treated as a proven investment strategy. Instead, it should be monitored as an audit-ready sector-flow research engine.
Recommended operational decision:
Continue monthly live tracking.
Do not move to V3.3 yet.
Do not modify λ_C yet.
Collect 3–4 additional live months before further changes.
13. Next Steps
- Continue using V3.2 engine and tracker for monthly live observation.
- Run the V3.2 official tracker after each realized month closes.
- Accumulate at least 3–4 additional live months.
- Review live performance separately from backtest performance.
- Only after additional live data, consider whether a V3.3 reduced-short safety filter is justified.
- Begin designing a Flow Observatory archive/dashboard after the V3.2 evidence base matures.
14. Final Positioning
V3.2 does not prove that Flow Observatory is a finished strategy.
But it does show that the sector-flow hypothesis is becoming testable, versioned, auditable, and empirically meaningful.
The core insight is:
V3.2 captures this insight by allowing reduced-gross, beta-controlled expressions of incomplete flow structures.
This makes V3.2 the strongest LRAC candidate so far.
2025 Snapshots
Finance: System-wide structural contraction with negative deviation clusters
Healthcare: Early-year expansion surge followed by phase normalization
Retail: Prolonged contraction with late-year positive momentum divergence
Energy: Mid-cycle contraction transitioning into selective expansion
2024 Snapshots
MSFT: Stabilizing post-acceleration
TSLA: Deep contraction phase
BA: Early expansion signal
MSFT: Neutral flow
TSLA: Contraction continues
BA: Recovery forming
Reports
Flow leaves traces.
Archive preserves them.
All snapshots are manually reviewed before publication. No automated report is archived without validation.