Estate Iac Quality: 14 tests: 14 passed, 0 failed, 0 skipped, 15 of 15 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the libraryEstate Iac: its three layers as namespaces.#Entry pointssrc/mod.tssrc/governance/mod.tssrc/logical/mod.tssrc/physical/mod.ts#Modulesgovernance/modThe Governance layer of Estate Iac: what an importer gives, as data.governance/modelWhat an importer gives: assets and links of the estate, each asset with where it came from.logical/modThe Logical layer of Estate Iac: the importers, which read the text of a file, and the comparison of the code with a cloud.logical/cloudformationCloudFormation: a template, as JSON or as YAML without the short-form tags (!Ref and the others are tags, which the YAML reader refuses; aws cloudformation get-template and cfn-flip --json give…logical/composeCompose files: every service is an application with its image, an endpoint for each port it publishes (open to the internet where it is published on all interfaces, internal where it is published on…logical/kubernetesKubernetes manifests: one YAML text with documents separated by ---.logical/terraformOpenTofu and Terraform: the JSON of show -json for a plan or for a state, read as text.logical/pulumiPulumi: the JSON of pulumi stack export.logical/detectWhich importer reads a file: by what is in it, since a name says little (plan.json, stack.json, main.yaml).logical/driftDrift between what the code says and what a cloud shows.physical/modThe Physical layer of Estate Iac: reading the files the importers are given.physical/filesReading files for the importers: a path that is a file is read and must be one an importer reads; a path that is a folder is walked, and a JSON or YAML file in it that no importer reads is skipped…