Enforcement

Type: Node / Governed Institutional Operation

Working Definition: Enforcement is a governed institutional operation that applies an authorized instrument, pursuant to an enforcement warrant, to compel, prevent, restrain, secure, or realize an outcome specified by a valid governing basis, for a grammar-tracked subject and, where they differ, a distinct target, within a stated Jurisdiction. Enforcement may respond to non-compliance, but it may also execute a Judgment, maintain a boundary, prevent a prohibited transition, or apply a rule-defined consequence before any voluntary-performance option ever existed.

Function in the Grammar: Enforcement is where a governing basis stops merely binding and starts bearing on a subject through an applied instrument. Many institutional relations can exist, and even be recorded as valid and binding, without Enforcement ever occurring: an Obligation's existence does not depend on whether any forum can or does enforce it, and a Judgment can be rendered, recorded, and appealed with no Enforcement operation following it. But Enforcement is not only a response to failure. A sentence executed on schedule, a protective order restraining conduct before anticipated harm, an access-control system denying an unauthorized request, and a rule engine rejecting a prohibited transition are all Enforcement even though no one first declined to comply voluntarily. What unifies these cases is not adversity but application: an authorized instrument is brought to bear to realize what a governing basis specifies.

Enforcement's governing basis and its enforcement warrant are not the same thing. A Judgment or Obligation may establish what is owed, owned, or prohibited without specifying which instrument may be used against it, who may use it, when it becomes available, how severe it may be, or what notice or cure must precede it. The warrant is the further disclosed basis that maps a trigger to a permitted instrument, actor, timing, and severity. These are analytically distinct roles, not necessarily separate instruments: a single Judgment may both establish liability and order execution, and a single statute may both prohibit conduct and authorize the automatic denial that enforces the prohibition. What matters is that both roles are filled and disclosed, whether by one document or two. A valid underlying basis does not by itself make every available instrument authorized against it.

The subject bound by the basis and the target the instrument is applied to are also not always the same thing. A debtor is the subject of a garnishment; the wages or account garnished are the target. A religious community is the subject of a confiscation finding; the basilica taken is the target. Subject and target commonly coincide, as when a suspended account holder is also the account suspended, and Enforcement does not require them to differ. But treating them as always identical lets an Authority to act against one subject silently extend to another person's property, conduct, or holdings.

Enforcement also requires its own grant of Authority, independently scoped even when it is conferred by the same office or provision that grants Authority to judge or decide. A forum that may judge a matter does not thereby acquire Authority to enforce its finding; the scope of each grant must be separately established, whether or not the two share a common source.

Enforcement depends on Power, the causal capacity to make an authorized attempt actually take effect, without being identical to it. Authorization, initiation, and effectiveness are three different questions. An Enforcement operation can be fully authorized and still be resisted, stayed, or fail outright; it can also be initiated and later found to have exceeded its warrant. Enforcement names the governed operation directed at an outcome, not the outcome's guaranteed arrival.

Finally, Enforcement need not be a single Act performed by one person at one moment. It may be a discrete Act, an extended sequence of Acts, a governed Procedure, a continuing restraint, or an authorized automated mechanism that initiates and applies an instrument without further human action once its conditions are satisfied.

Formal Grammar Representation

<enforcement> ::= Enforcement(
  id: <enforcement-id>,
  enforcer: <enforcer-ref>,
  subject: <subject-ref>,
  target: <target-ref>,
  underlying_basis: <governing-basis>,
  enforcement_warrant: <warrant-ref>,
  trigger: <trigger-condition>,
  instrument: <enforcement-instrument>,
  authority: Authority(<authority-id>),
  jurisdiction: Jurisdiction(<jurisdiction-id>),
  initiated_at: <time>
)

<enforcer-ref> ::= Agent | RoleOccupant acting for an Institution
                 | AuthorizedSystem | GovernedInstitutionalMechanism

<subject-ref> ::= Agent | Institution | Role | other governed actor
                | bound by the underlying basis

