DEV Community: Ayub

SET-12 Sealed: 149 Tests, 0.54s, MPFR Oracle in Rust

Ayub — Mon, 22 Jun 2026 12:45:36 +0000

Harmonis Prime SET-12 is sealed.

What that means:

149 reproducible tests, 0.54s, zero failures

400‑bit MPFR ζ(½+it) oracle with honest f64 fallback

Kahan‑Neumaier compensation: exact recovery of 2.0 from catastrophic cancellation

Backlund‑type truncation bound with monotonicity verification

Every limitation documented inline — no aspirational drift

What we did NOT do:

Claim "first‑of‑its‑kind" — no literature survey

Claim "aerospace‑grade" — no DO‑178C cert

Claim hardware acceleration — software‑only until Phase 3

Hide behind marketing — all claims verifiable via cargo test

The README is now live at v3.2 — research‑grade, with Mermaid architecture diagram, Phase 2 roadmap, and community engagement prompts.

One command to verify everything:

bash
git clone https://github.com/Ayub19123/Harmonis-Prime
cd Harmonis-Prime
cargo test --lib -- --nocapture
Permanent artifacts:

Whitepaper: https://doi.org/10.5281/zenodo.20777632

HF Space: https://huggingface.co/spaces/ayub227/harmonis-prime-set1

GitHub: https://github.com/Ayub19123/Harmonis-Prime

Every claim has a failing test first. The precision is eternal.

"How We Built a System That Refuses to Drift – Harmonis Prime Phase‑1 Complete"

Ayub — Sun, 21 Jun 2026 15:14:45 +0000

135 tests. 0.38 seconds. Zero warnings. One honest ignore.

🧱 1. The Problem – Why This System Exists
Modern computing is fragmented.
Distributed systems, kernel enforcement, identity, network calculus, energy telemetry, PIM, and analytic number theory all live in isolated silos. Each domain has its own languages, tools, and assumptions. Crossing boundaries is painful. Reproducibility is rare. Drift is everywhere.

Harmonis Prime asks a single question:

Can these domains be unified under one deterministic, test‑driven framework with zero diagnostic drift?

We set out to build a system where:

Every architectural claim is backed by an executable test.

Every limitation is documented inline.

Every commit is sealed with zero warnings, zero drift.

This is not a research demo. It is a production‑grade engineering discipline applied to HPC and analytic number theory.

🏛️ 2. Architecture Overview – The Flight Stack Analogy
Harmonis Prime is built like an aircraft flight stack:

Layer Analogy Purpose
Identity Transponder Unique, unforgeable node identity (PUF + NIST)
Kernel Enforcement Firewall Blocks all unauthorised egress (eBPF + netfilter)
Network Calculus Air Traffic Control Bounded delays, deterministic latency (min‑plus)
Energy Telemetry Fuel Instrumentation Real‑time, precise, drift ≤ 1% (PMU + EMA)
PIM Solver Onboard Compute Parallel 3‑SAT evaluation (O(1) model)
Analytic Number Theory Navigation Mathematical grounding (θ(t), Dirichlet, MPFR)
Each layer is:

Test‑verified – every invariant has a failing test first.

Deterministic – same input → same output, every run.

Sealed – zero warnings, zero drift, 0.38s full suite.

✅ 3. Phase‑1 Sealed – 135 Tests, 0.38s, Zero Drift
We shipped SET‑11, the final brick of Phase‑1:

Milestone Deliverable Status
M1.2 MPFR θ(t) oracle (Neumaier‑compensated, ε ≤ 1e‑14) ✅ Sealed
M1.3 Odlyzko zeros parser + SHA‑256 placeholder ✅ Sealed
M1.4b Backlund‑type truncation bound ✅ Sealed
M1.4 Criterion 30‑run benchmark baseline ✅ Sealed
Full suite:

bash
cargo test --lib -- --nocapture
Output:

text
test result: ok. 135 passed; 0 failed; 1 ignored; 0 warnings; 0.38s
The system is self‑auditing. Every claim can be verified by anyone, anywhere, with one command.

🔍 4. Honest Limitations – What We Did and Didn't Build
We document everything – including what we have not yet achieved.

What we built What we did NOT build (honest limitations)
✅ Neumaier‑compensated θ(t) oracle ❌ True MPFR ζ(½+it) – f64 fallback only
✅ Odlyzko zeros parser ❌ Odlyzko dataset validation – manual download pending
✅ Backlund‑type truncation bound ❌ FPGA acceleration – software simulation only
✅ Criterion benchmark baseline ❌ AVX‑512 kernel – experimental, may not compile
✅ Software PIM 3‑SAT solver ❌ Hardware PIM implementation
No hype. No overclaim. Just honest engineering.

🚀 5. Phase‑2 Preview – What Comes Next
Phase‑2 begins now. It is the hardware mapping phase:

