HVE Roles and Collaboration

Up: HVE Core · Teaching: HVE Teaching Plan

Microsoft Guidance

The Engineer Guide emphasizes investigation, implementation planning, coding, review, and delivery. It pairs RPI tooling with file-matched language instructions and Git workflows.

The Tech Lead Guide adds architecture decisions, diagrams, standards, and curation of AI artifacts. It distinguishes code review from implementation-against-plan review and positions automated review as support for human judgment. hve-builder supports creating and improving prompts, agents, instructions, and skills.

The guide index also covers TPM, security architect, data scientist, SRE/operations, business program manager, new contributor, and UX designer, plus utility capabilities. These additional role guides have not yet been reviewed in depth for this vault.

Frontier Teaching Proposal

Use a shared foundation followed by paired engineer/architect exercises. The engineer supplies implementation and validation evidence; the architect challenges trade-offs, checks requirements, and records a disposition. Rotate roles once.

Audience	Proposed emphasis	Evidence to assess
Engineer	Bounded implementation and validation	Working change with acceptance evidence
Architect / lead	Decisions, standards, review	Decision rationale and a justified review
Engagement lead	Problem framing and client handoff	Scope, unresolved questions, and accountable owners

The engagement-lead path is a Frontier proposal pending deeper TPM and business-program-manager research. Confirm the first cohort’s roles through ^q-004 before committing to separate tracks.