Hydra separates architecture, governance, and trading implementation into distinct layers. That separation is what makes the system easier to reason about, safer to operate, and harder to break under live conditions.
Hydra Core is the public-facing architecture and doctrine layer. It defines the principles, system boundaries, governance posture, and structural thinking behind the stack.
This is where the operating philosophy lives: risk-first design, fail-closed posture, operator visibility, and separation of concerns.
Hydra Guardian is the policy and supervision layer that sits above execution. It is responsible for posture checks, veto logic, rule enforcement, and independent controls that constrain what the system is allowed to do.
This is the layer that answers: even if a strategy wants to act, should it be permitted to?
Hydra Quant is the trading implementation layer: engines, bridges, monitoring, telemetry, deployment, and live execution surfaces.
It is where research meets infrastructure — but inside governance boundaries established by the broader Hydra stack.