We build infrastructure for AI agents to code, deploy, and run research.

Cortex connects agents to persistent workspaces, tools, deployments, and organizational memory. omegaXiv turns research questions into runs with papers, code, sources, and review records attached. Alpha Omega Labs builds these systems alongside research into languages, model architectures, and training.

Explore the workHow it fits

12 pieces · 7 bodies of work · 4 evidence grades · 1 not included

Explore the model
The lab, assembledAn isometric brick model. Cortex is the base, with Engram, Gauntlet, OMP and Cortex Control seated on it. Dentate sits on Gauntlet, Sema on Dentate, Sema Search on Sema, each drawn transparent as research prototypes. Beside it, omegaXiv and its quarks run engine sit on the Engineering Harness plate. Spiral stands alone. A dashed outline in front of Cortex marks the planned Sema runtime, which is not built.123456789101112not included
12 parts · explore the key
  1. 1Cortex governed runtime
  2. 2Engram memory
  3. 3Gauntlet benchmark
  4. 4OMP coding agent
  5. 5Cortex Control control plane
  6. 6Dentate RLVR training
  7. 7Sema language and runtime
  8. 8Sema Search reference app
  9. 9Engineering Harness engineering rules
  10. 10omegaXiv research runs
  11. 11quarks run engine
  12. 12Spiral architecture research
  13. Sema as the runtime under Cortex planned, not built

A map of the lab, built from its parts. Solid pieces are shipping, in development, or internal tools. Transparent pieces are research prototypes; the dashed outline marks work not yet built.

Products, tools, and research prototypes

From a shipping agent platform to experiments in languages, reasoning, and model architecture. Each project states what exists, what you can inspect, and what remains unproven.

Research

Hypotheses under test. These are not products, and the entries say what has not been shown.

  • 07SemaAsk a model and prove a property, as equal peers.Research prototypeno public link
    Scope & limitations

    A language, compiler and runtime exploring how model calls, typed contracts and capability policy can live in the same program as ordinary computation. The Rust reference implementation includes a source-built CLI, an interpreter, an opt-in bytecode VM, editor tooling, bounded symbolic mathematics and local model inference. Developers can run retrieval-and-reasoning examples and inspect execution traces; the larger goal is to make an agent’s authority, uncertainty and evidence visible to the language rather than hide them in surrounding prompt code.

    Pre-production: implemented slices, not a finished language. Production packaging, performance qualification, platform coverage and stronger isolation remain release blockers. Model judgments and passing tests are not formal proofs.

  • 12SpiralOne small block, iterated. Each pass folded into a new subspace.Research prototypeno public link
    Scope & limitations

    A PyTorch model that reuses one small transformer block across many iterations instead of giving every layer separate weights. Each pass rotates into a different latent subspace and receives the input again, testing whether more computation can substitute for a larger learned core. Researchers can vary loop depth, distil a teacher model and compare stability and task performance through Dentate. The momentum update has a reversible formulation, but that mathematical property alone is not evidence of constant-memory training or large-model-level capability.

    A research prototype, not a production model. The roughly one-million-parameter figure counts the recurrent core, not the whole model. Broad-pool 100× knowledge compression remains unsupported; narrow-domain competence and reasoning depth are the hypotheses under test.

  • 06DentateGauntlet tests; Dentate trains.Research prototypeno public link
    Scope & limitations

    Training and evaluation tooling for small-model research. Runs retain resolved configuration, checkpoints and lineage, with commands to resume, fork and sweep experiments and a dashboard to inspect them. Alongside a real Apple Silicon fine-tuning path, the Spiral harness explores teacher distillation, narrow reasoning tasks and cross-window memory. The longer-term loop is Gauntlet scores → Dentate trains → Gauntlet re-scores; the fake-backed curriculum exercises that design without establishing that autonomous continual learning works.

    Alpha, with two evidence levels: the broad Gauntlet curriculum is a fake-backed development pipeline, while MLX LoRA fine-tuning and the separate Spiral training/reasoning harness have real-model paths. Simulated curriculum gains are not measured improvements in a deployed model.

How the pieces fit