<target-ref> ::= Agent | Institution | artifact | account | property
               | document | resource | attempted transition or Act
               | other object the instrument is applied to
               | (may coincide with <subject-ref>)

<governing-basis> ::= Rule | Obligation | Commitment | Judgment | Decision
                    | Constitution | other disclosed basis capable of
                      specifying an outcome for the subject

<warrant-ref> ::= Rule | Judgment | Decision | Constitution
                | Procedure, where the governing grammar gives it
                  independent force to authorize the instrument
                | other disclosed basis that maps a trigger to a
                  permitted instrument, actor, timing, and severity

<trigger-condition> ::= Breach | non-satisfaction of a due Obligation
                      | non-compliance with a binding Judgment or Decision
                      | expiration of a compliance period
                      | an anticipated or ongoing condition a warrant
                        treats as warranting preventive or protective action
                      | a compound condition joining several disclosed facts
                      | other disclosed condition a warrant treats as
                        warranting enforcement

<enforcement-instrument> ::= seizure | confiscation | exclusion | suspension
                           | restraint | fine | compulsion | exile
                           | withholding | denial | injunction
                           | other authorized institutional means

Enforcement(ε) is well-formed when:
  ENFORCER(ε, a)
  SUBJECT(ε, x)
  TARGET(ε, y)
  SEEKS_TO_GIVE_EFFECT_TO(ε, g)
  WARRANTED_BY(ε, w)
  TRIGGERED_BY(ε, τ)
  INSTRUMENT(ε, m)
  GROUNDED_IN(ε, Authority(alpha))
  WITHIN(ε, Jurisdiction(D))
  INITIATED_AT(ε, t0)

Enforcement(ε) is authorized when, in addition:
  VALID(g, at: t0)
  VALID(w, at: t0)
  ESTABLISHED_UNDER(τ, g | w)
  WARRANTS(w, trigger: τ, instrument: m, against: x, upon: y, under: g)
  AUTHORIZES(Authority(alpha), a, EnforcementOperation(m))
  COVERS(Jurisdiction(D), subject: x, target: y, subject_matter: subject_matter(g))
  NO_ACTIVE_STAY(ε, at: t0)
  NO_APPLICABLE_EXCEPTION(x, g, at: t0)

  THEREFORE
    QUALIFIES_AS(ε, Enforcement)

Otherwise:
    PURPORTS_TO_BE(ε, Enforcement)   -- claimed or recorded as Enforcement,
                                          without attaining that standing

A trigger may itself be compound, with each conjunct established by a different determination rather than one instrument being read as evidence for every fact Enforcement requires:

TRIGGER_CONDITION(τ,
  AND(
    Fact_1,
    Fact_2,
    ...
  )
)

ESTABLISHED_BY(Fact_1, Determination_1)
ESTABLISHED_BY(Fact_2, Determination_2)

SATISFIES(τ, TriggerRequiredBy(w))
  iff every conjunct of τ is separately established

Semantic Constraints

The expression Enforcement(ε, a, x, y, g, w, τ, m, alpha, D, t0) is well-formed when an enforcer, subject, target, underlying basis, enforcement warrant, trigger, instrument, authority, jurisdiction, and initiation time are each identifiable. Whether ε is authorized requires further conditions the syntax cannot supply. A valid Judgment does not by itself make every available instrument authorized against the party it binds: ValidJudgment(g) does not entail AnyAvailableInstrumentIsAuthorized(m). A separate WARRANTS(w, ...) relation must connect this trigger, under this basis, to this instrument, against this subject, upon this target.

SUBJECT and TARGET may coincide, and most Enforcement examples involve a single party who is both. Where they differ, WARRANTS must independently cover each, and COVERS(D, ...) must independently reach both the subject and the target's location, holder, or domain. Authority to act against a subject does not by itself authorize an instrument applied to a target the warrant does not separately name.

