13.1 Params, and anchoring a rule

A rule set may declare params in the same vocabulary as view params (type / default / description), referenced as $name in any body:

params:
  minStake: { type: int, default: 50, description: "Aggregate percentage at which status propagates" }

A query that merely MATCHes the derived label evaluates the rules implicitly, on defaults — so a rule set meant for implicit evaluation should default every param. Anchoring a rule set to one entity is nothing special: declare the key as a param ({officerId: $officer}). Param names may not shadow the engine’s reserved names or the scope pair (userId, worldId).