Skip to content

Use Rootform where you review changes and write source. A Form remains the saved architecture evidence across these tools: GitHub presents its reports, CI retains it for reuse, and the Explorer provides an interactive view of it. Editor integrations help you author the Dialects and Policies that give that evidence meaning.

Choose your workflow

GitHub
Review architecture and Policy results in Job Summaries and optional PR comments; keep the Form and Explorer as artifacts.
Guide
VS Code
Write .rf.hcl with diagnostics, completion, hover, definitions and formatting.
Guide
Zed
Use the same Rootform authoring features in Zed.
Guide
Other CI/CD
Analyze completed evidence, retain Forms and reports, and apply an explicit Policy gate in GitLab, Azure Pipelines or another runner.
Guide

Start from the evidence you have

Plan and state exports are sources of evidence. A saved Form lets you reopen or compare the architecture without analyzing those inputs again. Rootform never runs Terraform or OpenTofu, executes providers, or contacts clouds during analysis. Unknown or ambiguous evidence stays explicit in the result.

For the review itself, follow Review a pull request. For source authoring, follow Edit Rootform source, then test and validate.