Overview
What RHEA Kernel is.
RHEA Kernel is an experimental AI-efficiency project focused on reducing computational, token, latency and energy cost in LLM-based workloads while preserving output quality.
The project remains under active private development and experimental validation. The public website and repository document selected outcomes and project records rather than the mechanism used to produce them.
Documentation principle. Public RHEA Kernel material is designed to establish what was measured, under what stated scope, and which selected private artifacts have public integrity references — not to provide enough information to reconstruct the system.
Public scope
What is intentionally published.
The public record is deliberately narrow. It contains material that can be independently referenced while technical implementation and unpublished supporting material remain private.
01 · Purpose
High-level project scope
What RHEA Kernel is trying to improve and the dimensions on which the project is experimentally evaluated.
02 · Evidence
Selected validation outcomes
Benchmark-specific measurements, quality checks, replication records and dated validation statements approved for public release.
03 · Integrity
Cryptographic fingerprints
SHA-256 fingerprints of selected retained private artifacts, allowing later copies to be checked against a public record.
04 · Rights
Disclosure and rights notices
Clear boundaries around proprietary material, publication scope and the absence of an open-source grant.
Validation model
How to read the public evidence.
RHEA Kernel publishes benchmark-specific outcomes. A result should always be interpreted together with its model, workload, validation size, quality conditions and measurement method.
- Controlled baseline. Reported reductions are expressed relative to the comparison baseline used in the stated experiment.
- Quality preservation. Public records report coverage, accuracy or output parity where those checks were part of the validation.
- Cross-model replication. Repeating a validation pattern on additional model families supports reproducibility within those tested cases; it does not prove universal behavior.
- Paired energy validation. Published paired measurements represent separate controlled workload conditions rather than one universal percentage.
- Functional validation. A later frozen private runtime has published correctness and recorded-behavior evidence. Those functional results do not transfer an energy claim.
No universal savings claim. Published percentages are specific to their stated experiments and must not be treated as guaranteed savings for every model, workload, company, dataset or hardware platform.
Terminology
Public validation glossary.
- Baseline
- The comparison condition used in a controlled experiment. Public reductions are reported relative to that stated baseline.
- Coverage
- Whether the benchmark's required cases were successfully handled under the recorded validation criteria.
- Accuracy
- Whether outputs met the benchmark's correctness requirement under the recorded validation procedure.
- Output parity
- A recorded check that the compared outputs satisfy the parity requirement defined for that validation campaign.
- Wall time
- End-to-end elapsed workload time measured for the stated benchmark run.
- System-wide energy estimate
- An energy estimate derived from sampled macOS system-wide telemetry in the published experiments. It is not a calibrated external power-meter measurement and is not process-exclusive.
- Functional Freeze
- A formal recorded decision that a frozen private runtime met the stated functional-validation gate. It does not establish an energy claim.
- Frozen artifact
- A retained private package whose exact contents are fixed and can later be checked against its recorded cryptographic fingerprint.
- SHA-256 fingerprint
- A cryptographic digest used as an integrity reference. Publishing a hash does not disclose the underlying private artifact.
Public evidence map
Evidence currently represented in the public record.
This is an evidence map, not a development-version map or download list. Current internal revision mapping and private development state are intentionally outside the public scope.
| Public record | Recorded scope | What is publicly established |
| Controlled multi-round benchmark | Llama 3.2 3B · 6 × 600 queries | Published reductions in complete LLM calls, tokens, wall time and measured system-wide energy, with 100% coverage and accuracy in the recorded benchmark. |
| Independent cross-model replication | Qwen3 4B and Gemma3 4B | The overall measured benchmark effect was reproduced on additional tested model families with 100% recorded quality/output parity. |
| Preregistered paired energy validation | 3 controlled conditions · 24 valid pairs | Condition-specific paired energy reductions of 5.1526% to 40.2103%, with 100% quality/output parity and positive statistical evidence in every reported condition. |
| Later functional validation | Frozen private runtime · 25 Aug 2026 | 171/171 hosted tests, 2/2 cross-model cases, 9/9 endurance cases and 5,220/5,220 recorded raw events validated. These are functional results, not energy claims. |
Current internal version identifiers, validation-workflow mapping, experiment progress and development sequence are intentionally not represented here.
Artifact integrity
Why fingerprints are published.
Selected private RHEA Kernel artifacts are retained outside the public repository. Their SHA-256 fingerprints can be published without exposing those artifacts.
SHA-256Cryptographic fingerprint format used in the public integrity records.
PrivateThe underlying retained private artifacts are not published by those fingerprint records.
VerifiableA retained copy can later be hashed and compared with the public fingerprint to check exact identity.
Important limitation. A published artifact fingerprint is an integrity record only. The public repository explicitly states that it is not, by itself, a patent filing, statutory copyright registration, qualified electronic timestamp or legal opinion regarding priority or ownership.
Latest dated integrity note. The 7 September 2026 public record reports a retained private verification result of 44 checks: 40 PASS, 0 FAIL, 4 SKIP for selected retained private material. It does not establish a new performance, energy, quality or commercial claim.
Commercial measurement
Benchmark evidence and customer savings are different measurement layers.
Public benchmark results describe completed historical experiments under their stated conditions. Commercial Verified Net Savings for a future customer would instead be calculated from that customer's own agreed equivalent workload and quality gate.
Baseline
Baseline Equivalent Cost
The agreed equivalent baseline cost for the measured customer workload.
Quality
Quality gate
The agreed minimum output-quality requirement that must be preserved for a cost reduction to qualify as commercial savings.
Savings
Verified Net Savings
Baseline Equivalent Cost minus RHEA-enabled workload cost and agreed incremental costs attributable to operating RHEA.
Commercial fee
Performance fee
The applicable contractual percentage of positive Verified Net Savings. If Verified Net Savings are zero or negative, the performance fee is €0.
Quality-preserving requirement. A lower cost does not qualify as Verified Net Savings if the agreed quality gate is not maintained.
Disclosure boundary. These commercial measurement definitions explain how economic outcomes are evaluated. They do not disclose the proprietary mechanism used internally by RHEA Kernel.
Disclosure boundary
What this documentation does not disclose.
RHEA Kernel is proprietary. Technical implementation and unpublished supporting material remain private, and publication of the public repository does not grant a license to unpublished RHEA Kernel materials.
- No source release. RHEA Kernel is not released as open-source software.
- No reconstruction guide. Public documentation is not intended to provide information sufficient to reconstruct the system.
- No current private-state mapping. Current internal version identifiers, validation-workflow mapping, experiment progress and development sequence are intentionally outside the public scope.
- No universal performance guarantee. Experimental figures remain tied to the stated validation context.
- No implied license. Publication of selected records does not grant rights to unpublished proprietary material.
Official sources
Public records.
The website summarizes approved public material. The repository remains the underlying public record for dated documents, selected results, artifact fingerprints and rights notices.
Project
README
High-level purpose, public scope, disclosure boundary and current public status.
Open README ↗
Results
Selected experimental results
Historical public benchmark measurements and interpretation limits.
Open results ↗
Validation
Dated validation record
Public validation evidence dated 29 August 2026, including functional and integrity references.
Open validation record ↗
Integrity
Artifact fingerprints
SHA-256 fingerprints of selected retained private artifacts using intentionally generic public labels.
Open fingerprints ↗
Latest record
Selected integrity record
Dated public integrity reference from 7 September 2026, without internal revision, workflow or current-progress mapping.
Open integrity record ↗
Rights
Rights & disclosure
Proprietary status, disclosure limits and rights notice.
Open rights notice ↗
Website
Measured results
Readable presentation of selected approved public validation outcomes.
Open Results →