Architecture

Eqiora is organized around one directional path:

text

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

This direction prevents authoring clients, numerical methods, storage formats, or hardware adapters from becoming alternate sources of model meaning.

Two layers, several projections

The semantic model owns canonical relations, activation, typed ports, connections, and identity. The realization owns discretization and execution choices. Block diagrams, state charts, physical networks, field views, Python, and Studio are projections or clients of those shared contracts.

Artifacts bind exact model, realization, execution, and result lineage without turning provenance into model semantics. Verification manifests separately bind bounded claims to reproducible evidence.

Authoritative design material

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

These repository documents, not this overview, define the detailed contracts.