Estate Query Quality: 18 tests: 18 passed, 0 failed, 0 skipped, 20 of 20 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the libraryEstate Query: its three layers as namespaces.#Entry pointssrc/mod.tssrc/governance/mod.tssrc/logical/mod.tssrc/physical/mod.ts#Modulesgovernance/modThe Governance layer of Estate Query: what the relations of an estate are.governance/relationsThe relations of an estate, as data: each has a name, a sentence, and columns with a type and a sentence.governance/osqueryThe tables of osquery that a question over the live fleet may name, as data: each is an allow-list of the columns that may be read, so that the text sent to a machine is made here from these names…logical/modThe Logical layer of Estate Query: the relations built from what an estate holds, and the question asked of them.logical/dataWhat an estate holds, in the shapes of the estate library, and the relations built from it.logical/queryAsking the estate a question in SQL: one statement that only reads, refused with every reason before anything runs, bound to the catalog of the relations (an unknown table or column is said with the…physical/modThe Physical layer of Estate Query: the estate as the connection of the sql runner of grc, so that a policy is a question in SQL.physical/checksPolicy as SQL: a check of the grc library whose question is a query over the estate (a check passes where its query gives no row, or whatever else it expects of the rows), run by the sql runner…physical/liveAsking the machines of a fleet at once, read only: for each machine and each table a question names, the SELECT made from the list of tables is sent through the way of reaching a machine that the…