Abstract

This paper presents GENESIS Inference Co-Design Suite, 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 3 project tests successfully. No accelerator, deployment, or performance conclusion is inferred unless a corresponding committed benchmark or profiler artifact exists.

Introduction

GENESIS Inference Co-Design Suite (GENESIS) addresses a bounded problem within the portfolio’s track-05-hardware-software-codesign 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: GENESIS-genesis-inference-codesign-suite.tex.

Technical Context

Hardware–software co-design links analytical models, workload evidence, accelerator mappings, and operator tools. Modeled, simulated, and measured values must remain distinguishable so design tradeoffs are not overstated. 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:

$$D=\{(m_i,v_i,s_i,\ell_i)\},\quad v_i=\mathrm{null}\ \text{when evidence is absent}$$

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/evidence_table.py. Unsupported real-world conditions are surfaced as limitations rather than silently simulated.

Detailed Script Operation and Rationale

The evidence-table script reads the latest VORTEX and LUMEN JSONL records, preserves source and limitation fields, represents missing evidence explicitly, and writes a comparison artifact. Its purpose is to prevent unrelated or absent measurements from becoming misleading zero-valued comparisons.

The execution path is:

1. Locate the latest available evidence for configured source projects.

2. Parse the final valid JSONL record without changing provenance.

3. Represent absent files and metrics as missing rather than zero.

4. Build a normalized comparison-oriented JSON structure.

5. Write the report for later tradeoff charts and dashboard ingestion.

Implemented Prototype

The metadata and source audit found these completed features :

• Provenance-aware VORTEX/LUMEN evidence reader

• Explicit missing-evidence handling

• Generated JSON comparison table and tests

On August 14, 2026, python3 -m unittest discover -s tests -p ’test_*.py’ completed successfully with 3 tests. The inspected test artifacts are tests/test_evidence.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 3 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:

• Cross-project performance is not directly comparable 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. Normalized metric schema

2. Tradeoff charts

3. ASTRAEUS/AETHERSIM evidence ingestion

4. Add statistical comparability checks and uncertainty-aware Pareto analysis.

5. Expose provenance-linked tradeoff views through 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

GENESIS Inference Co-Design Suite 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.