Skip to content

Routing policies

Router quality depends less on YAML and more on your rules: privacy, difficulty, cost, latency, and verifiability.

Classify before calling

Terminal
task_policy:
  summarization:
    preferred: local-fast
    max_cost_usd: 0.01
  legal_or_private:
    preferred: local-private
    cloud_allowed: false
  final_editorial_review:
    preferred: frontier-review
    requires_trace: true
  code_patch:
    preferred: coding-agent
    requires_tests: true

Routing signals

  • Data sensitivity: public, internal, personal, or secret.
  • Expected difficulty: simple, medium, strong reasoning, or multimodal.
  • Latency tolerance: interactive, batch, or overnight review.
  • Need for citations, traceability, or human review.

Start with few rules. A router with ten clear policies usually works better than one with a hundred exceptions nobody understands.

Complete Aulafy mapSee how this lesson fits without leaving your path.

Complete Aulafy map

How all courses connect

This is not a checklist. Start with the foundation, choose an outcome, and go deeper only when your project needs more control.

  1. 1Understand
  2. 2Apply or build
  3. 3Operate with confidence
01

Choose an application

Turn the foundation into a visible outcome: a website, a business improvement, media, or an interactive experience.

Continue into the technical branch when you need to maintain code, data, or infrastructure.

02

Build with code

Prepare your environment, work with coding agents, and run models while keeping control of your projects.

This branch prepares you to design and operate reliable AI systems.

03

Take systems to production

Combine retrieval, agents, evaluation, security, deployment, and model adaptation when the problem requires it.

You do not need every course: choose the component your system needs and return as it grows.

View full catalogue