Authority to enforce is not implied by Authority to judge, recognize, or decide, even when both are conferred by the same constitutional provision, office, or delegation event. The invariant is not that the two grants trace to separate documents; a single office may hold both. The invariant is that the scope of Authority to enforce must be independently established and cannot be inferred merely from possession of a related Authority over the same matter. The same non-numerical reading applies to g and w: one instrument may fill both roles, but a Procedure functions as a warrant only where the governing grammar gives that Procedure independent force to authorize the instrument. Absent that grant, a Procedure specifies how an already-warranted instrument is applied; it does not itself supply the warrant, and treating it as if it did launders authorization through process.

SEEKS_TO_GIVE_EFFECT_TO(ε, g) states which basis the operation is undertaken to realize. It does not by itself assert that g was realized. Once ε concludes, its relation to g becomes assessable rather than assumed: GIVES_EFFECT_TO(ε, g, extent: full), GIVES_EFFECT_TO(ε, g, extent: partial), or FAILS_TO_GIVE_EFFECT_TO(ε, g). OUTCOME(ε, ...) records the operation's procedural status, including values such as resisted, stayed, or reversed that are not reducible to extent of effect; the two are related but not identical.

Trigger establishment is itself conditional. Some warrants make τ determinable from an authoritative record, a record the governing basis or warrant itself gives trigger-establishing force, such as a missed filing deadline verified against the institution's own Ledger. An undisputed record is not automatically an authoritative one: silence or the absence of a challenge does not by itself confer that force. Other warrants require a prior Judgment or Recognition establishing that the claimed condition holds before Enforcement may proceed. Where τ is compound, each conjunct should be traced to its own establishing determination; a single instrument that establishes one conjunct should not be read as establishing the others.

A model or Agent proposing Enforcement(ε, ...) must not manufacture Authority, Jurisdiction, a warrant, a target, or a satisfied trigger by filling the corresponding slots with plausible labels. QUALIFIES_AS(ε, Enforcement) holds only where the authorized conditions above are met; otherwise the operation PURPORTS_TO_BE(ε, Enforcement) without attaining that standing, however an institution describes or records it. The failure modes below concern purported operations of this kind.

Formal Pattern

Enforcement(ε, enforcer: a, subject: x, target: y, underlying_basis: g,
            enforcement_warrant: w, trigger: τ, instrument: m,
            authority: alpha, jurisdiction: D, initiated_at: t0)

INITIATES(Agent(a) | AuthorizedSystem(a), ε, at: t0)
APPLIES_INSTRUMENT(ε, m, to: y)
SEEKS_TO_GIVE_EFFECT_TO(ε, GoverningBasis(g))
WARRANTED_BY(ε, Warrant(w))
TRIGGERED_BY(ε, TriggerCondition(τ))
RECORDED_IN(ε, Ledger(L))                         -- when required
CHALLENGED_BY(ε, Challenger(c))                   -- optional
STAYED_BY(ε, AuthorizedOrder(o))                  -- optional
REVERSED_BY(ε, AuthorizedDecision(d))              -- optional

EFFECTIVE_AT(ε, t1)                                -- when and if successful
COMPLETED_AT(ε, t2)                                -- when applicable
OUTCOME(ε, effective | partial | resisted | failed | stayed | reversed)
GIVES_EFFECT_TO(ε, g, extent: full | partial)      -- assessed, not assumed
FAILS_TO_GIVE_EFFECT_TO(ε, g)                      -- alternative to the above
PRODUCES(ε, Transformation(θ1) ... Transformation(θn))
HAS_CONSEQUENCE(ε, c1) ... HAS_CONSEQUENCE(ε, cn)

Some listed instruments occupy different grammatical roles depending on the case rather than always naming the Enforcement instrument itself. An injunction is usually a Judgment, order, or warrant that a later contempt proceeding, restraint, or seizure enforces. A fine may be a decided Consequence, with assessment and collection as separate Enforcement operations. Exile is commonly the resulting status; an expulsion or banishment order is the instrument. A retraction may be a correction-producing Decision and Transformation rather than Enforcement, while barring an author from future submission is more clearly Enforcement. The grammatical role a term occupies must be checked against the particular case, not assumed from the word.

