The compute pipeline is the computation side of CoFHE. Contracts never call it. It subscribes to what happens onchain, does the encrypted math, and anchors the results.
Four components make up the pipeline. Each one owns a single step, and work moves in one direction.
Slim listener
The slim listener watches TaskManager events on every host chain the pipeline serves.TaskCreated events bring FHE operations in for execution. InputVerified events bring verified encrypted inputs in, so a commitment gets anchored for each.
Delivery is reliable by construction. The listener tracks the last processed block, so a crash or a missed range is re-scanned rather than skipped.
FheOS
FheOS checks that each operation is well formed and that the inputs it references exist. It holds the operation state for the pipeline. Operations can arrive before the inputs they depend on have finished computing. FheOS defers such operations and releases them once the missing results land, so out-of-order arrival never produces a wrong answer. Work that is malformed, or that references inputs that never materialize, is set aside for inspection instead of being silently dropped.FHE Engine
The FHE Engine runs validated operations against the TFHE library: arithmetic, comparison, select, cast, and random generation on encrypted operands. It reads its operands from the ciphertext store and writes the result back. The result ciphertext is stored under the handle the TaskManager issued. Any deferred operations waiting on that handle are released as soon as it lands. Note the name. The FHE Engine is one component inside the compute pipeline, not the pipeline itself.Blockchain poster
For every stored result, the pipeline produces a commitment, thekeccak256 hash of the stored ciphertext bytes. The blockchain poster batches those commitments and posts them to the CommitmentRegistry on the registry chain.
This is the anchor Teecryptor verifies before decrypting anything. Only bytes that hash to a registered commitment ever reach the decryption key.