Pipeline Substrate Library → Proving Grounds → Oracle Validation → Hypothesis Generation → Parametric Search → Evolutionary Discovery

Glossary

The formal vocabulary of Substrate Geometry. Eight definitions that constitute the intellectual foundation of the research program — every term precise enough to be used unambiguously in code, papers, and conversation.

What This Is

Engineering systems fail because of their geometry — not their material. Substrate Geometry is a research program that identifies geometric shapes whose mathematical properties eliminate failure modes at source, rather than delaying them with better materials.

The Synthesis Engine scores geometric primitives across five independent physics domains — contact, stress, thermal, fatigue, and wear — to determine what a shape guarantees under sustained physical operation. Each shape receives an invariant vector: a set of numbers that define its engineering identity.

The Problem

Changing the material delays the failure. Changing the geometry eliminates it.

The Method

Seven computational oracles scoring each shape across contact, stress, thermal, fatigue, and wear physics.

The Result

The oloid scores 58–68× better than a cylinder on every metric. Five physics measurements confirming one geometric invariant.

Formal Definitions

The intellectual vocabulary of the Substrate Geometry Research Program. Every term carries a precise definition, an illustrative example, and a note on its significance to the pipeline.

Substrate Geometry
The study of geometric forms as engineering substrates, classified by their operational invariants rather than their symmetry groups. Where conventional geometry asks "what shape is this?", substrate geometry asks "what does this shape guarantee under physical operation?"
Example: The oloid guarantees uniform contact distribution; this property, not its topology, is its classification.
Significance: Reframes the entire discipline of geometric engineering around computable guarantees rather than descriptive taxonomy.
Invariant Primitive
A geometric body whose engineering utility derives from a formally stated mathematical invariant that holds under physical operation (rolling, flow, stress, or field exposure). Distinguished from "shapes" or "solids" by the requirement that the invariant be expressible as a computable predicate.
Example: The oloid is an invariant primitive; a cube is not. The oloid's contact distribution invariant is testable by the oracle; a cube has no operational invariant.
Significance: Establishes the boundary between conventional geometric engineering and substrate geometry.
Geometric Failure Mode
A class of engineering failure whose root cause is the geometry of the component rather than the material or power source. Thermal hotspot concentration, Hertz contact fatigue localization, Hartmann boundary-layer loss, and mixing dead zones are all geometric failure modes.
The defining characteristic: changing the material delays the failure; changing the geometry eliminates it.
Significance: Identifies the exact problem class that invariant primitives are designed to solve.
Contact Distribution Score (CDS)
A scalar measure of how uniformly a convex body distributes contact time across its surface during rolling. Computed as the area-weighted variance of the contact distribution: CDS → 0 means perfectly uniform (invariant satisfied); CDS > 0 means localized contact (conventional failure mode).
The oloid scores 1.15 × 10⁻⁶; a cylinder scores 3.21 × 10⁻⁵ — 28× worse.
Significance: The quantitative metric that makes the contact distribution invariant computable and comparable across geometries.
Pass-Gate Validation
The four-criterion framework every invariant primitive must satisfy to enter the Substrate Library: (1) Formal invariant statement as a computable predicate, (2) Physics simulation or measurement confirming the invariant predicts the efficiency outcome, (3) Baseline comparison with geometry as the isolated variable, (4) Cross-domain transfer argument showing the invariant applies in at least one other physics regime.
Example: The oloid has passed all four criteria. A novel candidate enters the Proving Grounds and must satisfy each gate before promotion.
Significance: Prevents false positives from entering the substrate library. Every criterion closes a specific escape hatch.
Substrate Library
The curated catalog of validated invariant primitives. Each entry carries a formal invariant, parameter vector, physics regime validation status, and cross-domain transfer evidence. Currently contains 10 entries across three layers (Surface, Flow, Mechanism).
Example: The gyroid entry carries H = 0 as its invariant, validated in thermal and electromagnetic regimes, with an MHD hypothesis under investigation.
Significance: The data substrate that the synthesis engine, parametric search, and evolutionary discovery layers read from.
Proving Grounds
The validation arena where candidate primitives are tested against the pass-gate criteria with numerical evidence. A primitive enters as a hypothesis and exits as either a validated substrate library entry or a rejected candidate.
Example: The oloid case study is the first completed Proving Grounds validation, establishing the evidentiary standard for all subsequent entries.
Significance: The quality gate that maintains the integrity of the substrate library and the credibility of the research program.
Search Family
The invariant-preserving parameterization space surrounding a known primitive. Defined by the set of continuous deformations that maintain a target invariant below a specified threshold. A search family is the mechanism by which Substrate Geometry discovers novel primitives rather than cataloging known ones.
Example: The oloid is a fixed point in the developable roller family. Perturbations of its generating-circle angle (90°), offset (r), and radii ratio (1:1) define the search territory. The parametric search engine explores this space; the oracle scores each point; evolutionary algorithms optimize the traversal.
Significance: The connective tissue between known primitives and undiscovered ones. Search families that span physics regimes are cross-domain objects that no single engineering discipline owns — they are the orthogonal bridge between substrate library entries and the compositional layer beyond them.

