HVE
Hyper Velocity Engineering Microsoft framework for agentic coding best practices
Research and Teaching Map
Research reviewed on 2026-11-03. Microsoft documentation summaries and proposed Frontier teaching material are distinguished in the linked notes. Labs and timings have not yet been tested.
- HVE Core — research overview and source map
- HVE Project Lifecycle — nine delivery stages
- HVE RPI Workflow — evidence, planning, implementation, review, and follow-up
- HVE Context Engineering — focused context and durable handoffs
- HVE Roles and Collaboration — engineer and architect responsibilities
- HVE Installation and Cohort Baseline — setup choices and delivery checks
- HVE Teaching Plan — proposed learning sequence, pilot lab, and assessment evidence
Research Maintenance
Keep source URLs and verification dates on reference notes. Record the exact tested product version or source commit for each lab, and recheck before each cohort. Use unique descriptive note names and Obsidian wikilinks; link new HVE notes back to this hub. Teaching proposals remain drafts until validated.
Program Links
Role in the curriculum
HVE is the spine of the program. GitHub Copilot, Foundry and Fabric are where the method gets applied. Product features change monthly; a method for working with agents lasts longer. Scope is decided: we teach Microsoft’s HVE Core as published (^q-006).
The proposed learning sequence, pilot lab and assessment evidence are in HVE Teaching Plan.
Learning outcomes (draft)
- Run a full RPI cycle on a real repo with Copilot + HVE agents → HVE RPI Workflow
- Write instructions/skills that encode a team standard → HVE Context Engineering
- Set review gates that fit the risk of the change
- (Delivery roles) Plan and govern an HVE-style engagement → HVE Roles and Collaboration, Learner Personas
Risk
Microsoft describes HVE Core as opinionated and rapidly evolving. Pin a version per cohort and recheck before each delivery (see Research Maintenance).