Praecise Engine v0.1.0 Read the docs

Documentation · Using it

Crates

  • llama-cpp-sys-2 — low-level FFI; pulls the llama.cpp backend (the Praecise fork, synced with upstream llama.cpp 1.0.0 of 2026-11-13; that sync is built on the CPU only, and no GPU backend has been compiled against it).
  • llama-cpp-2 — safe Rust bindings, including the speculative-decode primitives.
  • praecise-hardware — the hardware layer: which accelerators a machine has (every vendor, read from the operating system), which backend drives each, what a confined engine needs to reach them, the memory and bandwidth of the systems worth planning for, and the praecise-hw binary. No dependencies.
  • praecise-runtime — the backend-agnostic acceleration runtime and inference API.
  • praecise-host — runtime hosts and the engine set: confined, supervised engines, one per model, within one memory budget; job engines and the praecise-job binary.
  • praecise-remote — generation on an inference API outside the machine (Groq, Cerebras, SambaNova or any OpenAI-compatible endpoint), in the runtime's types. Opt-in: nothing opens a connection unless the application depends on this crate and the operator permits the host.
  • praecise-ffi — the stable C ABI over the runtime's backend-agnostic types (config, result, stop reason, error), for callers in other languages.
  • praecise-diffusion — flow-matching image, video, audio and 3D generation on the same ggml backend, device and memory budget as the language-model family.
  • praecise-provenance — signed C2PA content credentials embedded in generated PNG, WAV and MP4 files, and their verification.
  • praecise-train — the training substrate: the deterministic replayable step, the hash-linked step log, content-hashed checkpoints with lineage, objectives, optimizers and parameter-delta primitives.
  • praecise-codec — in-process video coding: H.264, H.265 and AV1 decoding from MP4 and Matroska/WebM, H.264 and AV1 encoding to MP4 (AV1 also to WebM) with an Opus soundtrack. Generated videos are written as MP4.
  • praecise-perception — video in, object tracks out: detection on every decoded frame, ByteTrack, nv.Frame output; the praecise-track binary.
  • praecise-onnx — the ONNX model families: speech-to-text, object detection, promptable and text-prompted segmentation, image encoders, time-series forecasting and text embedding. Sessions register the execution provider the machine's GPU needs (CUDA and TensorRT, MIGraphX, OpenVINO, QNN, CANN, CoreML, or DirectML and WebGPU on any vendor's GPU) and refuse a model they cannot accelerate rather than running it on the CPU. A neural processor is used when the operator asks for it.
  • praecise-moe — expert-parallel mixture-of-experts execution: expert FFNs and gating from safetensors blobs, GGUF block-quantized expert weights, a memory and disk residency cache, and the combine step, on the CPU (AVX-512-VNNI, AVX-VNNI, the Arm dot-product extension), CUDA or any other GPU through wgpu. The cuda feature builds for the CUDA toolkit that nvcc reports (12 or 13); cuda-12 and cuda-13 pin the version on a build host without a toolkit.

Edit this page on GitHub · Read it as Markdown

    Type to search. Arrow keys move, Enter opens.