HVE Context Engineering

Up: HVE Core · Related: HVE RPI Workflow

Microsoft Guidance

Context Engineering treats the information visible to the model as a resource to manage deliberately. Long conversations can obscure instructions, task evidence, and the next action.

Use a fresh chat or /clear when accumulated material interferes with the task; /compact summarizes history but can lose detail. Resume from dated task artifacts and stable identifiers. Resetting context does not require repeating adequate research or restarting the workflow. Supply the plan and critique for implementation, and the plan, changes, and relevant validation evidence for review.

The guide’s token counts and explanation of model attention are illustrative claims from Microsoft documentation, not benchmarks established for our learners’ chosen models.

Frontier Teaching Proposal

Run a handoff exercise in pairs. One learner completes planning; another receives a new conversation plus selected artifacts and implements one bounded task. The second learner must identify the approved scope, unresolved decisions, and acceptance criteria without relying on the first learner’s chat history.

Compare a useful handoff with one missing the acceptance criteria. Ask what information must be restored before work continues. Grade evidence selection and continuity of decisions.

Keep organizational standards in reusable repository artifacts, and task-specific facts in the task record. The instructor should demonstrate how an irrelevant file or stale decision can distort the next action, then remove it and repeat the request.