Substrate Library

The curated catalog of geometric primitives with formally stated invariants. Each entry carries a computable predicate, parameter vector, physics regime validation status, and cross-domain transfer evidence. 10 entries across three layers — 1 fully validated.

Proving Grounds

The validation arena. A primitive enters as a hypothesis and exits as either a validated library entry or a rejected candidate. The four-criterion pass gate maintains the scientific standard — no primitive enters the library without earning it.

Case Study I · Mechanism Layer · Validated

The Oloid — geometry as engineering function

The anchor primitive. The first fully validated substrate entry. Every novel candidate that passes the four-criterion pass gate earns the same standing. The oloid sets the evidentiary standard the entire program is measured against.

All 4 validation criteria passed

Mechanics Visualization

The oloid's surface is fully developable (K = 0 everywhere). It has no rotational symmetry axis, yet rolls on a flat surface in a path that eventually covers the entire plane. Surface area: 4πr². Contact: full line-contact at every instant.

Live mechanics visualization
Contact line
Swept path
Generating circles

The Problem Space

Three failure modes geometry can solve

01
Thermal Concentration
When geometry creates persistent hotspots, it establishes failure nucleation sites. No alloy specification eliminates this — the heat finds the geometry before the material gives.
MHD drives · Rocket nozzles · High-cycle turbine blades
02
Contact Localization
Standard rolling elements trace the same contact path on every cycle. The Hertz pressure integral concentrates fatigue at a fixed locus. This is a geometric inevitability for those shapes.
Bearings · Seals · Couplings · Valve seats
03
Mixing Dead Zones
Conventional impeller designs create rotational symmetry that generates stagnation regions — volumes of fluid that never fully exchange with the bulk.
Wastewater aeration · Industrial bioreactors · Liquid-liquid extraction
Criterion 01
Formal Invariant Statement
The invariant must be expressed as a computable mathematical predicate — not prose. Must specify what is guaranteed, under what conditions, with convergence bounds.
Contact distribution convergence theorem
Criterion 02
Physics Simulation or Measurement
At least one simulation or documented physical measurement demonstrating the invariant predicts the efficiency outcome. Theory alone does not pass.
Aeration efficiency +72% vs prior best
Criterion 03
Conventional Baseline Comparison
Benchmarked against the best conventional approach. Geometry must be the isolated variable — not motor power, not material grade.
vs. diffuser bubble systems (prior best-in-class)
Criterion 04
Cross-Domain Transfer Argument
The invariant must be argued to apply in at least one other physics regime. This separates a primitive from a domain-specific tool.
Contact mechanics + MHD electrode hypotheses active
Theorem 1Contact Distribution Invariant — Mechanism Layer

Let O be an oloid of radius r rolling without slipping on plane Π. Define contact locus C(t) as the set of surface points contacting Π at time t. The time-averaged contact measure converges to the uniform distribution over the surface:

\[ \lim_{T \to \infty} \frac{1}{T}\int_0^T \mathbf{1}_{[p \in C(t)]}\, dt \;=\; \frac{1}{|\partial O|} \qquad \forall\; p \in \partial O \]

The Hertz contact pressure integral distributes across the full surface area as motion accumulates:

\[ \oint_{\partial O} \sigma_H(p,t)\, dA \;\longrightarrow\; \text{uniform as } t \to \infty \]
Engineering implication: No surface point accumulates disproportionate contact fatigue. A cylinder bearing concentrates Hertz stress at a fixed locus on every rotation. The oloid's invariant eliminates this at the geometric level — not by reducing stress, but by distributing it across the full surface before any point reaches its endurance limit.
CorollaryFluid Traversal Completeness — Mixing & Aeration

For fluid volume Ω with an oloid agitator, the induced velocity field v(x,t) satisfies:

\[ \forall\; x \in \Omega,\quad \exists\; t_x \;:\; \|\mathbf{v}(x,\, t_x)\| \;>\; v_{\text{thresh}} \]
Engineering implication: Dead zones are topologically impossible. Conventional impeller rotation guarantees stagnation at the central axis — running it harder does not eliminate that zone. The oloid's traversal completeness is a topological property, not an intensity property.
Energy efficiency
Oxygen transfer per kWh
Surface aerator (conv.)1.2 kg O₂/kWh
Diffuser bubble (prior best)1.8 kg O₂/kWh
Oloid agitator system3.1 kg O₂/kWh
+72%
vs. prior best-in-class · geometry was the variable
Mixing uniformity
Dead zone elimination
Dead zone volume (conv.)18–24%
Dead zone volume (oloid)<2%
Full-volume traversal time−60%
Key distinction: dead zone elimination is not a power story. Running conventional impellers harder increases energy input to already-active regions. The invariant does the work — the motor does not.

Cross-domain transferability of the invariant

Confirmed
Fluid Mixing
Traversal completeness invariant applies directly. Dead zone elimination validated in lake aeration and industrial bioreactor applications.
Under Investigation
Bearing & Seal Systems
Hertz fatigue redistribution predicted by the contact distribution invariant. Requires contact mechanics simulation oracle.
Novel Hypothesis
MHD Electrode Surfaces
Lorentz stress and thermal concentration at MHD electrode surfaces may respond to oloid-derived surface topologies.
Pass Gate Status — Oloid / Case Study I
All criteria satisfied
This entry is now part of the substrate.
It feeds the synthesis engine as a base invariant.
CRITERION 01
Formal Invariant Statement
The invariant must be expressed as a computable mathematical predicate — not a prose description.
Contact distribution convergence theorem
CRITERION 02
Simulated or Measured Physics Result
At least one simulation or documented physical measurement must show the invariant predicts the efficiency outcome.
Aeration efficiency validated (72% gain)
CRITERION 03
Conventional Baseline Comparison
Efficiency gain must be benchmarked against the best conventional approach, isolating geometry as the variable.
vs. diffuser bubble systems (prior best-in-class)
CRITERION 04
Cross-Domain Transfer Argument
The invariant must apply in at least one other physics regime, separating a primitive from a domain-specific tool.
Contact mechanics + MHD hypotheses active

Research Lineage & Forward Path

1929
Schatz discovers
the oloid
∂O
Invariant
formalized
Proving grounds
validated
Synthesis engine
generates candidates
Novel primitives
enter substrate
→∞
Extended
vocabulary

Candidate Zone

Primitives proposed by the synthesis engine that haven’t yet passed the proving grounds. Each entry shows its readiness checklist — what work remains before validation. Candidates that pass all four criteria graduate to the substrate library.

Oracle Console

Seven oracle artifacts measuring geometric invariants across five independent physics domains: contact time, Hertz stress, frictional thermal, Basquin fatigue, and Archard wear. The computational engine that turns shapes into numbers.

Rigid-Body Oracle — Euler-equation dynamics, 3 runs, 600 samples

Rank Geometry CDS Score vs. Oloid Surface Area Contact CV Status
1 Oloid (Schatz 1929) 8.2e-7 1.00× 12.66 0.917 PASS
2 Candidate #2 (120°/1.30/0.80) 8.7e-7 1.06× 11.34 0.856 PASS
3 Candidate #3 (90°/0.70/0.80) 1.09e-6 1.33× 9.35 0.758 PASS
4 Candidate #1 (120°/0.70/0.80) 1.93e-6 2.35× 9.02 0.759 PASS
5 Cylinder (conventional) 4.75e-5 58× 18.83 1.610 FAIL

Approximate Oracle — Composed rotation, 600 steps (search layer)

Geometry CDS Score Steps Surface Area Contact CV Status
Oloid 1.15e-6 600 4πr² ~0.03 PASS
Sphere 1.12e-6 600 4πr² ~0.03 PASS
Cylinder 3.21e-5 600 2πr(r+h) ~0.18 FAIL
Reuleaux 3D 3.31e-3 600 varies ~0.58 FAIL

Oloid Invariant Vector — Complete

Five independent physical measurements confirming the oloid’s geometric invariant. Each oracle uses different physics (contact mechanics, elasticity, thermodynamics, fatigue, tribology) but scores the same underlying property: does this shape distribute uniformly?

Dimension Oracle Oloid Cylinder Ratio Tier
CDS Contact time 8.20 × 10−7 4.75 × 10−5 58× Tier 1
SDS Hertz stress 8.07 × 10−7 4.68 × 10−5 58× Tier 1
TDS Thermal (friction heat) 7.77 × 10−7 5.28 × 10−5 68× Tier 1
WDSvol Archard wear volume 7.77 × 10−7 5.28 × 10−5 68× Tier 1
WDSdepth Wear depth (area-normalized) 1.15 × 10−6 5.33 × 10−5 46× Tier 2
FDS Basquin fatigue damage 2.42 × 10−6 Tier 2

Tier 1 — Lossless Transfer

CDS, SDS, TDS, WDSvol all cluster at ~8 × 10−7. The contact time invariant propagates linearly through stress, thermal, and wear volume physics. Cylinder 58–68× worse on every metric.

SDS/CDS = 0.98 — TDS/CDS = 0.95 — WDS/CDS = 0.95

Tier 2 — Lossy Transfer

FDS and WDSdepth diverge due to nonlinear physics. Basquin’s S-N law exponentially amplifies small stress differences. Area normalization penalizes small mesh faces. Oloid still dominates all tested geometries.

FDS: oloid damage ratio 23× vs. 159× for nearest competitor

Key Findings

TDS is the lowest score in the vector (7.77 × 10−7). The oloid’s rolling kinematics produce an inverse correlation between contact frequency and sliding velocity — faces that contact most often slide slower, creating self-compensating thermal distribution.

Rolling dynamics, not static curvature, are the operative mechanism. The oloid has higher curvature variance (σH = 0.90) than the cylinder (0.28) yet distributes stress more uniformly. The geometry of motion dominates.

Cylinder FDS = ∞ — at 5,000 N bearing load, all cylinder contact stresses fall below the endurance limit because contact is so localized. The cylinder doesn’t fail by distributed fatigue — it fails by pitting and spalling at a single locus. A qualitatively different failure mode.

The RB Winner (120°/1.30/0.80) achieves a fatigue damage ratio of 14× vs. the oloid’s 23×, suggesting the CDS-optimal shape is not always the fatigue-optimal shape. The invariant vector captures tradeoffs invisible to any single metric.

Hertz Stress Oracle — SDS vs CDS, 3 runs, 600 samples

Rank Geometry CDS SDS SDS/CDS max (MPa) Stress CV
1 Oloid (90°, 1.0, 1.0) 8.20e-7 8.07e-7 0.98 68.3 0.085
2 RB Winner (120°, 1.30, 0.80) 8.70e-7 8.89e-7 1.02 68.3 0.084
3 Candidate (115°, 1.20, 0.65) 9.30e-7 9.80e-7 1.05 76.0 0.101
4 Candidate (115°, 1.30, 0.65) 8.60e-7 9.80e-7 1.14 76.6 0.110
5 Candidate (115°, 0.70, 0.65) 1.77e-6 1.79e-6 1.01 79.2 0.109
6 Cylinder (conventional) 4.75e-5 4.68e-5 0.99 49.7 0.045
Convergence analysis
CDS Score vs. Simulation Steps (log scale)
Oloid
Sphere
Cylinder
Reuleaux 3D
CDS comparison
Contact Distribution Score (log scale)

