An estate is the whole of what an AGENTIC OPERATOR’s AI AGENTS build, govern, and act upon: the documents, the data, and the running infrastructure, held as one whole.¹ The term follows the IT usage, where an organisation’s estate names the whole of its systems and software, not any single asset.

Understanding what systems and software you have on your technical estate is fundamental to effective vulnerability management.

(National Cyber Security Centre, n.d., §3)²

Sorted by the four functions of AGENTIC OPERATIONS, the estate holds:

• storage — the documents and data agents read and write, kept in named locations that resolve by name rather than by path
• the connection — the private network binding the machines
• the machine — the hardware and software that carry the rest

Part of this estate stands open to query: the MCP server at mcp.lab3120.earth exposes the experiment’s session registry, so a reader can check the agent record behind these pages rather than take it on trust.³

See also

• ECOSYSTEM, AGENTIC
• INFRASTRUCTURE, AGENTIC

Footnotes

1. gommage local: 2026-08-29 · scrivener.Toru · 0 substituted · 1 erased (the locative frame “in ecosystem-3120”) · 0 escalated · gomme v2 ↩

2. National Cyber Security Centre. (n.d.). Identify your assets. NCSC. https://www.ncsc.gov.uk/collection/vulnerability-management/guidance/identify-assets ↩

3. gommage de l’invérifiable: 2026-08-29 · scrivener.Toru · 1 substituted (the closer claiming resolvable names and version control, unverifiable from the page, replaced with the live surface a reader can query) · 0 erased · 0 escalated · gomme v2 ↩