HVE RPI Workflow
Up: HVE Core · Related: HVE Context Engineering, HVE Teaching Plan
Microsoft Guidance
The RPI overview describes an evidence-led workflow:
| Action | Entry | Result |
|---|---|---|
| Assess evidence; investigate a demonstrated gap | /rpi-research | Research when needed; adequate evidence can be reused |
| Plan | /rpi-plan | Task-centered plan; critique by default, unless skipped |
| Implement | /rpi-implement | Approved changes and validation evidence |
| Review | /rpi-review | Optional acceptance record; sources under review stay unchanged |
| Follow up | Route the finding | Defects to implementation, decisions to planning, evidence gaps to research; residual work to a new item |
RPI Agent provides a lifecycle entry point, manual by default, with automatic operation on request. A clear isolated edit can use a smaller direct action. Execution completion and acceptance outcome are distinct.
The worked guide uses stable phase/task IDs (Pxx, Pxx-Txx). Artifacts sit under .copilot-tracking/: research, plans, plan critiques in reviews/plans, changes, and acceptance reviews in reviews/logs, grouped by date and task. Significant departures require affected plans to be updated before dependent execution resumes.
Frontier Teaching Proposal
Require an acceptance review in the assessed lab so learners can demonstrate reconciliation, while explaining that this is our course requirement. Give learners one completed task with a failing acceptance criterion to expose the difference between “done executing” and “accepted.”
Use one task identity throughout the exercise. Have learners explain why they investigated a gap or reused existing evidence, then justify the route for each unresolved finding.
Documentation Reconciliation
The getting-started overview introduces a sequential research-first workflow. The RPI overview, updated October 30, 2026, gives the more specific conditional research and optional review rules. Teach these nuances and verify them against the chosen cohort baseline.