Home / The model / The universes / The enforcement

U4: The enforcement

Owner whoever set the control: the vendor, the platform, the deployer or nobody. Centre of gravity the enforcer. Smallest node one configuration line at one layer, set by one party, on one date. Level across. Status one edge deep.

Four barriers, three enforcers, one Control formula that the gate walks on every build. The formula is the most important thing on the site and it lands in a world with three nodes. The dev brief of 11 September on the prohibition's two lives wrote most of this universe's vocabulary and it was never made into nodes.

Node types

A node type is a required pattern of paths, not a label. The ones marked yes are walked on every build and the count is what matched; the rest are the vocabulary this universe needs and does not have.

TypeFormulaExists todayNote
Barrier[Barrier] := a node that -bounds-> at least one [GrantedCapability]yes, 4 matched
Enforcera node that -enforces-> at least one [Barrier], -set_by-> a [Party], -at_layer-> a [Layer]yesThree today, with only inside_the_grant on each. Party and Layer are the change.
Control[Control] := a [Barrier] that is -enforced_by-> an [Enforcer] the [Grant] does not includeyes, 1 matchedDoes not change, and gains a second reading: with Party and removable_by as nodes and edges, does not include becomes a path, walked one universe further.
Layerone of prompt, tool schema, client rule, gateway, sandbox; a node a [Layer] is -above-> or -below-> anothernot yet
Partythe vendor, the platform, the deployer, the administrator, the agent's own account, or nobodynot yet
EvidencedControla [Control] whose [Enforcer] is -backed_by-> an [Observation] in U3not yetThe regulated customer's stricter formula from the three layers page, now writable beside ours without touching ours.
CompiledRulea node that a [Prohibition] in U7 -compiles_to->, in a named target language, that -passes-> a shadowed permit analysisnot yet

Verbs

Each is a verb with a distinct inverse, a stated domain and range, and the sentence it reads as. The ones marked live are in the edge vocabulary today; the rest are proposed here, or declared by the universe's owner elsewhere, and say so.

EdgeReads asInverseReads asDomainRangeFromStatus
enforced_bythis barrier is enforced by something above the grantenforcesthis enforcer enforces these barriersBarrierEnforcerthis sitelive
set_bythis enforcer was set by this partysetsthis party sets these enforcersEnforcerPartyproposed hereproposed
at_layerthis enforcer sits at the gateway layerlayer_ofthe gateway layer is the layer of these enforcersEnforcerLayerproposed hereproposed
removable_bythis enforcer can be removed by this partycan_removethis party can remove these enforcersEnforcerPartyproposed here; the enforcer test as an edgeproposed
expires_onthis enforcer is good until this date, or has no stated expiryexpiry_ofthis date is the expiry of these enforcersEnforcerDateproposed hereproposed
compiles_tothis prohibition compiles to this rulecompiled_fromthis rule is compiled from this prohibitionProhibitionCompiledRuleproposed hereproposed
defeated_bythis barrier was defeated in this observationdefeatsthis observation defeats this barrierBarrierObservationgraphs.sgit.ai edge setproposed

The edges that cross its boundary today

Arrives alongFrom
bounded_byThe grant and its evidence
movesThe deployment shape

What the map adds here

Lab 06 added the property the 11 September brief did not have: a barrier is perishable, and a classifier that refuses a probe today is a barrier with no row and no expiry. The five layers become nodes so that the leaflet's rightmost column, the layer a control would sit at, stops being a string.

U3: The grant and its evidence · All thirteen · U5: The deployer · This universe as JSON · The brief