# Quickstart Open a sample Form in the Explorer, find one resource, and read the evidence behind its placement, then run the same analysis on your machine. Open a synthetic Azure commerce platform of 153 planned resources in the Explorer, find one resource, and read the evidence behind its placement. The first half needs only a browser; the second half installs Rootform and produces the same result on your machine. Rootform turns a Terraform or OpenTofu plan, or a state export, into a [Form](https://docs.rootform.dev/concepts/forms/): a portable saved result you can explore, explain, compare, and check. The Explorer is the Form's interactive view. Nothing here runs Terraform, since the sample plan is already exported. ## Open the sample Form Open the [Playground](https://rootform.dev/playground/) and keep **Commerce platform** with **Plan** selected. The canvas shows the top level of the planned architecture: four resource groups, the relations between them, and a few resources that no group holds. ![The Explorer at the top level of the commerce platform plan: four resource group blocks with their object counts, relation labels such as Peers with and Delivers to, and the Planned changes selector](https://docs.rootform.dev/images/explorer/quickstart-overview-light.webp#gh-light-mode-only) ![The Explorer at the top level of the commerce platform plan: four resource group blocks with their object counts, relation labels such as Peers with and Delivers to, and the Planned changes selector](https://docs.rootform.dev/images/explorer/quickstart-overview-dark.webp#gh-dark-mode-only) The selector at the top left reads **Planned changes**, Refreshed to Planned: this plan starts from an empty state, so everything it proposes is added. The counters at the bottom count the added, removed, and changed entries, and the placements the evidence could not settle. ## Find one resource Press **Search** (`⌘K` on macOS, `Ctrl+K` elsewhere) and type `prod_data`. The first result is the subnet `azurerm_subnet.prod_data` with its path `prod / prod`: resource group `prod`, virtual network `prod`. Choose it, and the Explorer opens the virtual network that holds the subnet. Select the **prod_data** card to open the Inspector on the right. ## Read why it is placed there In **Details**, **Contexts** lists two placements: Ownership in resource group `prod` and Network in VNet `prod`. **Incoming contexts** lists the six private endpoints placed in this subnet; **Scene members** counts them. Open the **Evidence** tab. Under **Evidence**, the entry `azurerm_subnet.prod_data → azurerm_virtual_network.prod` is the network placement. Expand its **Resolution**: it names the Rule `azure.rule.subnet`, the attribute it followed, `source.virtual_network_name`, and the kind of evidence that settled it. The resolved outcome establishes this placement. ![The Evidence tab for azurerm_subnet.prod_data: evaluated value and verified traversal, the resolved outcome, and both placement closures with their candidate counts](https://docs.rootform.dev/images/explorer/quickstart-evidence-light.webp#gh-light-mode-only) ![The Evidence tab for azurerm_subnet.prod_data: evaluated value and verified traversal, the resolved outcome, and both placement closures with their candidate counts](https://docs.rootform.dev/images/explorer/quickstart-evidence-dark.webp#gh-dark-mode-only) That one fact carries the whole idea. Rootform did not draw the subnet inside the VNet because Terraform references it: a Rule in the Azure [Dialect](https://docs.rootform.dev/concepts/dialects/) declares what the reference means, and the plan evidence proved it. [Trace a placement](https://docs.rootform.dev/getting-started/first-architecture/) explains how producer references become architectural facts and what incomplete evidence changes. ## Run the same analysis locally [Install Rootform](https://docs.rootform.dev/installation/), then download the two files that produced this Form: the plan JSON export and the saved plan it was exported from. ```sh mkdir rootform-quickstart && cd rootform-quickstart curl -fsSLO https://raw.githubusercontent.com/rootform-dev/rootform/v0.1.0-pr.117.1/examples/playground/commerce-platform/head/plan.json curl -fsSLO https://raw.githubusercontent.com/rootform-dev/rootform/v0.1.0-pr.117.1/examples/playground/commerce-platform/head/plan.tfplan ``` Analyze the plan. Rootform reads both files, prints a summary, and opens the Explorer in your browser from a local server: ```sh rootform run plan.json --plan-file plan.tfplan ``` ```ansi title="Run output excerpt" Plan analyzed Enrichment Saved plan paired with this plan JSON (1 module) Stage Planned Architecture Instances 153 Interpreted 153 Contexts 207 ``` The terminal also shows the Explorer address; press `Ctrl+C` when you are done. **Enrichment** records that the saved plan paired with the JSON export, which is how Rootform followed references whose values are unknown until apply. **Instances** counts the resource instances in the plan, and **Interpreted** counts those a Rule matched: all 153 here. The 207 contexts are placements like the one you just read. ## Keep the Form Write the Form to a file instead of serving it: ```sh rootform run plan.json --plan-file plan.tfplan --no-serve -o analysis.json ``` ```ansi title="Saved Form excerpt" Wrote  analysis.json ``` `analysis.json` reopens with `rootform run analysis.json` without the plan files. [Explain an architecture](https://docs.rootform.dev/guides/explain-architecture/) questions it from the terminal, [Check a Form with Policies](https://docs.rootform.dev/guides/check-with-policies/) evaluates Policies against it, and [Compare two Forms](https://docs.rootform.dev/guides/compare-architectures/) sets it against another revision. It holds no sensitive plan values, but it names resources and describes topology. Next, move to your own files with [Analyze your plan or state](https://docs.rootform.dev/getting-started/analyze-your-plan/), or stay with this sample in [Explore a Form](https://docs.rootform.dev/guides/explore-architecture/).