# RH-W-18: Unified Certificate Backend and Single Verification Entry Point

**Node**: `RH-W-18-CERTIFICATE-BACKEND-CONSOLIDATION`  
**Date**: 2026-07-24  
**Positioning**: Certificate engineering consolidation for Batch 01; not a proof or disproof of the Riemann Hypothesis.

## Abstract

RH-W-05 through RH-W-17 have gradually formed various certificates: finite-dimensional Weil matrices, prime-power chambers, generalized spectral lower bounds, fixed witness upper bounds, mixed regularity dictionaries, parameter tubes, 3D boxes, and event surface segmentations. Their mathematical content is compatible, but the schemas, dependencies, output formats, and completeness of the historical packages are inconsistent.

This round establishes a common backend:

```bash
python rhcert.py list
python rhcert.py verify
python rhcert.py verify --record RH-W-17
python redteam_backend.py
```

The backend first checks the SHA-256 hashes, then executes each historical verifier in a temporary copy to prevent the output files generated by the verifier from modifying the original certificates. Each successful result must also simultaneously contain the expected status string and `RH_CLAIM=False`.

## Five Certificate Categories

1. `NUMERICAL_MATRIX`: Finite-dimensional interval matrices and exact rational LDL certificates.
2. `PARAMETER_REGION`: Continuous parameter boxes, corner convex hulls, and Taylor remainders.
3. `CHAMBER_COVER`: Event surface segmentations, closed interval covers, and chamber adjacencies.
4. `STRUCTURAL_IDENTITY`: Activation orders, regularity, and kernel convolution identities.
5. `PROTOCOL_ONLY`: Defines how to accept a negative witness, but does not claim a witness has been found.

## Status is Not Binary Pass/Fail

- `VERIFIED`: The specified verifier can be completely replayed within the package.
- `VERIFIED_WITH_LIMITATION`: The verifiable part holds, but is insufficient to reconstruct all historical inputs.
- `PROTOCOL_ONLY`: The verification protocol passes self-testing, with no target mathematical witness.
- `SUPERSEDED_RECERTIFIED`: The old derivation is superseded, and the conclusion is reproven by subsequent rounds.
- `LEGACY_INCOMPLETE`: Missing necessary historical inputs; not allowed to be displayed in green.

This status lattice is more important than "all rounds succeeded" because it separates the research content from the package quality.

## Claim Firewall

The unified manifest is fixed as:

```json
{"RH_CLAIM": false, "allowed_global_conclusion": "FINITE_CERTIFICATE_BACKEND_ONLY"}
```

A single finite-dimensional positivity, finite parameter tube, or event surface cover cannot be elevated to an RH conclusion by the backend. If the manifest is changed to `RH_CLAIM=true`, the manifest verification will still reject it even if the file hashes are recomputed.

## The Most Important Engineering Result of This Round

W-18 does not force different mathematical certificates into the same matrix format, but rather unifies their high-level semantics:

$$
\text{Artifact Identity}
\to
\text{Native Verification}
\to
\text{Normalized Claim Record}
\to
\text{Dependency Graph}
\to
\text{Claim Firewall}.
$$

Therefore, when adding new certificate types in the future, the native verifiers can be preserved; one only needs to add an adapter and a manifest record, without having to rewrite all historical certificates.

## External Research Context

Related work in 2026 also emphasizes the distinction between finite Galerkin Weil matrices, strict Archimedean tail bounds, and replayable computational artifacts; other work studies their structure from the connection between screw functions and Weil quadratic forms. These contexts support the importance of rigorous certificate engineering, but the results and responsibility boundaries of this engineering package are entirely determined by its own artifacts and verifiers.