Building with PyTorch, TensorFlow, Ray, MLflow, W&B, or Kubeflow? GreatCTO auto-detects the mlops archetype and ships dataset versioning (DVC / LakeFS), training cost budgets, drift detection, bias / fairness audit, shadow + canary serving, and EU AI Act high-risk gates from day one.
mlflow + torch + dvc →Compliance auto-suggested: eu-ai-act · nist-ai-rmf · iso42001. Specialist agents activated:
Dataset lineage (DVC / LakeFS) · cost budget enforcement · MLflow / W&B model registry · drift detection wired · bias audit per protected attribute · shadow → canary serving · EU AI Act risk tier classification.
tests/eval/EVAL-*.md golden scenarios · accuracy + F1 + per-cohort breakdown · cost-per-eval · cross-model comparison.
Prompt injection (if LLM fine-tune) · model extraction · membership inference · adversarial robustness · supply chain (pretrained model provenance).
PII classification on training data · GDPR Art. 17 erasure → retrain trigger · sub-processor docs · cross-border transfer compliance.
Packs auto-attach when CLI detects pack-specific signals (e.g. twilio in deps → voice-pack). Each pack adds its own reviewer agents + human gates on top of the base archetype pipeline.
$ npx great-cto init