Three common sufficient patterns show how a trigger may be established and how an operation may be executed, as separate axes. They are not exhaustive biconditionals or a mandatory workflow.

Judgment-dependent, Act-executed enforcement:
  VALID(g, at: t0); VALID(w, at: t0)
  Judgment(j) establishes TRIGGERED_BY(ε, τ)
  WARRANTS(w, trigger: τ, instrument: m, against: x, upon: y, under: g)
  AUTHORIZES(Authority(alpha), a, EnforcementOperation(m))
  COVERS(Jurisdiction(D), x, y, subject_matter(g))
  PERFORMS(Agent(a), Act(initiate_and_apply(m)))

  THEREFORE
    INITIATES(a, ε, at: t0); APPLIES_INSTRUMENT(ε, m, to: y)

Automatically triggered, Act-executed enforcement:
  VALID(g, at: t0); VALID(w, at: t0)
  AuthoritativeRecord(rec) establishes TRIGGERED_BY(ε, τ) without a
    separate finding
  WARRANTS(w, trigger: τ, instrument: m, against: x, upon: y, under: g)
  AUTHORIZES(Authority(alpha), a, EnforcementOperation(m))
  COVERS(Jurisdiction(D), x, y, subject_matter(g))
  Agent(a) still performs a distinct Act to initiate and apply m

  THEREFORE
    INITIATES(a, ε, at: t0); APPLIES_INSTRUMENT(ε, m, to: y)

Automatically triggered and automatically executed enforcement:
  VALID(g, at: t0); VALID(w, at: t0)
  Rule evaluation establishes TRIGGERED_BY(ε, τ)
  WARRANTS(w, trigger: τ, instrument: m, against: x, upon: y, under: g)
  AUTHORIZES(Authority(alpha), AuthorizedSystem(s), EnforcementOperation(m))
  COVERS(Jurisdiction(D), x, y, subject_matter(g))
  NO_ACTIVE_STAY(ε, at: t0); NO_APPLICABLE_EXCEPTION(x, g, at: t0)

  THEREFORE
    INITIATES(s, ε, at: t0); APPLIES_INSTRUMENT(ε, m, to: y)

The rule engine executes what the warrant specifies. It does not confer the underlying status, invent the trigger, or supply Authority the warrant does not disclose. A structural or physical arrangement that blocks an outcome without performing this evaluation is not itself this pattern; see Distinctions, Enforcement ≠ Constraint.

Core Relations

Typical Questions

• What underlying basis does this Enforcement operation seek to give effect to, and is it still valid and in force?
• What enforcement warrant connects this trigger to this specific instrument, separate from any general Authority the enforcer holds, and is that warrant itself independently authorized if it is a Procedure?
• Which Agent, role-occupant, or authorized system enforces, and does their Authority specifically extend to this instrument?
• Is the subject bound by the basis the same party as the target the instrument is applied to? If not, does the warrant independently cover the target?
• Does the enforcing Institution's Jurisdiction cover this subject, this target, and this subject matter?
• What triggering condition is asserted, is it compound, and was each part established through a Judgment, a Recognition, or an authoritative record?
• Was the operation initiated, and did it actually give effect to the basis in full, in part, or not at all?
• Is the enforcement instrument proportionate to the trigger under the governing basis and warrant?
• Has the Enforcement operation been recorded in the Ledger?
• Can the subject appeal, resist, or obtain a stay of this Enforcement operation?
• Is Enforcement being treated as automatic from the mere existence of harm, Breach, or an unfulfilled Obligation, without a warrant connecting them?
• Is Authority to judge, recognize, or decide being treated as if it already includes Authority to enforce?
• Is Enforcement being equated with coercion, punishment, or mere structural constraint when the governing basis characterizes it differently?
• Does this operation actually qualify as Enforcement, or does it only purport to?
• Has a Waiver released the underlying claim, making a proposed Enforcement operation unwarranted?

