Methodology enforcement is constraining

Type: kb/types/note.md · Tags: learning-theory, constraining

Methodology enforcement is constraining because it commits choices about when a requirement applies and what consequences follow. These are separate operative parts. An activation rule constrains which events invoke the requirement. A response rule constrains which interpretations or outputs count as satisfying it. An enforcement design can commit either part without committing the other.

This makes enforcement strength a partial order, not an inherent instruction → skill → hook → script ladder. Those names describe different packages and runtime surfaces. A skill can preserve the same natural-language procedure as an instruction while adding more reliable discovery or explicit invocation. A hook can attach a fixed trigger to an interpreted warning or to a symbolic rejection. A deterministic command can assign exact consequences yet remain optional because nothing requires it to run.

Surface Activation Response Remaining latitude
Routed instruction A model or human decides that the rule applies A model or human interprets the guidance Both applicability and compliance remain open to interpretation
Explicitly invoked skill Invocation is fixed for that run The skill body is usually interpreted natural language Invocation is settled, but compliant execution may still vary
Event hook with a warning A runtime assigns the triggering event A model or human interprets the warning and chooses a repair Detection is fixed; response and recovery remain open
Event hook with a rejection A runtime assigns the triggering event The attempted operation is rejected Detection and blocking are fixed; repair remains open
Optional validator or command A caller decides whether it runs A formal consumer assigns consequences to the encoded rule The checked predicate is fixed, but coverage depends on invocation
Required validator or command A runtime requires it at the relevant boundary A formal consumer assigns consequences to the encoded rule Both activation and the encoded acceptance condition are fixed

The table classifies configured combinations, not artifact types in isolation. A mixed artifact must be split by operative part, since representational form follows how each part is encoded and consumed. Skill routing metadata may be symbolic while its procedure remains natural-language. A hook is a scheduling attachment; its handler determines whether the response is interpreted or symbolic. A script supplies symbolic response semantics, but its caller determines activation.

Hardening can constrain either axis

Activation hardens when applicability moves from contextual recognition to explicit invocation, an event trigger, or a required gate. Response semantics harden when broad guidance becomes narrower natural-language criteria and, where a formal consumer assigns consequences, crosses into codification. The two movements often travel together, but neither entails the other. An always-running warning hook has stronger activation than a manually run validator and weaker response semantics.

This separation explains what the familiar maturation trajectory gets right. A practice can begin as interpreted guidance while its useful meaning is unsettled. Repeated failures to notice the rule create pressure to constrain activation. Stable, verifiable interpretations create warrant to constrain the response. When both conditions hold, a required symbolic check can constrain both parts. The trajectory is therefore one common path through the two-axis space, not a ranking built into the words instruction, skill, hook, and script.

Reliability increases only within the committed scope. A required validator guarantees that its encoded predicate runs at its boundary; it does not show that the predicate represents the real requirement. Codifying a proxy can enforce the wrong rule consistently. Judgment-heavy practices may therefore remain natural-language even when their activation is made reliable, because the boundary of automation is the boundary of verification.

Scope

  • The claim concerns activation and the immediate response to a requirement. Recovery after detection or rejection is a separate design dimension.
  • The table describes idealized configurations. A particular harness may combine routing, triggering, and response semantics differently.
  • Stronger enforcement is not automatically better. It trades interpretive latitude for a narrower commitment whose quality depends on its evidence and coverage.

Relevant Notes: