Concepts
Concepts explain why FHElium is structured as it is. They describe stable mental models, invariants, ownership rules, and mathematical semantics.
Choose a reading path
Write a correct evaluatorStart with the programming model, value identity, primitive state transitions, and the scale-level lifecycle.→Use multiple GPUsUnderstand the rank-local SPMD model before choosing communication semantics.→Repeat execution within bounded memoryConnect exact signatures, CUDA Graph execution, and residency lifetimes.→Optimize a workloadEstablish the CKKS cost model before selecting an optimization mechanism.→Compose CKKS bootstrappingCombine replaceable mathematical components in an engine-bound callable.→Use JIT programsRelate one mixed-dialect Program to structural validity, selected passes, retained runtime capabilities, and readiness.→Modify the native operator stackTrace ownership responsibilities and state transitions before entering the engine and native stack.→
The conceptual map
The main conceptual families are:
| Family | Scope |
|---|---|
| Architecture | Responsibility ownership across system layers |
| CKKS semantics | Context, value identity, primitive transitions, scale-level laws, and evaluator state effects |
| Distributed execution | Mathematical relationships among rank-local values |
| Execution and lifecycle | Exact-value staging, repetition, persistence, and retention |
| Features | Composable CKKS bootstrapping and JIT program construction, transformation, and execution |
| Performance | Operation costs and optimization effects |
| Glossary | Definitions of FHElium terminology |