Research · Engine
RU Universality Certificate Engine
Project Scope
This project exists for one reason: to turn a strong claim into something you can rerun.
The flagship gap-free work says that when you impose real constraints on a positive growth process and then push growth to its minimum, the dynamics is forced into a small rigid core. That core is not guessed. It is returned by a finite certificate.
But a careful reader always asks the next question.
Is this a story you can actually use, or is it a story you can only admire?
The RU Engine is the answer.
It packages the flagship contract as a reproducible engine. You feed it finite input data in a fixed format: a constraint graph, nonnegative templates, and a cost model. The engine runs the same normalization steps the papers describe, then it produces one of two outcomes.
- If universality is forced, it outputs a robust certificate: a witnessed mixing word, a recurrence object, explicit contraction rates, and quantitative margins that yield a stability radius \(\varepsilon^*\). That radius tells you how far you can perturb the input without losing the guarantee.
- If universality is not forced, it does not hide. It outputs a finite obstruction witness (OG1–OG4) that explains what structural mechanism blocks the conclusion.
That is why this engine belongs in the library.
It is the bridge from theory to reuse. It makes it possible to speak in a different register:
- not only “a theorem holds,”
- but “here is the audited certificate object,”
- or “here is the audited obstruction object.”
If you want to see what changed as this engine became a real audited packet, use the updates page.
This page is the “runnable companion” to the flagship gap-free universality work.
The flagship submission proves a contract: from finite input data, you either obtain a quantitative universality certificate (explicit rates and robustness) or you obtain a finite obstruction witness (OG1–OG4) explaining why universality is not forced.
The RU Engine takes that contract seriously as engineering. It ships a reproducible packet that:
- accepts host instances in a schema-validated format
- executes the normalization and certificate/obstruction pipeline
- emits auditable JSON artifacts (certificates, obstruction witnesses, and region reports)
- includes a self-check so you can verify that the shipped artifacts match the claimed outcomes
What this engine is for
| You want | This engine gives you |
|---|---|
| A concrete way to rerun the story | Tools that regenerate the example artifacts and validate them against schemas |
| A stable “language” for results | Robust certificate objects with margins, rate packs, and a computed stability radius \(\varepsilon^*\) |
| Honest failure reporting | Finite obstruction witnesses that localize the mechanism (OG1–OG4) |
| Region-level output | A chamberwise report builder that aggregates certificates across a one-parameter family |
How it connects to the rest of the library
| Library layer | What it does | How the engine complements it |
|---|---|---|
| Gap-Free Global Universality (Submission v19) | The theorem-level contract and the region-level “cover-or-atlas” viewpoint | The engine makes the contract operational: the same objects appear as schema-validated artifacts |
| Verification Toolkit | Verification philosophy and tooling guidance | The engine provides a concrete audited suite to validate and extend |
| String Theory Bridge | Applied examples on physics-adjacent constrained families | The engine is the general-purpose runner that turns those examples into reproducible certificates |
What is inside the source packet
The source packet contains:
- a README and a reading order
- a self-check script that validates that artifacts match schemas
- schemas for host instances, robust certificates, obstruction witnesses, and region reports
- curated worked examples (including success and failure outcomes)
- reproducibility tooling for regenerating the audited suite
How to use it
| If you want | Do this |
|---|---|
| A fast overview | Read the engine overview inside the sources packet, then return here |
| To verify the shipped claims | Run the self-check script (listed in the packet README) |
| To adapt the machinery to a new host | Use the host instance schema, then validate the emitted certificate objects |
