1# Scaffold & Parameterize
2 
3Use this reference to fetch the confirmed template and wire up parameters.
4 
5## Path A — OFFICIAL / ADAPT
6 
7If the user has no GitHub access, the template must already be present in the workspace. Do NOT attempt to fetch from GitHub.
8 
9Fetch the template from the GitHub URL in [template-index.md](template-index.md). Choose **Bicep or Terraform** based on the user's preference or existing workspace files. Fetch the **entire template folder** including subdirectories. Create the files in the user's workspace (e.g., `infra/` folder).
10 
11For ADAPT: after fetching, modify the template to match the user's requirements before parameterizing.
12 
13## Path B — EXTEND
14 
15If the user has existing Bicep or Terraform templates they want to extend, load [custom-template-adaptation.md](custom-template-adaptation.md). Follow the gap analysis there: read the user's template, identify what's present, add only the missing mandatory resources.
16 
17Set parameter values using the answers collected in [intake.md](intake.md):
18 
19| Parameter | Source |
20|-----------|--------|
21| Location | Region (or inferred from existing VNet) |
22| VNet name / resource ID | VNet answer (new or existing) |
23| VNet address space | Address space from requirements (default `192.168.0.0/16`) |
24| Subnet CIDRs | Subnet answers (agent `/24`, PE `/24`, MCP `/24` if needed) |
25| Existing Cosmos DB / Storage / AI Search IDs | BYO resource IDs (only if reusing) |
26| Isolation mode (T18 only) | Managed VNet outbound mode (`AllowOnlyApprovedOutbound` or `AllowInternetOutbound`) |
27| Model name, version, format | Model selection from requirements |
28| `disableLocalAuth` | Set `true` if Azure Policy requires it |
29 
30> Do NOT run `az deployment group create` yet — validate first (next step).
31