Cloud systems research

Cloud Orchestrator

Control decisions you can trace.

From workload data to scoped A–H policies, execution checks and independent outcome evaluation.

5 published notesMar 2026 - Present
Start reading

In this journey

The reading path

Follow the project from its first problem through the work that followed.

  1. / 6 min read

    Building a Causal Foundation for Failure Forecasting

    From Borg trace windows to causal features, mature failure labels, and temporal validation: the data foundation behind Cloud Orchestrator.

  2. / 6 min read

    Data Repair, Temporal Validation, and Two Different Prediction Tasks

    Why causal schemas, mature labels, label-independent validation sampling, and model provenance matter—and why Borg failure forecasting differs from the live controller's next-window predictors.

  3. / 8 min read

    Eight Roles, One Mutation: Designing the Control Boundary

    The six-layer Cloud Orchestrator separates A–H responsibilities, feasibility, serial arbitration, durable execution, and independent assessment.

  4. / 8 min read

    Tuning a Controller Without Tuning Its Evidence

    Separating legacy PPO and Optuna experiments, local Kubernetes comparison, verified actuation, and a frozen independent CSC/CSP outcome gate.

  5. / 9 min read

    Learning Without Surrendering Control

    How Cloud Orchestrator combines eight specialist roles with an optional adaptive ranker, verified decision feedback, frozen comparisons, and evidence-gated policy promotion.

Search writing

Search across titles, article text, and tags.