Applied AI engineering program

Stop demoing. Ship an AI system that survives real invoices.

Most AI courses end right where things get interesting, at the moment the demo meets messy vendor PDFs and the model starts inventing totals. I have watched brilliant engineers stall at exactly that wall. Keel starts there: across 13 phases you build an invoice reconciliation and dispute triage pipeline for OmniCart Operations, a simulated B2B distributor, from first commit to deployed system. Every submission runs against real tests and a published rubric. It passes only when the work holds up.

Monthly all-access subscription. Clear a milestone gate. Get 15% back.

13

Phases, one system

889

Hours of real build work

3

Ways every milestone is checked

15%

Rebate at each milestone gate

How a unit works

Five steps. Same loop, every unit: you will know it by heart by week two.

Each unit is a small build with the same heartbeat: learn the concept, practice on a parallel task, ship the deliverable, get it graded, move on. No surprises after unit one, because the surprise budget goes to the ideas, where it belongs.

  1. STEP 01

    Learn

    One written lesson, read start to finish. It opens with the concept, grounds it in the client's numbers, then shows exactly what you are about to produce, with checkpoints you answer before you peek. (Peeking is allowed. Peeking first is noticeable.)

  2. STEP 02

    Practice

    Every chapter builds the program in front of you, a few explained lines at a time. Then you finish it yourself on the client's files, and automated checks tell you exactly which step is missing.

  3. STEP 03

    Build

    Ship the deliverable to your own git repository. The deliverable and the submission contract are published up front, so you will never have to guess what 'done' means.

  4. STEP 04

    Verify

    Push, and automated checks plus rubric review get to work. Every verdict quotes evidence from your code, so a Not yet always tells you what to fix.

  5. STEP 05

    Move on

    Pass a unit and the next one opens. Pass a milestone gate and 15% comes back to your card. Only verified work moves you forward, and that is the whole transcript.

Graded for real

A pass means the work held up. Here is exactly how we check.

This program grades what you shipped, against a bar you read before you started. Three stages, every milestone:

1

Automated checks

Your code runs in an isolated run against the unit's test suite and data. Results list each automated check as Passed or Not yet, with the full command output, so you see exactly what the grader saw.

2

Rubric review

A language model reads your submission against the unit's published criteria and quotes the lines of your code behind every verdict. No quoted evidence? The verdict reads Not yet. That is the rule that keeps the whole system honest.

3

Defend the build

Milestone work gets defended out loud, once to a technical reviewer and once to the budget holder. Both are AI playing a written brief you can read first, and your side is scored against a rubric. Paste-and-pray does not survive this room.

Support on every unit

Help that shows up at 2am, scoped to the exact lesson.

Stuck is normal; stuck for a week is a curriculum bug, and we treat it like one. Each unit ships its failure modes with fixes, plus an assistant that knows the lesson.

  • An assistant scoped to the unit

    Ask why a concept works. Ask for another exercise. Ask about the error that has been glaring at you since midnight. It answers from the curriculum only, so it will not hallucinate a syllabus.

  • Planned failure modes, published

    Every unit lists what usually breaks, each with its fix linked. Most stuck moments end in one click, and the rest end in the assistant.

  • A pod that ships with you

    Each week you post what shipped, what broke, and what is next. Peers review milestone work against the same rubric the platform uses: harsh, but it is the same harsh for everyone.

  • A public gallery of real work

    Passed projects can go public with their verification attached. Employers never have to take your word for it, because they can read the verdict.

Curriculum units

Start here. These units are open today.

Every unit page shows the lesson, the practice set, the deliverable, and the rubric: all four, before you pay a cent.

All 13 phases
  • Unit 0.1Phase 0

    Meet the client: Lantern Home

    none

    Open the unit
  • Unit 0.2Phase 0

    Phases, time-boxes, and how your work is graded

    none

    Open the unit
  • Unit 1.1.1Phase 1

    A program that reads a customer's message

    read_message.py, which opens messages/M-1041.txt and prints the customer's email address and the order number found in the message.

    Open the unit

Your first submission is one push away. Seriously.

Create an account, take the 20-minute placement check or skip it, and open your first unit in the same session.