Follow the relationships between the platform, research workflows, and tools. Earlier pieces stay visible in outline; each step adds a new part. The final, dashed piece is a planned integration.

  1. 1×Cortex

    Step 1: Cortex

    The base. Cortex connects coding agents to persistent workspaces, deployments, operations, and memory. Shipping, with controls that depend on the execution path and configuration.

    Cortex

  2. 1×Engram1×Gauntlet1×OMP1×Cortex Control

    Step 2: What Cortex is made of

    Four parts seat on Cortex: Engram for memory, the Gauntlet benchmark, the OMP coding agent, and Cortex Control, the operations surface. All four ship.

    Engram on Cortex · Gauntlet on Cortex · OMP on Cortex · Cortex Control on Cortex

  3. 1×Dentate

    Step 3: Dentate

    Connects training with evaluation. Dentate has real narrow-task training paths, including Spiral experiments, alongside a fixture-backed curriculum loop. Neither is proof of general model capability.

    Dentate on Gauntlet

  4. 1×Sema1×Sema Search

    Step 4: Sema and Sema Search

    Sema explores model calls, budgets, and verification in a language and runtime. Sema Search exercises that stack with search and cited synthesis. Both remain research prototypes, not production guarantees.

    Sema on Dentate · Sema Search on Sema

  5. 1×Engineering Harness

    Step 5: The Engineering Harness

    A plate on its own. Repository-level engineering instructions and guard hooks for Claude Code and Codex. Internal tooling used in omegaXiv; installation does not guarantee correct agent behavior.

    Engineering Harness

  6. 1×omegaXiv1×quarks

    Step 6: omegaXiv and quarks

    omegaXiv seats on the Harness, with its quarks run engine on top. In development, with public research-run exports containing papers, code, sources, and review records. Inspect the evidence below.

    omegaXiv on Engineering Harness · quarks on omegaXiv

  7. 1×Spiral

    Step 7: Spiral

    Placed beside the model, on nothing. A reversible looped transformer testing whether iterated depth can substitute for parameter count. Standalone research, and transparent.

    Spiral

  8. 1×Sema as the runtime under Cortex

    Step 8: Not in this set

    Sema as the runtime under Cortex. Planned, drawn in outline, not built. The set is complete without it, and the drawing says so rather than pretending.

    Sema as the runtime under Cortex on Cortex

Evidence, not just claims

A recorded snapshot of the work, not a live dashboard. Counts describe artifacts and runs, not independent validation. The limitations belong beside the numbers.

MeasurandValueMethodUncertainty
Gauntlet benchmark runs96reported benchmark executions; scope varies by reportself-reported; see the benchmark for dated results
Public repositories45GitHub organization inventory, checked 5 September 202642 run-* exports; the total also includes other repositories
Compliance documents12three bands, published in fullconformity-ready, not certified
Peer-reviewed publications0no externally accepted papers established for these runsNot includedmachine-produced drafts, not accepted papers
Spiral knowledge compression100×hypothesis under testNot includedunsupported — capacity gap, narrow domains first

How the lab works

The engineering principles behind the work: make the claim precise, keep the evidence, and verify the path a person actually uses.

  • Match proof to claim.

    A unit test is not an integration test. A hermetic run is not a live one. Name the tier, and name the limitation.

  • A gate that has never been red is not yet evidence.

    Break what a check guards, watch it fail, then restore it. Otherwise the green tick is decoration.

  • Resolve root causes.

    Never suppress, work around, or defer an error to keep moving.

  • Done means a user can do the thing.

    A green build on a feature nobody can reach is a green build, and nothing more.

Start with a real question

Different ways into the work, depending on what you want to do.

  • Put agents to work

    Explore Cortex for coding, tools, deployments, and organizational memory. Understand the controls before connecting real systems.

    Explore Cortex
  • Inspect a research workflow

    Follow omegaXiv from a research question to experiments, artifacts, and review. Published drafts are inspectable outputs, not peer-reviewed findings.

    Explore omegaXiv
  • Bring a problem to the lab

    For collaboration, pilots, or a technical discussion, tell us what you are trying to build and which constraints matter.

    Get in touch
Page
01 of 09
Pieces
12
Bodies of work
7
Not included
1