Examples

Distinctions

Enforcement ≠ Consequence. Consequence is the general relation between a source and whatever follows from it, whether or not any institution authorized or intended the connection. Enforcement is the narrower case: an authorized institutional operation performed to give effect to a governing basis. A confiscation is Enforcement and also has further Consequences, including ones the enforcing institution never intended, such as a strengthened resistance identity within the community it confiscated from. Treating the confiscation and its downstream effects as one relation erases that only the first is authorized institutional action.

Enforcement ≠ Power. Power is the factual capacity to produce effects, whether or not that capacity is authorized. Enforcement is the authorized institutional operation; it requires Power to take effect but is not identical to that capacity. A forum may hold clear Authority to enforce a Judgment and lack the Power to make compliance happen, producing failed or partial Enforcement. An actor may have the Power to seize property and lack any Authority that makes the seizure Enforcement rather than force.

Enforcement ≠ Constraint. A constraint limits what can occur through structure, design, or physical arrangement, without evaluating a case under an authoritative rule. Enforcement applies a governing basis to a particular subject, target, act, or attempted transition through a rule-governed determination. A wall constrains movement; a missing software feature limits possibility; neither is Enforcement merely because it prevents something. A validation gate counts as Enforcement when it encounters an attempted transition, evaluates it under an authoritative rule, applies a rule-authorized instrument or denial, and produces an institutionally legible result. A technical impossibility with none of that evaluative structure remains a constraint.

Enforcement ≠ Coercion. Coercion is the use or threat of pressure, restraint, deprivation, or force to alter conduct. Enforcement is a governed institutional operation applying an authorized instrument. Enforcement may be coercive, but it need not be, and coercion may occur without any valid Enforcement Authority. A validation gate that rejects an unauthorized transition is Enforcement without coercing a person. A private threat used to force compliance is coercion without Enforcement. An authorized confiscation is both.

Enforcement ≠ Punishment. Punishment imposes deprivation or condemnation in response to attributed wrongdoing. Enforcement may instead be remedial, preventive, protective, restitutive, or compliance-seeking, and it need not rest on any finding of wrongdoing at all. A seizure satisfying a civil Judgment is remedial rather than punitive. A blocked unauthorized request is preventive. A suspension may be protective, punitive, or both, and the governing basis, not the mere fact of Enforcement, determines which.

Enforcement ≠ Judgment or Decision. Judgment settles what claims, evidence, or interpretations establish. Decision selects a course, disposition, or response. Either may ground the underlying basis Enforcement later gives effect to, but a Judgment can be rendered, recorded, and even appealed with no Enforcement operation ever following it. A court's finding of liability is a Judgment; the garnishment that satisfies the resulting award is the Enforcement.

Enforcement ≠ Accountability. Accountability is the continuing relation of answerability, whether or not the answerable Agent's conduct ever becomes the subject of an authorized response. Enforcement is one possible authorized response. An enforcing Agent remains accountable for whether an Enforcement operation was authorized and proportionate; that accountability relation does not itself enforce anything, and performing an Enforcement operation does not discharge the accountability owed for having performed it.

Enforcement ≠ Repair. Enforcement gives effect to a governing basis directed at a governed subject, target, act, condition, or attempted transition. Repair is a purpose-directed Process addressing an acknowledged institutional failure, defect, or injury. An institution may enforce rules against its own officers, employees, organs, and members just as it enforces them against outside parties; Enforcement's subject need not be external to the enforcing institution. Repair may itself include Enforcement operations, but the two are distinguished by their governing purpose, not by the direction of time or the location of the subject: an Enforcement operation the institution later finds was disproportionate, unauthorized, or mistaken is itself a failure that may require Repair, while the Enforcement operation and the Repair that answers it remain distinct acts with distinct authorizations.