Pipeline Artifacts — 7 Oracles Complete

01 contact_oracle.py → CDS (contact time)
02 parametric_search.py → 1,430 genome search
03 rigidbody_oracle.py → Defensible CDS (Euler equations)
04 hertz_oracle.py → SDS (Hertz stress distribution)
05 fatigue_oracle.py → FDS (Basquin S-N fatigue damage)
06 thermal_oracle.py → TDS (friction thermal distribution)
07 wear_oracle.py → WDS (Archard wear distribution)

Source: github.com/gyapaganda-a11y/substrate-geometry

Framework

The architecture, design principles, and operating rules of the Substrate Geometry research program. This is the constitution — the vision, the invariant vector structure, the oracle runner spec, and the path from computation to real engineering application.

1 — The Thesis

“Changing the material delays the failure; changing the geometry eliminates it.”

“I dont want to replace one cylinder of an engine with a cool shape and just revolutionize the engine. What I want? To discover if its possible to build on the whole of Archimedean architecture, to have someone look at a traditional current working system of parts and then my version of it, an array of newly designed geometric primitives re-distributing the foundational logic of the methodology a design intention was employed in physical space at the granular level up to the interlocking macro systems involved.”

“Its not even that new primitives can be discovered and used. Its that mapping this field, populating it with real working applications and new geometry that works with engineering principles, will reveal a new layer later on which is: How do all of these new applications of substrate geometry interact with EACH OTHER to produce even more vastly efficient methods of engineering.”

2 — The Invariant Vector

Every validated primitive receives a complete invariant vector — independently measured scores across physics domains. This is the primitive’s engineering identity card.

DimensionPhysicsOloidCylinderRatioTier
CDSContact time (rolling dynamics)8.20e-74.75e-558×Tier 1
SDSHertz contact stress8.07e-74.68e-558×Tier 1
TDSFrictional thermal (p × v)7.77e-75.28e-568×Tier 1
WDSvolArchard wear volume7.77e-75.28e-568×Tier 1
WDSdepthArea-normalized wear depth1.15e-65.33e-546×Tier 2
FDSBasquin fatigue (S-N + Miner’s)2.42e-6Tier 2

Tier 1 — Lossless Transfer

CDS, SDS, TDS, WDSvol cluster at ~8×10-7. Four independent physics measurements within 5% of each other. The contact time invariant propagates losslessly through stress, thermal, and wear volume physics.

Tier 2 — Lossy Transfer

FDS and WDSdepth diverge. Basquin’s S-N law exponentially amplifies small stress differences. Area normalization penalizes small faces. Oloid still dominates — the transfer is lossy, not broken.

Every primitive gets the shared dimensions (CDS, SDS, TDS, FDS, WDS) for cross-primitive comparison, PLUS its own unique invariant-specific score — the measurement that captures what makes that primitive irreplaceable. The shared dimensions are the common language. The unique dimension is the identity.

3 — Oracle Runner Architecture

The oracle runner takes a shape and an engineering context and outputs a prediction an engineer can act on. Not “run mesh through 5 oracles” — a full operating-regime-aware scoring engine.

Required Inputs

Mesh — any watertight STL/OBJ

Invariant definition — formal computable predicate

Baseline geometry — “better than what?”

Operating Context

Constraint geometry — flat plane, plates, bore, field

Load envelope — sweep range, find crossovers

Material + environment — not hardcoded

Failure criterion — turns scores into service life

Target Output

“Gyroid electrode surface (H=0 invariant) under 50 kW/m² arc heat flux at 1200K predicts TDS = X vs flat plate TDS = Y, a Z% improvement in thermal uniformity. Predicted thermal cycling life: N cycles to first hotspot exceeding 1500K. Confidence: ±W% at current mesh resolution. Manufacturable via SLM additive. Recommended experimental validation: thermocouple array on 3D-printed specimen under controlled arc.”

