Public whitepaper · engine emit

Omega Engine — Whitepaper.

Generated:
Source: active blocks in C:\Omega\logic-base ·

● loading… ● loading… load-clean · … provenance failures · … schemas verified · … conductor · …
public tools · … products · … quarantined · … governor gate · …

Abstract

Omega is a sovereign, self-building code engine. Logic is canonical — stored as content-addressed contracts on a frozen address space. Source code is disposable output, emitted deterministically from each contract's logic-IR by per-tier templates. The engine ingests real code, decouples it into shared single-responsibility atoms addressed by a frozen CNAE vocabulary, gates every contract through an immune system (sovereign imports, no stubs, no inline logic at T2+, real logic density, CNAE-valid), autowires emergent compositions across sources, and re-emits the entire source tree from contracts on demand. The DNA store is the only source of truth; the rendered code can be wiped and recovered byte-identically.

This whitepaper is itself an emit — it was rendered from a template against the live logic-base. The numbers above are the engine's current state, not a snapshot from press time.

§ 1The One Principle

Logic is the only source of truth. Code is a deterministic projection of it.

Because each atom's name encodes its location (action_entity_scope), the engine never needs a stored dependency graph. It computes every import from the callee's name. A tiny compliant seed can assemble the whole tree because composition is implicit in the names.

§ 2Architecture

2.1 The Tier DAG

Imports go downward only — never same-tier or upward. This is mechanically enforced.

TierRole
T0axioms / constants — frozen primitives
T1single-purpose leaves — the primitive logic (parsers, validators, scorers)
T2composites — no inline logic, only compose lower atoms
T3state / IO — read+write the world
T4orchestrators — temporal flows
T5products — what customers run
T6internal ecosystem — engine-internal coordination
T7public surface — APIs, SDKs, MCP
T8swarm — multi-engine coordination

2.2 CNAE — Names as Addresses

Every atom is named action_entity_scope. 54 frozen actions, 12 frozen scopes. Scope fixes the tier. Frozen so addresses are stable → auto-wire, dedup, and reuse all work.

The live per-action histogram is emitted alongside this document at ATOMS.md in the engine docs suite; it changes every cycle as the engine grows.

2.3 The Immune Gate

Every contract must pass before emit:

  1. Sovereign imports — T0–T4 may import only stdlib + atomadic.*. No external dependencies in the core.
  2. No stubs, no echo-shells — no NotImplementedError, no pass # TODO, no template bodies.
  3. No inline logic at T2+ — T2 and above compose, they do not implement. Implementation lives at T0/T1.
  4. Exactly one public callable — one function per file.
  5. Real logic density — bodies are checked for substantive AST node counts vs trivial echoes.
  6. CNAE-valid — name decomposes into a known action + entity + scope.

Harvest is permissive on the name (we will reclassify a bad name from the source/docstring) but strict on the logic. The engine never accepts a stub.

2.4 Self-Build

The engine implements every capability an agent can perform, as a native atom:

The engine can sit and run all of these on its own. A missing capability is the next thing to emit (Axiom 2 — invent it).

§ 3Sovereignty Invariants

Current verdict: loading from /.well-known/atomadic-closure.json…

Verify yourself: pull /.well-known/atomadic-closure.json and check the Ed25519 signature against /.well-known/atomadic-issuer-pubkey.json. The omega-verification-kit does it offline in five lines.

§ 4The Three-Workspace Topology

WorkspacePurpose
C:\Atomadic-Compliant (FORGE)authoring workspace — templates, specs, MCP server source, bootstrap scripts
C:\Omega-Shadow (SHADOW)emit-only promotion testbed — first render target, gated before promotion
C:\Omega (STABLE)emit-only canonical — the live engine; promoted from shadow

A read-only hook enforces emit-only on src/atomadic and DNA across all three.

§ 5Documentation as Emit

This document, like every other in the suite, is itself an emit. The doc generator (orchestrate_documentation_suite_temporal) reads the live logic-base, builds a context variable map from the truth, and renders templates from C:\Atomadic-Compliant\docs\_templates. After major emits or on cycle, orchestrate_post_emit_doc_refresh_temporal regenerates the suite and syncs the NotebookLM lobe so the operator's planning oracle is always grounded on current truth.

If you read this and the numbers above feel wrong, regenerate: omega_refresh_docs_and_lobe.


Whitepaper emitted by omega_generate_docs against C:\Omega\logic-base. Source template: polished-sota-demo/public/whitepaper.md.tmpl. Live numbers are fetched at page load from /state_of_truth.json and /.well-known/atomadic-closure.json — if you read a stale value, hard-refresh.