AI curriculum
Course outline for Applied Generative AI
A plausible classification can still violate the task rules or send too many cases to review. Design a structured interaction, validate its proposed tool inputs, and compare routing choices on unseen examples. Include an abstention path and measure errors and review demand rather than trusting a model's stated confidence.
- Technology
- AI Foundations
- Duration
- 6 hours
- Modules
- 3 · 2 hours each
- Level
- Level 2
About Applied Generative AI
A plausible classification can still violate the task rules or send too many cases to review. Design a structured interaction, validate its proposed tool inputs, and compare routing choices on unseen examples. Include an abstention path and measure errors and review demand rather than trusting a model's stated confidence.
Applied Generative AI Course Objectives
- Write a task prompt with examples, exclusions, and explicit output requirements.
- Validate structure separately from the meaning and evidence of an output.
- Describe and test a bounded function interface without granting action authority.
- Compare model response fixtures on held-out cases using an explicit rubric.
- Select routing and abstention rules using observed errors and review capacity.
- Assemble relevant text or image context while excluding unnecessary data.
Pre-requisites
- Artificial Intelligence Foundations or equivalent awareness of AI capabilities and limitations.
- Familiarity with common AI interfaces.
- Basic understanding of structured data such as JSON; a short JSON bridge is available.
Before this course
Complete the required courses or bring equivalent experience. Recommended courses add useful depth; they are not enrolment gates.
Required preparation
Recommended preparation
Recognizes AI capabilities and limitations; can read JSON or learn it through a short bridge before structured interaction exercises.
Find your place in the learning mapLab Setup
- Computer with a browser, JSON editor, and spreadsheet or supplied local validator.
- Synthetic documents/images, separate labeled development and held-out cases, mock function exchanges, two response sets, and an explicit error-cost/reviewer-capacity worksheet.
- Optional local model or approved nonproduction API; no durable application store, live tool mutation, or paid service is required.
Detailed Course Outline
Module 1: Specify and validate an interaction (2 hours)
- Prompting: Task instructions, examples, exclusions, and output requirements; separate model inference from calculations that deterministic code should perform.
- Structured outputs: Required fields, allowed values, and schema checks; validate source support and intended meaning separately from structural compliance.
- Tool use: Capability descriptions, proposed arguments, and external execution; treat model-selected operations as untrusted proposals rather than granted authority.
Practical outcome: Convert a document classification request into a prompt, schema, and semantic rubric; distinguish model inference from deterministic calculation and treat proposed tool arguments as untrusted.
Module 2: Choose a bounded execution path (2 hours)
- Function calling: Argument schemas, call identifiers, and tool-result exchanges; reject malformed inputs before invoking the supplied mock function.
- Model selection: Task criteria, held-out response comparisons, and observed error categories; choose models using evidence rather than brand or self-reported confidence.
- Model routing: Simple and difficult case routes, error costs, and review limits; compare fixed routing policies against observed failures and abstentions.
Practical outcome: Inspect a mock function-call exchange, compare two model response sets on held-out inputs, and choose routes using false-positive, false-negative, and human-review costs rather than brand or stated confidence.
Module 3: Use context and handle uncertainty (2 hours)
- Context engineering: Relevant evidence, examples, and minimal task inputs; exclude unnecessary data and distinguish missing support from an unclear instruction.
- Multimodal interaction: Text and image evidence, input relevance, and interpretation limits; construct bounded requests without treating uncertain perception as established fact.
- Decision and classification models: Label contracts, false positives, false negatives, and abstention thresholds; select policies on development cases before evaluating held-out results.
Practical outcome: Prepare minimal text/image context, include an abstention route for insufficient evidence, and compare threshold policies against observed errors and a fixed reviewer capacity.
Practical exercise
- Produce a classification prompt, output contract, routing table, and held-out evaluation report.
- Accept a valid source-supported classification; reject a structurally valid but unsupported label and malformed function arguments.
- Score at least twelve supplied cases, separating errors, abstentions, and review demand; compare two routing policies against a stated review limit.
- Explain one case where rules or human review are preferable and why self-reported confidence is not a calibrated probability.
What you will produce
Design and compare a validated classification interaction with a measured routing and abstention policy.
How the work is checked
- Structure and semantic support are checked independently.
- Routing policies are frozen before the held-out report records errors, abstentions, and review demand.
- The selected policy respects the stated reviewer capacity and error costs; score thresholds are not described as calibrated probabilities.
- Mock tool inputs are validated without equating a function proposal with permission to execute.
Six hours of individual structured interactions and fixture-based routing, with exercises inside module time. Select a routing threshold on supplied development cases, then freeze it before scoring separate held-out cases. Any confidence score is an uncalibrated signal unless independent calibration evidence is supplied. Durable state and deployed tools are separate work.
When another approach is better
- Use deterministic rules for stable classifications that do not need model interpretation.
- Do not automate uncertain decisions when the review queue exceeds capacity or the evidence is insufficient.
How we train
Contact us for full course details, including duration, delivery options and lab requirements.
Ask about exercises, instructor feedback and the prior knowledge you need. Tool-specific courses marked provisional may become modules in a broader course.
Discuss your learning goalsRelated Courses
These courses list this course as preparation.