# Enclosure **Domain:** Architecture / Governance / Systems **Doc Type:** Bridge Concept **Maturity:** Developed ## Definition An **enclosure** is a bounded environment within which actors, resources and interactions acquire structured conditions. Its defining feature is not total isolation but controlled relation between inside and outside. ## Historical Lineage Fields, walls, houses, workshops, institutions and protected habitats use enclosure to concentrate resources, stabilize conditions and assign responsibility. Enclosure can shelter and coordinate; it can also dispossess, confine or make a population newly manageable. ## Governing Variable Enclosure governs permeability: what may enter or leave, by which route, under whose authority and with what change of status. ## Material and Computational Manifestation Walls, fences, roofs, gates and service boundaries form physical enclosures. Sandboxes, namespaces, network segments and permission domains form computational enclosures. [[wiki/Cyber-Physical Enclosure|Cyber-Physical Enclosure]] joins the two when identity, sensing and actuation participate in maintaining the boundary. ## Relation to Governance Enclosure turns an abstract [[wiki/Boundary|boundary]] into an environment that can preserve a selected internal state. [[articles/Cyber-Physical Lessons from Imperial Beekeeping|Cyber-Physical Lessons from Imperial Beekeeping]] uses the hive box as a control case: protection and management can be properties of the same architecture. ## Constitutional Question and Failure Modes Who may revise the enclosure, inspect its inhabitants, withhold its resources or permit exit? Protective enclosures become coercive when dependency removes meaningful exit, boundaries are opaque or those inside cannot contest the conditions that keep the system viable. ## Related Ontology [[wiki/Boundary|Boundary]] · [[wiki/Threshold|Threshold]] · [[wiki/Property|Property]] · [[wiki/Built Environment|Built Environment]] · [[wiki/Cyber-Physical Enclosure|Cyber-Physical Enclosure]]