Confidence Bounds

Not just “TDS = 7.77e-7” but “±0.3e-7 at this mesh resolution.” Error bars make predictions mappable to real experiments.

Manufacturability

Can this shape be made? Machinable, 3D-printable, SLM additive, theoretical only. Doesn’t affect physics scores but affects whether results are actionable.

Composition Slots

Adjacent geometries in a system. For future invariant composition studies — do invariants compose when primitives combine?

4 — Design Principles

USE EXISTING INFRASTRUCTURE BEFORE BUILDING

Free meshes on Thingiverse before modeling in Blender. Import from existing oracles before writing new physics. Published material properties before custom characterization. Existing frameworks (FEniCS, OpenFOAM, DEAP) before custom solvers.

“We realized architecture already existed that we could use for free instead, and shortened production time by 40-60% conservatively. Lets keep applying that logic going forward.”

EVERY PRIMITIVE ON ITS OWN TERMS

Each primitive gets its own folder, its own invariant-specific oracle, its own unique vector dimension, PLUS the shared dimensions for cross-comparison. Never measure a primitive on another primitive’s terms.

“I wont measure the Meissner body on the oloid’s terms, that doesnt even make sense.”

ADDITIVE ARCHITECTURE ONLY

New work goes in new folders. Existing codebase is a library, not a workspace. Import from it, never modify it. The oloid oracle files are frozen — they match a submitted paper and endorsement emails.

GRANULARITY SERVES CROSS-REFERENCING

A three-shape comparison is basic. A 10-primitive library with 5+ dimensions each, scored across multiple operating regimes, is a real search space. The library’s value is proportional to validated entries × scored dimensions × operating profiles tested.

“Once we have a rich enough dataset and computational simulation library it wouldnt be that difficult to just point you in the direction of an industry and cross reference that.”

5 — Path from Computation to Application

1

Define failure mode precisely

2

Identify geometric property that addresses it

3

Build or adapt oracle to measure it

4

Run oracle on candidates vs baseline

5

Output recommended experimental validation

The computation defines the experiment. The experiment confirms the prediction. The framework succeeds when it can take an engineering failure mode as input and return a geometric solution as output, with enough rigor that the recommended experiment is obvious and the predicted improvement has confidence bounds.

6 — What “Done” Looks Like for a Primitive

Formal invariant stated as computable predicate
Watertight mesh (generated, downloaded, or modeled)
Unique invariant-specific oracle scoring its claimed property
Full shared invariant vector (CDS, SDS, TDS, FDS, WDS minimum)
Baseline comparison with conventional geometry
Results across a load envelope (not just one load)
Material properties documented
Constraint geometry specified
Confidence bounds reported
Cross-domain transfer evidence
Manufacturability assessment
Recommended experimental validation defined
Primitive profile JSON in standardized schema

7 — Current Status

Completed

7 oracle artifacts for oloid
Complete 5D invariant vector
Two-tier structure identified
1,430-genome parametric search
Preprint submitted for endorsement
GitHub repo live
Dashboard deployed

Next Build

→ Generalized oracle runner
→ Meissner body (constant-width invariant)
→ Plasma electrode case study
→ DEAP evolutionary search
→ Invariant composition

Substrate library: 10 entries cataloged, 1 fully validated (oloid). Each additional validated entry increases the framework’s cross-referencing power.

Hypothesis Engine

Define a formal invariant and physics regime. The engine returns candidate primitives in substrate schema format — structured data, not narrative. Novel candidates are flagged with their construction path and the simulation tooling needed to validate them.

Pipeline state: AI reasoning layer active → FEniCS oracle: pending → DEAP evolutionary search: pending → manufacturability filter: pending

Invariant class
Physics regime
Engineering context
Target failure mode
Custom invariant statement (optional)
Candidate output — substrate schema format
Candidates will appear here in substrate schema format.
Each entry can be added to the Candidate Zone directly.