Identity & signing
A protected and traceable research record
Riemann Console is deliberately designed so that work released through this project does not become an anonymous collection of web pages.
Published material is tied to a controlled research and publication record using stable public identifiers, governed source records, publication decisions, exact content fingerprints, version history and correction history. For formal releases, that chain can additionally include cryptographic signatures made with the project’s OpenPGP signing identity and independent trusted timestamp evidence.
The signing identity published on this page is bound to Dom Boucher and to the programme’s public identity record. This makes it possible to establish, from independently checkable evidence, which exact material was released through Riemann Console, which project identity authorised the signed release, and whether the released bytes have subsequently changed.
This protection is about provenance, identity, integrity and chronology. It does not prevent material from being copied, nor does a cryptographic signature prove that a mathematical claim is correct. What it does mean is that copying the work does not erase the project’s documented publication trail: the originating public record can remain independently identifiable and verifiable.
Cryptographic status is reported honestly for each release. A signature or trusted timestamp is never implied where that evidence is still pending.
Riemann Console uses a dedicated OpenPGP signing identity to bind published release evidence to the research programme and to make exact released bytes independently verifiable.
Public identity
The research programme was initiated and is directed by Dom Boucher. His role includes question framing, curation, adversarial-testing oversight, systems architecture and publication/provenance stewardship. These roles are distinct from mathematical derivation or independent mathematical verification.
OpenPGP signing identity
Primary certification key Fingerprint: D7AF1093C786189118481BF552A7D2D1A5CD8238 Algorithm: Ed25519 Created: 4 September 2026 Expires: 3 September 2031 Capability: certification only
Signing subkey Fingerprint: 37D8C4E855C88B9A69B24B4E24C8B79030375C7D Algorithm: Ed25519 Created: 4 September 2026 Expires: 3 September 2028 Capability: signing
Verification status
The public-key export has been imported successfully into a fresh isolated keyring. The signing subkey has passed detached sign-and-verify testing using its full fingerprint, including testing in an isolated signing-subkey-only working environment.
Recovery and continuity
Two verified offline recovery copies of the signing identity exist on encrypted removable media, together with offline revocation material. The recovery copies have been checked against retained SHA-256 checksums. No secret-key material, passphrases, unreleased revocation material or recovery locations are published by Riemann Console.
What a signature establishes
A valid cryptographic signature can establish that particular bytes were signed using the project signing identity. Together with a deterministic release manifest, packet root and retained timestamp evidence, this supports later verification of exactly what was released and whether it has changed.
A cryptographic signature does not establish that a mathematical claim is true, novel or independently verified. Those are separate questions addressed by the research record, evidence and disclosure status associated with each release.
Public key
The ASCII-armoured public key associated with the fingerprint above is part of the project’s public verification evidence. Public-key file: DOM\_BOUCHER\_RH\_OPENPGP\_PUBLIC.asc. SHA-256: 577781ece1ce89e760a0053320268af621c323c1adef6eb37279cd2805e1ff2f. It is safe to distribute and is intended to be retained with public release evidence so historical signatures remain verifiable after future key rotation. \\\` \-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEapq3XhYJKwYBBAHaRw8BAQdAS4U4BKh4lX8UKR5/NuNMGGMLIma7wEdHM+qF pTs5pBS0Q0RvbSBCb3VjaGVyIChSaWVtYW5uIEh5cG90aGVzaXMgcmVzZWFyY2gp IDxyZXNlYXJjaEBkb21ib3VjaGVyLmNvbT6ItQQTFgoAXRYhBNevEJPHhhiRGEgb 9VKn0tGlzYI4BQJqmrdeGxSAAAAAAAQADm1hbnUyLDIuNSsxLjEyLDAsMwIbAQUJ CWYBgAULCQgHAgIiAgYVCgkICwIEFgIDAQIeBwIXgAAKCRBSp9LRpc2COO9+AP4t LjBkWtuFO50eQAOOYJQ95P6p3IcPYoCwzQrc+0NtBgEA1FMcyqreE9Ek0JFkKEzM d62l9jrA/OQIx6olBSR9pQ24MwRqmrrZFgkrBgEEAdpHDwEBB0DRtuvN21/oM3uB lK+ZYtYevKVt6TXIfxQ+KSm5IQMfKYkBEQQYFgoAQhYhBNevEJPHhhiRGEgb9VKn 0tGlzYI4BQJqmrrZGxSAAAAAAAQADm1hbnUyLDIuNSsxLjEyLDAsMwIbAgUJA8Jn AACBCRBSp9LRpc2COHYgBBkWCgAdFiEEN9jE6FXIi5ppsktOJMi3kDA3XH0FAmqa utkACgkQJMi3kDA3XH2XQQEApoXrWQUIT22Pds4usskKz3iJWQMHWz/T9zGxLJt6 RyUBALGP+Sw2rA7i2xZEQ4YsH0D4ICC+Hi/eNRlKAvat6NsKAggBAOx3A2EUbMcE jJ7LBsbUwdV5QOWYgjM5ag98zBbTV/lWAP9LDoPZGw4yCeSub8iwiLoKNbFmvtPW kScvad2+6005Dw== \=RUpn \-----END PGP PUBLIC KEY BLOCK----- \\\`
Identity binding
Dom Boucher’s ORCID iD is 0009-0008-5087-5987. Riemann Console has been added to that ORCID record as a web link, and this identity record links back to the same ORCID iD, establishing the intended reciprocal public identity binding.