Prepare the feature and schema decision exercise

Orientation | Course | Cowork method

Prepare HVE access and client interview evidence, not ten builds or code-debugging exercises.

Core learner requirements

1. Approved Cowork access with the current HVE Squad plugin enabled.
2. An authorized OneDrive/SharePoint training project folder, explicitly selected or created with consent.
3. The selected guide's Copy standalone prompt request, with its interview, full applicable rules, DS definitions and sample records included. Static scenario evidence needs no separate attachment.
4. A workshop decision owner and an operator contact for actual gates/access issues.
5. A partner to inspect the handoff or continue the project, where possible.

No Power Apps authoring skill, Dataverse environment, RPA machine, Power BI Desktop or code-app workspace is required for the core.

Facilitator: verify the actual plugin

Use the current release's setup guidance and rehearsal. This repository does not install the plugin/server.

• Pin plugin/skill/server versions and verify compatibility.
• Confirm live discovery and squad_run under the participant identity.
• Verify the selected folder's actual project identity/binding.
• Rehearse a bounded request, status of the same run, retrieval of exact outputs and verified project persistence.
• Rehearse a same-run human question and distinguish its response from operator approval.
• Keep operator privileges restricted. An ordinary learner cannot self-approve.
• Rehearse a missing-tool/access failure and the truthful stop/recovery path.
• Rehearse the copy button with no course-file attachments or previous chat. Check that the request includes the actual interview, policy text and records, not just their IDs.
• If additional documents are attached, confirm they are actually readable. Do not assume the server can follow a local course URL or arbitrary SharePoint link.

A copied tool catalogue or passing code test is not a live participant rehearsal.

Source and feedback preparation

The business pack supplies policy and raw records. The current HVE-DECISIONS-1.0 cases supply interview evidence, candidate choices, changes and fictional design-review feedback.

Tell participants explicitly:

• Case proposals are not approved architecture or instructions.
• Fictional design-review feedback is not their own platform test or an HVE output.
• Sample files and earlier maker material are not mandatory schemas. Do not supply a ready table/control blueprint as the answer.
• The agent may see all case sections; these are learning cases, not blind evals.
• Actual HVE artifacts/run IDs must come from the real project.
• Later prompts need actual selected features/models and human decisions. Retrieve their verified originals or ask for the missing choice; do not invent prior acceptance from the static case.
• Actual platform execution, if added, is recorded separately.

Keep facilitator holdouts out of participant tuning. Do not put confidential client material, credentials or real personal data in training context.

Facilitation

Learners should:

1. Attempt the opening question.
2. Submit a bounded HVE request and inspect the result.
3. Answer real questions using stated authority.
4. Select technology-specific features and compare the data models they need.
5. Apply a changed requirement and justify field/relationship/scope consequences.
6. Walk realistic records, review the design pack and transfer the rationale.

Do not teach raw specialist-tool dispatch, designer settings or code repair. Ask which need justified the feature and which feature justified the data. Distinguish an unresolved business decision from an implementation fact to verify later.

No reliable core duration is established. Pilot request latency, review time, questions and learner intervention before setting a schedule.

Execution modes

If the plugin is unavailable, record the blocker and choose a desk walkthrough deliberately. Do not simulate tool receipts or mark it live.

Optional maker/developer extension

The maker-reference handoff card and individual recipes apply only if a separately prepared implementation extension is selected.

That extension needs its own tenant access, licenses, identities, advanced components, test harnesses and runtime rehearsal. Missing runtime packages do not block the HVE core, but they do block claims of an implemented solution.

Cleanup

Preserve learning evidence according to the approved training policy. Remove only exact test records/resources in the selected scope under a named owner. Never clear a shared environment or browser profile.

No public publication, real customer notifications, production writes or external tracker mutations are authorized.