# Steering: reproducibility as trust

In Solnix, a binary is trusted because it can be **independently reproduced**,
not because of who built it.

- A build is submitted unsigned. The site classifies and signs it (Option A).
- Trust accrues when **independent builders produce the same output hash** for
  the same input — a **reproducibility quorum**.
- Each package carries a trust tier, visible at
  `GET /api/v1/packages/:attr/attestations`:
  - `verified` — a quorum of independent, identical hashes.
  - `reproduced` — reproduced by at least one other party.
  - `single` — only the original builder so far.
  - `disputed` — independent builders disagree on the hash. Investigate before
    trusting.
- This is one of two minimal, non-merging trust roots: **math governs
  binaries** (N identical hashes → the signer); **the maintainer governs source**
  (email → git). Keep them separate.

Practical consequence for agents and contributors: prefer `verified`/`reproduced`
packages; treat `disputed` as a red flag; a reproduction you perform and report
is a real contribution (see the `reproduce-and-vote` workflow).