Realm
The oa::Core engine and runtime substrate

One engine.
Every module borrows its power.

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.

A luminous ring inside an industrial engine installation

Audio

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

A dark sphere surrounded by luminous energy trails

Ml

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

A silver figure seated in a luminous lunar landscape

Vision

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

Colourful digital figures within a corridor of light

Ui & Plot

GPU-composed retained figures, diagnostics, heatmaps, image grids, and live Viewer output from the same semantic values.

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.

01

oa::Engine

The sole local owner of device, memory, queues, kernels, scheduling, and profiling. Every module borrows it through composition.
02

oa::matrix and semantic values

Stateless, schema-owned operations share validation, differentiation, lowering metadata, and paired language surfaces.
03

oa::Event

Every submission returns the exact completion value. Waiting, polling, dependency chaining, and failure remain deliberate boundaries.
04

oa::ExecutionPlan

Immutable captured work submits repeatedly without exposing the private Vulkan graph or rebuilding stable regions.
05

oa::core::memory

Checked ordinary and streaming copy, equality, and secure erasure. Vulkan uploads use the explicit streaming contract.
06

Vendor-neutral contracts

Applications express semantic work once. Kernel, precision, subgroup, and memory routes stay internal capability decisions.
07

Embedded kernel manifest

Kernels compile and validate at build time, embed behind stable identities, and fail closed when a required capability is absent.
08

Qualified hardware packs

The Core reference is Intel Iris Xe FP32. NVIDIA, AMD, mobile, and datacenter routes remain unverified until requalified.
The oa::Engine compute substrate

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

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::ExecutionPlan captured Vulkan replay graph

One library. Across the stack.

Follow the same Engine, values, and explicit execution contract into another module.