Enforcement ≠ Breach. Breach is a status: the finding that a bearer failed to satisfy an applicable Obligation. Enforcement is an operation: the authorized institutional response a warrant may make available once Breach, or another disclosed condition, is established. A Breach can be found and recorded in the Ledger with no Enforcement ever following it, if no forum holds the further Authority to enforce or the beneficiary chooses Waiver instead.

Enforcement ≠ Obligation. An Obligation's existence and binding force depend on its own governing basis; they do not depend on whether any forum can or does enforce it. An Obligation with no available enforcement mechanism still binds its bearer, and an institution that purports to enforce an invalid or inapplicable Obligation has performed an unauthorized operation, not proof that the Obligation was genuine.

Common Failure Modes

The modes below concern operations that purport to be Enforcement. Where the warrant, Authority, Jurisdiction, subject, target, or triggering conditions fail, the operation does not attain valid Enforcement standing, however an institution describes or records it.

Minimum Viable Test Case

The following instantiates the operative structure of the 313–321 Donatist episode for grammatical analysis. It is a stylized reconstruction: it does not assume that every represented condition appeared in a single surviving instrument, only that the roles below (basis, warrant, trigger, target, authority) were each filled by some determination in the historical record.

Confiscation and exile were separately authorized operations descending from the same imperial policy. Splitting them keeps each separately testable rather than treating exile as a mere consequence of the confiscation.

g = EcclesialDetermination_Arles314
    (the council's finding that Caecilian's communion is the recognized
    Catholic Church and the Donatist communion is schismatic)
w = ImperialEnforcementRescript_317
    (a rescript warranting confiscation of disputed church property, and
    separately, removal of resisting clergy, once the compound trigger
    below is established)

x = DonatistCommunity_Carthage        -- subject of ε1
τ1 = TRIGGER_CONDITION(τ1,
       AND(
         EcclesialStatus(x, OutsideRecognizedCommunion),
         ContinuedPossession(x, Basilica_p)
       ))
ESTABLISHED_BY(EcclesialStatus(x, OutsideRecognizedCommunion), g)
ESTABLISHED_BY(ContinuedPossession(x, Basilica_p), AdministrativeFinding_317)
SATISFIES(τ1, TriggerRequiredBy(w))

a = ProvincialGovernor
alpha = Authority(ImperialDelegation, office: provincial_administration)
D = Jurisdiction(RomanNorthAfrica, subject_matter: disputed_church_property)
t0 = 317_CE

ε1 = Enforcement_Confiscation
ENFORCER(ε1, a)
SUBJECT(ε1, x)
TARGET(ε1, Basilica_p)
SEEKS_TO_GIVE_EFFECT_TO(ε1, g)
WARRANTED_BY(ε1, w)
TRIGGERED_BY(ε1, τ1)
INSTRUMENT(ε1, Confiscation)
GROUNDED_IN(ε1, alpha)
WITHIN(ε1, D)
INITIATED_AT(ε1, t0)

WARRANTS(w, trigger: τ1, instrument: Confiscation, against: x,
         upon: Basilica_p, under: g)
AUTHORIZES(alpha, a, EnforcementOperation(Confiscation))
COVERS(D, subject: x, target: Basilica_p, subject_matter: disputed_church_property)

EFFECTIVE_AT(ε1, 317_CE)
OUTCOME(ε1, effective)
GIVES_EFFECT_TO(ε1, g, extent: full)
PRODUCES(ε1, Transformation(θ1))   -- Basilica_p: held by x → held by recognized communion
HAS_CONSEQUENCE(ε1, strengthened_martyr_identity_within_x)

ε2 = Enforcement_ClergyRemoval
ENFORCER(ε2, a)
SUBJECT(ε2, ResistingClergy_p)
TARGET(ε2, ResistingClergy_p)          -- subject and target coincide here
SEEKS_TO_GIVE_EFFECT_TO(ε2, g)
WARRANTED_BY(ε2, w)
TRIGGERED_BY(ε2, τ1)
INSTRUMENT(ε2, Exile)
GROUNDED_IN(ε2, alpha)
WITHIN(ε2, D)
INITIATED_AT(ε2, t0)

