Wards are the policy that bounds your loop. The runtime resolves them here: numeric and boolean wards compose by tightening, while passthrough ward data remains explicit policy for the gate or medium that enforces it.
Pure ward resolution and inspection.
Wards are policy data. This module is the Elixir-native home for resolving
and querying those policies, leaving Cantrip.Circle as circle
configuration data.
Summary
Functions
@spec code_eval_timeout_ms([map()]) :: pos_integer()
@spec max_batch_size([map()]) :: pos_integer()
@spec max_children_total([map()]) :: non_neg_integer() | nil
@spec max_concurrent_children([map()]) :: pos_integer()
@spec max_depth([map()]) :: non_neg_integer() | nil
@spec max_turns([map()]) :: pos_integer() | nil
@spec validate_child_spawn([map()], Cantrip.Circle.t() | map()) :: :ok | {:error, String.t()}