
Core
One engine.
Every module borrows its power.
A capability-gated Vulkan runtime and semantic value system that Audio, Ml, Vision, Ui, Plot, Crypto, and Render borrow without ever seeing the device machinery beneath.
Library
The modules that live above Core.
Every domain in the Oa Library—Audio, Ml, Vision, Ui, Plot, Crypto, Render— borrows one oa::Engine and shares the same semantic value contracts.

Audio
Waveform decode, GPU DSP, spectral features, and direct handoff to the Ml stack through one Float32 matrix contract.

Ml
Autograd, optimizers, dense and sparse models, grouped Mamba-3, and semantic Q4/Q8 through one capability-gated runtime.

Vision
Image transforms, JPEG/PNG decode, GPU detection metrics, and Vulkan video decode behind one vendor-neutral surface.

Ui & Plot
GPU-composed retained figures, diagnostics, heatmaps, image grids, and live Viewer output from the same semantic values.
Contracts
The primitives every module builds on.
One API, capability-gated routes. oa::Engine owns local execution while domain modules such as oa::matrix preserve the semantic contract across Rust and Python. Hardware-specific decisions stay private; unsupported and unqualified routes stay explicit.
oa::matrix and semantic values
oa::Event
oa::ExecutionPlan
oa::core::memory
Vendor-neutral contracts
Embedded kernel manifest
Qualified hardware packs

Compute Engine
oa::Engine
The all-seeing eye. One pinned object holds the local compute world— device, memory, queues, kernels, scheduling, and profiling. Every matrix, image, waveform, frame, and plot moves through a single point of consciousness; the modules borrow its power without seeing the machinery beneath.
Operations describe intent, submission returns the exact oa::Event, and recurring work condenses into immutable oa::ExecutionPlan values while the semantic graph stays separate from the executable Vulkan graph.
oa::Engine
Ownership
oa::Event
Completion
oa::ExecutionPlan
Replay
oa::matrix
Operations
Captured Execution
oa::ExecutionPlan
Capture a reusable semantic region once, receive an immutable oa::ExecutionPlan, then submit it through the same oa::Engine and exact-event completion contract as eager work.
The private executable graph tracks resource reads, writes, aliases, lifetime edges, barriers, and lowering provenance. The public plan owns replay, not raw Vulkan graph authoring or inspection.
Automatic OaDnn capture and training-program replay use this same boundary. Performance claims remain workload-, device-, driver-, and measurement-specific.

Oa Library
One library. Across the stack.
Follow the same Engine, values, and explicit execution contract into another module.