Home/Catalog

// VERSION 6.2

Public Application
Catalog.

Complete reference of structural diagnostic applications across five domains and five license clusters. Source of record: catalog.public.json

107Total Applications
91Technical Domains
5Meta-Domain (SOV)
11Non-IP (COSMO)
5Domains
5Clusters

Catalog Architecture: Four Structural Axes

The catalog is organized through four structural axes. Domain defines the problem space, Cluster defines the structural regime class, Application defines the recurrent structural problem form, and Structural Dimensions V1–V4 define the diagnostic grammar used to read observations, structural causes, effect spaces, and decision surfaces.

Domains — the What

LabelIDTypeApps
AIai-systemsTechnical52
CXcomplex-systemsTechnical28
QSquantum-systemsTechnical11
SOVsovereignMeta-Domain5
COSMOcosmologyNon-IP11

Clusters — the How

ClusterLabelStructural Focus
ACouplingPhysical and logical coupling
BLearningTemporal adaptation
CControlOperative control & coherence
DEmergenceEmergent, non-linear behavior
EEvidenceTraceability & auditability

Applications — the Recurrent Form

Applications are not deployment-specific use cases and not software modules. They are reusable structural problem forms inside a cluster. Examples include AI.01 Interconnect Stability Control, AI.04 Runtime Control Coherence, and AI.13 Agentic System Stability.

IDApplicationCluster
AI.01Interconnect Stability ControlA — Coupling
AI.04Runtime Control CoherenceC — Control
AI.13Agentic System StabilityD — Emergence

Structural Dimensions V1–V4 — the Why

V1–V4 provide the diagnostic grammar. V1 identifies the observed structural phenomenon. V2 identifies the structural cause or coupling relation. V3 identifies the structural effect space. V4 identifies the decision, utilization, or evidence surface.

Dim.Reading
V1Observed phenomenon
V2Structural cause / coupling
V3Effect space
V4Decision / evidence surface

Key Principle

Domains are the What — problem spaces and interpretation contexts.
Clusters are the How — structural regime classes.
Applications are the Recurrent Form — reusable structural problem forms inside a cluster.
Structural Dimensions V1–V4 are the Why — the diagnostic grammar from observation to decision or evidence surface.
Scenario Class → Metric Set → Regime Classification is the inner application reading layer, not a fifth main axis.

For the public methodology behind this catalog structure, see the Structural Assessment Methodology. The Methodology page explains how Domain, Cluster, Application, V1–V4, Scenario Class, Metric Set, Regime Classification, and Evidence Interface connect into the public analysis layer.

Core-3 Entry Points

The Core-3 applications serve as primary entry points into the AI structural assessment space. They span three complementary coupling regimes: physical/interconnect coupling, logical/runtime-control coupling, and semantic/agentic coupling. Clusters B and E remain part of the wider catalog but are not part of the current Core-3 evidence release.

AI.01 · Cluster A

Interconnect Stability Control

Structural stability diagnostics and control for interconnect induced performance collapse in distributed AI and HPC systems.

View Demo → AI.04 · Cluster C

Runtime Control Coherence

Diagnose and reduce incoherence between scheduler, runtime and model control loops.

View Demo → AI.13 · Cluster D

Agentic System Stability

Stability control for agent workflows with retry loops, self verification, and tool calling patterns.

View Demo →

License Structure

License options for technical domains (AI, CX, QS) are structured around cluster combinations. The Sovereign meta-license supplements technical licenses.

Technical Domain Options

Infrastructure Only

A

Coupling analysis only. No training, agentic, or evidence scope.

Core-3 Coverage

A C D

Infrastructure, control, and emergence. No training or evidence scope.

Full Technical

A B C D

Complete technical coverage. No evidence use.

Full Domain

A B C D E

Complete coverage including evidence and auditability.

Sovereign Meta-License

The Sovereign license is a meta-license that supplements technical cluster licenses. It addresses decision capability, traceability, and strategic risks. Sovereign projects results from AI, CX, and QS onto governance level.

Cluster Scope: A C E only (Clusters B and D excluded)
Target Groups: Government, regulatory, sovereign cloud, procurement, legal

Cluster Distribution

Application distribution across domains and clusters.

Technical Domains

DomainABCDETotal
AI266910152
CX10467128
QS4132111
Sum40111819391

Meta-Domain (Sovereign)

DomainACETotal
SOV2125

Clusters B and D excluded in Sovereign.

Non-IP (Cosmology)

DomainTotal
COSMO11

Scientific publications only. No cluster assignment.

Browse Applications

Showing 0 applications