Known limits
Alpha.25 is a functional physical preview. It is not stable and it is not production-ready. The missing validation work is listed here rather than hidden behind a broader claim.
Incomplete work
[ ] broad hardware compatibility matrix [ ] repeated power-cycle campaign [ ] network outage recovery campaign [ ] pool outage recovery campaign [ ] long unattended soak [ ] complete SBOM [ ] formal production support policy [ ] stable release guarantee
Claim matrix
| Claim | Status | Reason |
|---|---|---|
| A bootable experimental appliance exists | Supported | Physical Alpha.25 nodes reached ready state and mined. |
| The local-first contract exists in code and documentation | Supported | No billing, entitlement, activation, forced-pool or kill-switch runtime is part of the product contract. |
| All x86_64 hardware is supported | Unsupported | No broad compatibility matrix exists. |
| Outage recovery is production-safe | Unsupported | Network and pool outage campaigns remain incomplete. |
| Unattended long-term stability is proven | Unsupported | No long soak or repeated power-cycle campaign has closed the evidence gap. |
| Published hashrates predict other machines | Unsupported | Recorded figures are node samples, not benchmark guarantees. |
Why Alpha.25 is frozen
Alpha.25 is a coherent milestone. The product contract, boot paths, state authority, configuration revisions, firstboot, runtime rendering, huge-page preparation, systemd miner ownership, operator command and physical evidence exist together.
Freezing the milestone protects that record. Later development should move forward from a named and inspectable baseline rather than silently rewriting what Alpha.25 actually proved.
Explicit non-claims
- RIGOS does not claim superiority over other products without comparative physical evidence.
- Acceptance targets are not presented as universal benchmarks.
- GitHub source archives are not presented as bootable release images.
- Upstream XMRig donation behavior is not removed or hidden.
- A successful sample is not treated as proof of indefinite unattended safety.
Next validation gates
A future stable claim requires the incomplete campaigns above and published evidence that can be inspected independently.