An estate is any real OpenTofu or Terraform configuration, pinned by tag or commit. Adding one is a manifest entry and a script, and the site picks it up on the next run.

go run ./tools/gauntlet add <name> <repo-url> <tag-or-commit> -lane <lane> [-core -reason "..."] -source "<one line>"

That writes the entry and a script stub at live/e2e/<name>/run.sh with every stage wired to the protocol and marked not_run. Fill the stub in, using the script of a similar estate as the template (live/e2e/corpus-vpc-complete/run.sh is the fullest), then:

go run ./tools/gauntlet run <name>     # runs it against the emulator, records verdicts
go run ./tools/gauntlet render         # regenerates the artifact and these pages

Commit the entry, the script, live/gauntlet.json and the rendered pages. CI runs the same two commands nightly.

Lanes: terraform-popular, opentofu-native, reference, published-deployment. A -core estate needs -reason; the rule for the core set is in live/GAUNTLET.md.

A manifest entry looks like this:

{
  "name": "corpus-alb-complete",
  "source": "terraform-aws-modules/terraform-aws-alb examples/complete-alb (tag v9.9.0), its flagship application-load-balancer example",
  "url": "https://github.com/terraform-aws-modules/terraform-aws-alb.git",
  "pin": "v9.9.0",
  "lane": "terraform-popular",
  "set": "core",
  "reason": "a most-downloaded terraform-aws-modules example, pinned by tag; the shape most people deploy"
}