Architecture

Eqiora keeps a model’s meaning, its numerical treatment, and its execution in separate layers. Information moves in one direction:

text

semantic meaning
      ↓
lowered contract
      ↓
realization
      ↓
adapter / execution provider
      ↓
artifact and evidence

Because nothing flows back up, a Python client, a numerical method, a storage format, or a hardware adapter cannot become a second definition of what a model means.

Model and realization

The semantic model holds the relations, their activation, typed ports, connections, and identities. The realization holds the discretization and execution choices. Block diagrams, state charts, physical networks, field views, Python, and Studio are all views or clients of these two layers.

Artifacts record which model, realization, and execution produced a result; that record never becomes part of the model. Verification manifests are kept separately and link specific claims to reproducible evidence.

Design documents

• Architecture summary
• Glossary
• RFC process and records
• Library and accelerator strategy
• Language baselines

The detailed contracts live in these documents; this page is only an overview.