Start here if you want to understand how Portfolio Engineers fits together.
Start with the philosophy to understand how the system is designed. Use research to build understanding, inspect the framework to see how it operates, and view portfolios as reference implementations in practice.
Best for first-time visitors who want the cleanest path through the philosophy, the operating system, and the portfolio layer.
The canonical explanation of the philosophy, the architecture, and the role of ARC, HYS, and AG.
Regime, momentum, leadership, and structure work together to show how the operating layer reads markets in practice.
ARC, HYS, and AG show how the philosophy becomes a real sleeve-based allocation structure.
Suggested Path
Four steps. Clear roles. Better orientation.
Start with the canonical explanation of the Portfolio Engineers philosophy: the three jobs a portfolio must do and why the system separates ARC, HYS, and AG.
Build the mental model through the written library: regimes, rebalancing, TDCA, concentration, and portfolio construction tradeoffs.
See how the operating layer works: regime, momentum, leadership, and structure combine to turn market observations into a structured read of posture and participation.
Review ARC, HYS, and AG as reference implementations. These are practical builds that express the philosophy in a usable portfolio structure.
Philosophy summary
The short version of the philosophy.
The Thesis page provides the full canonical explanation. The principles below are a condensed operational version intended for orientation, not a replacement for the Thesis.
Structure over prediction
The system is built around portfolio design, role clarity, and guardrails rather than heroic forecasting.
Behavior is part of the math
A sound portfolio should remain psychologically maintainable during drawdowns, volatility spikes, and narrative stress.
Role clarity helps preserve portfolio structure.
ARC compounds, HYS stabilizes and preserves optionality, and AG provides bounded asymmetric upside.
Tradeoffs should be explicit
No framework wins everywhere. The goal is a coherent system that balances growth, survivability, and optionality honestly.
The site moves from philosophy → evidence → system → implementation.
Portfolio Engineers is organized deliberately. The Thesis explains the core architecture. Research pages defend specific ideas. The Framework shows the operating layer. Portfolio pages show how the philosophy becomes a usable structure.
Using the site this way makes navigation easier and reduces the risk of treating one article, one dashboard, or one sleeve as the whole system.
A common mistake to avoid
Do not treat the regime engine as a prediction machine or the portfolio pages as one-size-fits-all prescriptions. The site is built to show structure, tradeoffs, and process, not to promise certainty.
The framework translates observable conditions into structured posture.
The framework is where regime, momentum, leadership, structure, composites, and posture logic come together. Its role is to reduce structural mismatch, not to justify constant action.
When evidence is mixed, the system generally favors steadiness. When evidence strengthens, any changes are designed to be measured, bounded, and auditable rather than dramatic.
What the framework is not
- • Not a day-trading dashboard
- • Not a prediction engine for every market turn
- • Not permission for constant reallocation
- • Not a replacement for diversification
The portfolio pages turn philosophy into a real allocation system.
ARC, HYS, and AG are not random buckets. They are role-specific sleeves inside a broader architecture: durable returns, capital stability, and bounded asymmetric upside.
The best path is simple: understand the logic first, then inspect the operating layer, then review the portfolios as reference implementations.
What new readers should do first
- 1) Read the Thesis.
- 2) Read one or two research pieces.
- 3) Open the Framework.
- 4) Review ARC, HYS, and AG.