Verified evidence
Operational claims require inspectable receipts, demonstrations or reproducible verification.
04
Holdings /::/ Horizons
What exists. What follows.
The transparent record of Asentxia’s architecture, products, systems, evidence boundaries, technical lineage and development direction.
Canonical registry
Confidence requires classification.
| Holding | Role | Public status | Scope |
|---|---|---|---|
| DCA foundation | Reference architecture | Canonical definition | Seven responsibilities, Cognitive Interface and Effect Boundary |
| Continuum | Core product | Canonical product definition | Asentxia’s flagship implementation of DCA |
| VERA | Principal model | Canonical definition | Verifiable, Enduring, Responsible Autonomous principal |
| The Regency | Governance product | Canonical product definition | Constitutional authority, policy and governance for autonomous systems |
| Operations & engineering | Supporting systems | Evidence review | Supervision, verification and governed system evolution |
| Network & exchange | Ecosystem systems | Architecture horizon | Discovery, trust, routing, exchange and settlement interfaces |
| Applied reference systems | Conformance environments | Evidence review | Cyber defense, science, markets and autonomous engineering |
Evidence standard
Architecture is defined here. Operation must be proved.
Explicit limits
Unresolved work, integration boundaries and unknown outcomes remain visible in the formal record.
Provenance
Origins, dependencies, external attribution and historical lineage stay attached to the work.
Release horizons
Near-term development and longer research directions remain distinct from present capability.
Public boundary
No theater of certainty.
The main site presents the complete architecture and product definition. This page preserves the crucial distinction between what is defined, what is integrated and what has been independently demonstrated.
Why Asentxia works this way ↗