# `Insider.Sentinel.Regression`
[🔗](https://github.com/hiivemarkets/insider/blob/v0.1.0/tools/insider_lab/lib/insider/sentinel/regression.ex#L1)

A bounded, canonical recipe for proving a confirmed incident still fails.

A regression embeds the exact source confirmation and scenario as data. Its
SHA-256 identity detects accidental or malicious rewriting when the expected
digest is trusted separately; it is not authenticity or proof of failure.
`classify/2` requires two distinct fresh confirmation records and deliberately
cannot make a passing-after claim.

# `t`

```elixir
@type t() :: %Insider.Sentinel.Regression{
  confirmed_record: term(),
  execution_policy: term(),
  expectation: term(),
  id: term(),
  integrity: term(),
  scenario: term(),
  schema: term()
}
```

# `canonical_binary`

```elixir
@spec canonical_binary(term()) ::
  {:ok, binary()} | {:error, Insider.Protocol.Error.t()}
```

# `classify`

```elixir
@spec classify(term(), term()) :: {:ok, map()} | {:error, Insider.Protocol.Error.t()}
```

Classifies exactly two fresh confirmation records against a regression.

The stable result is data, not a new evidence artifact. A `failed` result
means both fresh runs reproduced the bound failure. Every other valid run
combination is `inconclusive`; positive repair proof belongs to verification.

# `decode`

```elixir
@spec decode(binary()) :: {:ok, t()} | {:error, Insider.Protocol.Error.t()}
```

# `decode_map`

```elixir
@spec decode_map(term()) :: {:ok, t()} | {:error, Insider.Protocol.Error.t()}
```

# `materialize`

```elixir
@spec materialize(Insider.Sentinel.Confirmation.Record.t(), Insider.Scenario.t()) ::
  {:ok, t()} | {:error, Insider.Protocol.Error.t()}
```

# `to_wire_map`

```elixir
@spec to_wire_map(t()) :: map()
```

# `validate`

```elixir
@spec validate(term()) :: {:ok, t()} | {:error, Insider.Protocol.Error.t()}
```

---

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