# `Decree.Decision.Rule.Result`
[🔗](https://github.com/sparkle-space/decree/blob/v0.1.0/lib/decree/decision/rule.ex#L280)

What a rule's reads answered, for one call of `execute/2`.

  - `events` - the data of the events the rule's own items matched, in position order.
  - `matched_keys` - parallel to `events`: for each, the keys of the rule's own items that
    matched it, each once, in item order. An unkeyed item adds none.

`Inspect` shows nothing of them, so it cannot reach a log by accident. `Jason` refuses to
encode it, which fences an event only while the serializer is JSON and the event's encoder
hands the result to `Jason` whole.

# `t`

```elixir
@type t() :: %Decree.Decision.Rule.Result{
  events: [struct()],
  matched_keys: [[term()]]
}
```

---

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