AI VISTA COURSES

Build an AI workflow step by step, like taking a real course.

Browse every course and its complete syllabus below. Compare who each course serves and what you will make, then enter at the right lesson.

4complete courses67sequenced lessons1real task to begin
LEARNING ARC / FOUR COURSESFROM TASK TO SAFE OPERATION

ALL COURSES / COMPLETE SYLLABI

Choose a course, then open the lesson you need.

Every course shows its audience, outcome, and all published lessons.

60–90 minutes5 lessons

Build your first testable AI workflow

Move from an attractive idea to a bounded task, a workflow-or-agent decision, and a ten-case pilot a colleague can review before further investment.

Show all 5 lessons
  1. 01Should this task use AI at all?
  2. 02Turn an AI idea into a testable task brief
  3. 03Workflow or AI agent? Choose the control loop before building
  4. 04Draw the data boundary before AI sees the input
  5. 05Run a ten-case AI pilot before you scale
FOR
For anyone turning a repeated knowledge task into a first AI-assisted workflow.
OUTCOME
A task brief, control-loop decision, and ten-case pilot sheet.
LESSONS READ0 / 5
FOR
For teams whose prompt works in a demo but changes quality across real inputs.
OUTCOME
A context map, compaction checkpoint, acceptance contract, output protocol check, injection test set, and failure log.
LESSONS READ0 / 14
FOR
For knowledge assistants, policy search, support systems, and internal research workflows.
OUTCOME
A method decision, source admission register, chunking and retrieval trials, access and index checks, a no-evidence response gate, and a citation audit.
LESSONS READ0 / 11
Core 3–4 hours; branches vary37 lessons

Automate with permission, recovery, and cost controls

Build a bounded tool-using workflow with control ownership, data and action authority, stop rules, human review, recovery, service fallback, cost, and drift checks. Test delegation, MCP, memory, models, and deployment only when your task needs them.

Show all 37 lessons
  1. 01Workflow or AI agent? Choose the control loop before building
  2. 02Draw the data boundary before AI sees the input
  3. 03Give an agent the smallest useful permission
  4. 04How do you test an AI agent sandbox's file, network, and credential boundaries?
  5. 05Design an AI agent tool contract before exposing the function
  6. 06When should an AI agent continue, retry, or stop?
  7. 07Put human review where it can change the outcome
  8. 08Design recovery before the agent fails
  9. 09How should an AI model service fail over? Plan retries, queues, and human handoff
  10. 10Map the full cost of an AI workflow
  11. 11Your AI agent's real cost is cost per accepted task
  12. 12Monitor an AI workflow before drift becomes an incident
  13. 13How to implement an AI agent tool-calling loop
  14. 14Subagent or multi-agent? Choose the delegation topology
  15. 15When should an AI agent save, correct, or delete long-term memory?
  16. 16How can a long-running AI agent task resume without repeating work?
  17. 17How to debug one AI agent run from its observable trace
  18. 18What should you check before connecting a third-party MCP server?
  19. 19When should a repeated AI task become an agent skill?
  20. 20How do you load and unload an agent plugin safely?
  21. 21Your MCP server works locally. What breaks when a team depends on it?
  22. 22Claude Code without the chaos: a review-first workflow for coding agents
  23. 23Log the decision, not the prompt: a trace schema for AI agents
  24. 24Choose a model with a job-specific scorecard
  25. 25How much VRAM does a local LLM need? Budget weights and KV cache
  26. 26Is 4-bit LLM quantization worth it? Test fit, quality, and speed
  27. 27LoRA or QLoRA fine-tuning? Run a small, reviewable pilot
  28. 28Ollama, llama.cpp, vLLM, or SGLang? Choose a local inference engine
  29. 29How many concurrent requests can a local LLM serve?
  30. 30AI inference latency debugging: trace the wait from request to screen
  31. 31How many GPUs does a local LLM service need?
  32. 32Local LLM or cloud API? Choose by data, peak load, and operations
  33. 33Why prompt caching misses: run a three-request test
  34. 34AI support triage: the 10-case pilot that earned a review gate
  35. 35AI content review: the citation gate that stopped a confident wrong answer
  36. 36AI research synthesis: when the source changes after the brief
  37. 37The approval agent that could move money—until we removed the payment tool
FOR
For teams moving an agent or tool-using workflow from prototype toward production.
OUTCOME
A control-loop choice, data and permission boundaries, sandbox and tool contracts, runtime stop and human review gates, recovery runbook, service fallback, cost map, and drift watchboard; branch evidence where relevant.
SYLLABUS READ0 / 37

LEARNING ROUTE / STAGE 03 · COURSES

This stage follows a course path, then branches where the task requires it.

Courses are organized around real work. Related lessons reuse earlier decisions or artifacts. Complete the path your task needs and open relevant branches to produce a reviewable result.

BRING
The task direction found in the decision map
DO HERE
Complete decisions and outputs lesson by lesson
LEAVE WITH
A connected set of reviewable artifacts
WHEN THIS STAGE IS DONE Read for a specific gap Use the reading list when a branch needs more depth.

HOW EACH COURSE WORKS

A lesson is not an article you finish. It is a small read, make, review, continue loop.

All four courses use the same learning actions on different problems. Bring one real task and advance one decision per lesson; complete a specialized branch only when its conditions apply.

  1. 01
    READ

    Identify the one decision this lesson changes

    Compare the case and boundary with real work; do not try to memorize every term.

    DONE SIGNAL · You can state the decision in one sentence.
    →
  2. 02
    MAKE

    Replace the blank tool with your own material

    Use current inputs, criteria, owners, and failure handling instead of copying the example.

    DONE SIGNAL · The artifact contains real fields, cases, or constraints.
    →
  3. 03
    REVIEW

    Ask a second person to apply the same standard

    Offer no verbal explanation. Let the reviewer decide pass, revise, or stop from the artifact alone.

    DONE SIGNAL · Disagreement becomes a named issue for the next iteration.
    →
  4. 04
    CONTINUE

    Carry the artifact into the next lesson

    Keep the same task. Open the reading list only when practice exposes a precise gap.

    DONE SIGNAL · The syllabus shows connected changes, not scattered notes.
    ✓