---
name: SOLNIX-MAINTAINER
description: Review patches, version bumps, and governance decisions for Solnix. Use when acting as a maintainer or owner — voting on a patch, approving a version, deciding blast radius, or handling the OWNERS/CVE process.
---

# Maintaining Solnix

Solnix governs changes by an **email-patch model** (not forge pull requests) plus
**reproducibility-as-trust**. See
[email-patch-governance](community/steering/email-patch-governance.md) and
[reproducibility-as-trust](community/steering/reproducibility-as-trust.md).

## Two lists, two roots of trust

- `hackers@solnix.io` — patches and discussion (public).
- `security@solnix.io` — embargoed CVE work (private).

Two minimal trust roots that never merge:
1. **The maintainer governs source** (email → git.solnix.io).
2. **Math governs binaries** (N independent identical hashes → the signer).

## Reviewing a patch

- Read it on `hackers@`. Reply with `+1` / `0` / `-1`. An **owner `-1` hard-blocks**;
  silence past the timer can be a pocket-veto if a quorum path is available.
- A patch needs a **reproducibility quorum** (independent builders reaching the
  same output hash) AND a **distinct post-quorum owner approval** — the two are
  separate gates, not one.
- High-blast-radius changes (toolchain, stdenv, seeds) need an **owner quorum**.

## OWNERS + timers

`OWNERS` files declare who governs each area; the **core team governs OWNERS**.
Transition timers default to 3 business days; `adjust-timeout:` / `adjust-quorum:`
email commands tune a specific thread.

## Editions

You cut editions (`26.11`, `unstable`). See
[edition-policy](community/steering/edition-policy.md). The default branch is the
latest supported edition.

## Honesty

Never approve a claim the status page can't back. See
[honesty-over-hype](community/steering/honesty-over-hype.md).