Abstract

This paper presents VORTEX Roofline Lab, a project in a twenty-project AI infrastructure portfolio. The current repository is an active prototype with implemented behavior, automated correctness tests, and explicit boundaries around unverified hardware or production claims. We describe the system model, current implementation, goals, and evaluation method, then propose five integrations that advance the project toward reproducible system-level validation. A local audit on August 14, 2026 executed 8 project tests successfully. No accelerator, deployment, or performance conclusion is inferred unless a corresponding committed benchmark or profiler artifact exists.

Introduction

VORTEX Roofline Lab (VORTEX) addresses a bounded problem within the portfolio’s track-01-gpu-kernels track. Its declared status is Active Prototype . The project validates its central mechanism before adding device-specific acceleration, production orchestration, or real-world hardware. This ordering matters because optimization without a trusted reference can make incorrect behavior appear successful.

The project goals are to establish deterministic behavior, encode correctness as tests, create machine-readable evidence, identify limiting resources through measurement, and integrate results with adjacent portfolio systems without losing provenance. The repository contains one paper named exactly after its singular folder: VORTEX-vortex-roofline-lab.tex.

Technical Context

GPU kernel development requires a correct numerical reference before optimization. Reference equivalence, workload shape, warm-up policy, and profiler evidence are therefore first-class design concerns. The portfolio benchmark standard requires environment, workload, method, metric, artifact, reproduction, and limitation fields; unknown values remain explicitly unmeasured .

System Model and Architecture

The prototype is organized around the following domain model:

$$I=F/B,\quad P_{attainable}=\min(P_{peak},BW\,I)$$

The equation is a design and test abstraction rather than a claimed empirical law. It supports invariants and expected-value checks while later implementations replace synthetic inputs with representative workloads or devices.

The software architecture contains an input/configuration layer, a deterministic core, validation and evidence output, and a local visualization. The principal inspected source artifacts are python/compare_python_numpy.py, python/run_baseline.py. Unsupported real-world conditions are surfaced as limitations rather than silently simulated.

Detailed Script Operation and Rationale

The baseline script creates deterministic vectors, computes element-wise addition with a readable Python reference, checks every output, measures repeated execution, and appends environment-aware JSONL evidence. The companion comparison script runs the same workload with Python lists and NumPy so implementation overhead can be studied before an XPU port.

The execution path is:

1. Validate size, repetitions, warm-ups, and deterministic seed.

2. Generate two repeatable input vectors and compute the Python reference output.

3. Check output correctness before accepting any timing sample.

4. Measure repeated runs and summarize latency and throughput.

5. Attach Git/system metadata and append a JSONL record for review.

Implemented Prototype

The metadata and source audit found these completed features :

• Beginner-readable Python CPU vector-add reference

• Deterministic synthetic input generation

• Correctness validation and unit tests

• JSONL benchmark evidence writer with Git metadata

• Optional Python-list versus NumPy comparison

On August 14, 2026, python3 -m unittest discover -s tests -p ’test_*.py’ completed successfully with 8 tests. The inspected test artifacts are tests/unit/test_python_numpy_comparison.py, tests/unit/test_vector_add_reference.py. This is evidence of local correctness for encoded cases, not production scale or hardware performance.

Testing Methodology and Observed Results

Testing uses Python’s standard unittest discovery and exercises the public behavior of the reference implementation. The audit reran the suite from the project folder with python3 -m unittest discover -s tests -p ’test_*.py’. All 8 discovered tests passed. The result establishes correctness only for the encoded local cases; it does not establish accelerator correctness, real-device behavior, production reliability, or benchmark completion.

No numerical performance result is promoted by this test run. Where scripts emit JSON or JSONL, those outputs remain raw or simulation-specific until a reviewed summary includes hardware, software, workload, warm-up, repetition, correctness threshold, Git revision, and limitations.

Claim Boundaries and Risks

The project records these unverified or excluded claims:

• No XPU speedup or roofline result has been demonstrated yet

The main risk is confusing synthetic or modeled behavior with deployed-system behavior. Other risks include incomplete workloads, platform-dependent timing, missing failure injection, and interfaces not yet exercised across device boundaries. Performance claims require a reviewed record meeting the portfolio standard.

Evaluation Plan

Evaluation proceeds through correctness tests, deterministic reproduction with Git and environment metadata, repeated benchmarks reporting latency/throughput/memory/error metrics, and a named profiler capture tied to exact hardware and source revision. Success requires reference equivalence within a documented tolerance, preservation of safety and resource invariants, clear failures, and evidence reproducible from a clean environment.

Goals, Milestones, and Success Criteria

The project goals are staged so that correctness precedes performance and integration. A goal is complete only when its proof artifact is committed or otherwise reviewable; prose or a simulated number alone is insufficient.

Future Work and Integrations

The five project-specific next steps are:

1. Intel XPU implementation

2. Profiler capture and roofline analysis

3. Implement and validate equivalent SYCL and PyTorch XPU kernels.

4. Publish a reviewed roofline report linked to a named profiler capture.

5. Feed normalized benchmark summaries into GENESIS and POLARIS.

The early items complete declared evidence; the later items connect downstream portfolio consumers. Each integration should add tests and a reviewable artifact such as JSONL evidence, a report, profiler capture, deployment manifest, trace, or labeled data set.

Conclusion

VORTEX Roofline Lab is an evidence-aware active prototype: its implemented behavior and tests are real, while unbuilt hardware, deployment, and performance goals remain labeled. Completing the five integrations in dependency order will advance it from a learning artifact toward a credible portfolio component.