Milestone Deliverable Target
M2.1 Full MPFR Z(t) oracle (ζ(½+it) at 400‑bit) RQ‑002
M2.2 Odlyzko/LMFDB dataset auto‑fetch + SHA‑256 verification RQ‑050–054
M2.3 AVX‑512 SIMD kernel (8× FP64 lanes) Throughput ≥ 10⁷/s
M2.4 NUMA affinity + 20‑run determinism suite RQ‑010–013
M2.5 RAPL energy instrumentation (Linux) RQ‑020A/B
M2.6 FPGA precision certification (simulated) RQ‑043
M2.7 FMEA CRITICAL closure (FM‑005, FM‑012) Phase‑3 entry gate
We are building this brick by brick, with the same discipline: invariants first, code second, zero drift.

💻 6. How to Run It – One Command, Reproducible Proof
The entire system is open source. You can verify every claim in under a second:

bash
git clone https://github.com/Ayub19123/Harmonis-Prime.git
cd Harmonis-Prime
cargo test --lib -- --nocapture
That's it. No installation, no configuration, no black boxes.

Also available:

Hugging Face Space: https://huggingface.co/spaces/ayub227/harmonis-prime-set1

Whitepaper (Zenodo): https://doi.org/10.5281/zenodo.20777632

Whitepaper (Figshare): https://doi.org/10.6084/m9.figshare.32732766

🧱 7. Join the Conversation
We are now in the evaluation phase – engineers are auditing, researchers are validating, endorsees are verifying.

We invite you to participate:

GitHub Discussions: "What should SET‑12 include?"

Help Wanted: AVX‑512, Odlyzko automation, RAPL porting

Architecture Feedback: "How to unify energy telemetry with analytic number theory?"

If you are an engineer who evaluates, not just clicks – this is your invitation.

Every claim has a failing test first. The precision is eternal. 🧱📡

"I Open-Sourced 135 Tests That Shouldn't Exist in the Same Repo"

Ayub — Sun, 21 Jun 2026 11:15:00 +0000

Most research code is abandoned after publication.

We built the opposite: a system where every architectural claim is backed by an executable test, every limitation is documented inline, and every commit is sealed with zero diagnostic noise.

HARMonis Prime SET-11 — Sealed.

What we built:
• 135/135 invariant tests passing
• Neumaier-compensated θ(t) oracle (ε ≤ 1e-14)
• Backlund-type truncation bound with monotonicity verification
• Criterion 30-run benchmark baseline
• SHA-256 integrity placeholder for Odlyzko dataset

What we did NOT build (honest limitations):
• True MPFR ζ(½+it) — f64 fallback only
• Odlyzko dataset validation — manual download pending
• FPGA acceleration — software simulation only
• AVX-512 kernel — experimental, may not compile

The proof is one command:
git clone https://github.com/Ayub19123/Harmonis-Prime.git
cd Harmonis-Prime
git checkout 476fd34
cargo test --lib -- --nocapture

Whitepaper (permanently archived):
Zenodo: doi.org/10.5281/zenodo.20777632
Figshare: doi.org/10.6084/m9.figshare.32732766

Phase 2 begins: MPFR Z(t) oracle, Odlyzko automation, AVX-512 kernel.

Every claim has a failing test first. The precision is eternal.

RustProgramming #DistributedSystems #AnalyticNumberTheory #RiemannZetaFunction #ZeroDriftValidation #DeterministicComputation #EnergyTelemetry #SoftwareAssurance #ExecutableInvariants #FormalVerification #HighPerformanceComputing #NumberTheoreticComputation #MPFR #CriterionBenchmarking #PIM #NetworkCalculus #EBPF #ChaosEngineering #BuildInPublic #OpenSource #ResearchSoftware

Harmonis Prime (Rust): Request for Execution Review Run it git clone https://github.com/Ayub19123/Harmonis-Prime.git cd Harmonis-Prime cargo test

Ayub — Tue, 09 Jun 2026 19:11:59 +0000

GitHub - Ayub19123/Harmonis-Prime: Harmonis Prime v7.1.0 — Distributed cognitive mesh with absolute zero · GitHub

Harmonis Prime v7.1.0 — Distributed cognitive mesh with absolute zero - Ayub19123/Harmonis-Prime

github.com

Harmonis Prime (Rust): Seeking Independent Testers, Reviewers & Architectural Feedback

Ayub — Tue, 09 Jun 2026 13:57:48 +0000

We recently published the first public specification and reference implementation of Harmonis Prime (HBS-1.0) — a distributed systems benchmark and research platform written in Rust.

Current status:

✅ 0 compilation errors
✅ Deterministic validation suite passing
✅ CI verified on Linux, Windows, and macOS
✅ Open specification and source code available

Specification:
https://zenodo.org/records/20541821

Repository:
[](url)

We are not looking for hype.

We are looking for honest technical evaluation from developers, engineers, researchers, and distributed-systems practitioners.

If you have time, we'd appreciate:

Cloning the repository
Running cargo test
Reviewing the architecture
Identifying weaknesses, flaws, edge cases, or risks
Sharing independent feedback, critiques, or validation results

Positive feedback is welcome, but critical feedback is even more valuable. If something can be improved, we'd rather know now than later.

Our goal is simple: build something useful, reproducible, and worthy of community trust.

Thank you to anyone willing to invest time in an independent review.

Example validation command:
https://github.com/Ayub19123/Harmonis-Prime

git clone https://github.com/Ayub19123/Harmonis-Prime.git
cd Harmonis-Prime

cargo test

We look forward to your findings and architectural critiques.