# `Monty.Frameworks.Models.MotorPolicies.MotorPolicyResult`
[🔗](https://github.com/d-led/ex.tbp.monty/blob/v0.1.0/packages/ex_tbp_monty_core/lib/monty/frameworks/models/motor_policies/motor_policy_result.ex#L1)

What one call to a motor policy decided: the actions, and how finished it is.

Mirrors `tbp/monty/frameworks/models/motor_policies.py::MotorPolicyResult`.
`motor_only_step` says the learning modules should be skipped this step — a
policy that is only turning or moving has nothing for them to match — and is
how a policy affects the run without reaching into it. `telemetry` is the
surface policy's own record of why it chose what it chose, kept because there
is nowhere else for it to go yet, as Monty says of its own.

Monty lets a policy set `motor_only_step` on the motor system itself through a
`fixme_provide_motor_system` handout; here the policy says it in the result it
returns (`docs/monty-differences.md` §2.2).

# `action`

```elixir
@type action() :: term()
```

# `t`

```elixir
@type t() :: %Monty.Frameworks.Models.MotorPolicies.MotorPolicyResult{
  actions: [action()],
  motor_only_step: boolean(),
  status: Monty.Frameworks.Models.MotorPolicies.PolicyStatus.t(),
  telemetry: term()
}
```

# `new`

```elixir
@spec new() :: t()
```

A result with nothing decided: no actions, and the policy ready for more.

Monty's conservative defaults, so a policy only has to say what it did.

---

*Consult [api-reference.md](api-reference.md) for complete listing*