Curriculum Map

Working hypothesis — HVE is the spine; product tracks are where the method gets applied.

flowchart TB
  HVE["HVE Framework<br/>(method: Research → Plan → Implement → Review)"]
  HVE --> GH["GitHub Copilot<br/>code & SDLC"]
  HVE --> FD["Microsoft Foundry<br/>AI apps & agents"]
  HVE --> FB["Microsoft Fabric<br/>data & analytics"]
  GH --> CAP["Capstone<br/>one scenario across all three"]
  FD --> CAP
  FB --> CAP

Role paths × product tracks

Roles are mixed (see Learner Personas): everyone shares the HVE + scenario core, then branches by role. Product tracks go deep for technical roles and stay at the “what it enables” level for delivery roles.

Tracks

Track	Primary persona	Core question it answers
HVE	Everyone (consulting firm engineers & architects)	How do we engineer with agents, repeatably and safely?
Github Copilot	Developers	How do we ship software faster without losing quality?
Foundry	AI / app engineers	How do we build, evaluate, and run AI agents in production?
Fabric	Data engineers / analysts	How do we get AI-ready data and analytics on one platform?

Levels (proposal)

• L1 Foundations — exec/manager-friendly + hands-on basics (½–1 day)
• L2 Practitioner — role-based hands-on workshop (2–3 days) → our certification
• L3 Frontier — capstone across tracks + graded practical → credential (see Certification and Assessment Design)

Capstone scenario

Learners are consultants, so the workshop spine is a mock client engagement (borrowed from Claude Frontier Academy): use-case discovery → architecture → build with HVE → evals & security review → handover to the client team. Draft scenario: a regional insurer wants an agent to triage claims. It uses Fabric for the claims data, Foundry for the agent, and Copilot + HVE to build and ship it. This is Frontier’s own FDE model, taught.

Module index

Use Template - Module for each module and link it under its track note.