WARRANTS(w, trigger: τ1, instrument: Exile, against: ResistingClergy_p,
         upon: ResistingClergy_p, under: g)
AUTHORIZES(alpha, a, EnforcementOperation(Exile))
COVERS(D, subject: ResistingClergy_p, target: ResistingClergy_p,
       subject_matter: disputed_church_property)

OUTCOME(ε2, effective)
GIVES_EFFECT_TO(ε2, g, extent: full)
HAS_CONSEQUENCE(ε2, loss_of_local_ministry)

Result:
  ε1 and ε2 are each well-formed and authorized: a enforces under a
  traceable Authority, within a Jurisdiction covering the relevant
  subjects and targets, applying an instrument a warrant connects to a
  compound trigger whose conjuncts trace to distinct determinations.
  Neither ε1 nor ε2 settles whether g was ever Recognized within the
  Donatist community's own grammar. The same operations count there as
  persecution, not lawful correction.
  In 321, a later directive suspends the warrant for future operations:
    SUSPENDS(TolerationDirective_321, w, for_future_operations: true)
  This does not retract g, and it does not by itself determine whether
  ε1 or ε2 were valid when performed. That question requires examining
  w, alpha, and D as they stood at t0, not the later directive. What the
  later directive changes is only whether w continues to warrant further
  operations after 321.

Failure case:
  A provincial official, citing the same rescript w, seizes property
  belonging to a person not named by the warrant and not a party to the
  ecclesial determination g addresses.
  COVERS(D, unrelated_subject, unrelated_property) = false
  WARRANTS(w, τ1, Confiscation, against: unrelated_subject,
           upon: unrelated_property, under: g) = false
  The official holds real Power and a general office; the seizure changes
  possession. It does not QUALIFY_AS Enforcement under w; it only
  PURPORTS_TO_BE Enforcement. It is wrong-target enforcement, unambiguously
  outside the stated grammar, whatever domain the official's own
  institution claims for it.

Cross-References

Required

• Authority: determines which Agent may perform which enforcement instrument; Enforcement without a traceable, independently scoped Authority is unauthorized force
• Jurisdiction: bounds the subjects, targets, subject matter, and territory within which an Enforcement operation may validly operate
• Institution: the body within which Enforcement is authorized, recorded, and made answerable
• Rule, Obligation, Judgment, and Decision: distinct kinds of governing basis Enforcement may give effect to; a Rule, Judgment, Decision, Constitution, or independently empowered Procedure may separately serve as the enforcement warrant that maps a trigger to a permitted instrument

Consequential

• Consequence: Enforcement produces effects that are Consequences, but not every Consequence is Enforcement
• Breach: a common triggering condition, though Enforcement may respond to other disclosed conditions a warrant treats as warranting it, including compound and preventive ones
• Power: the causal capacity that may or may not carry out an authorized Enforcement operation; Power without Authority is not Enforcement
• Accountability: may examine whether an Enforcement operation was authorized, warranted, and proportionate without itself constituting Enforcement
• Repair: addresses acknowledged institutional failure, including a disproportionate or unauthorized Enforcement operation, through acknowledgment and restoration
• Waiver: the authorized non-enforcement or relinquishment of a claim in a specific instance, distinct from an Enforcement operation
• Appeal: may challenge, stay, or seek to suspend an Enforcement operation through a separately grounded appellate Authority and Jurisdiction
• Transformation: a single Enforcement operation may produce several, even contrary, Transformations across different institutions' grammars

Evidential

• Ledger: should preserve the enforcing Agent, Authority, underlying basis, warrant, trigger, subject, target, and instrument so a later actor can reconstruct whether the operation was authorized
• Recognition: may establish or attest the triggering condition an Enforcement operation responds to
• Claim and Evidence: support or contest the asserted trigger and the governing basis's continued validity