---
title: SHOW Semantic Definitions
url: https://nexyron.tech/docs/cypher/clauses/schema-and-admin/show-abstraction-definitions
description: The abstraction catalog now has direct Cypher discovery clauses for the schema level abstraction definition families:
---

# SHOW Semantic Definitions

## Generic Description

The abstraction catalog now has direct Cypher discovery clauses for the schema-level abstraction definition families:

-   `SHOW FEATURES`
-   `SHOW INTERVENTIONS`
-   `SHOW SCENARIOS`
-   `SHOW SNAPSHOTS`
-   `SHOW SPLIT POLICIES`
-   `SHOW DATASETS`
-   `SHOW MODELS`
-   `SHOW POLICIES`
-   `SHOW ANALYSIS RUNS`
-   `SHOW REPORTS`

Example:

```cypher
SHOW FEATURES
```

```cypher
SHOW ANALYSIS RUNS
```

## Consumer-Level Explanation

Use these clauses when you want to inspect what the abstraction platform currently knows without dropping into procedure form.

They are the discovery pair for the new `CREATE ... OPTIONS { ... }` abstraction DDL family.

## Conceptual Explanation

`SHOW ABSTRACTIONS` already exposed the first abstraction layer.

These `SHOW` clauses extend that idea to the rest of the abstraction platform:

-   feature definitions
-   intervention definitions
-   scenario definitions
-   snapshot contracts
-   split-policy contracts
-   dataset contracts
-   model contracts
-   policy contracts
-   analysis-run artifacts
-   report definitions

That makes the abstraction stack more visible as database metadata rather than only as procedure-managed state.

## Advanced Example

```cypher
SHOW MODELS;
SHOW POLICIES;
SHOW DATASETS;
SHOW ANALYSIS RUNS;
SHOW REPORTS;
```

That is useful when you want to verify the current abstraction execution surface before running:

-   `feature_serve`
-   `snapshot_build`
-   `dataset_build`
-   `model_score`
-   `policy_decide`

## Real Use Cases

-   Confirm which model and policy contracts are active before applying interventions.
-   Confirm which analysis runs are registered before using `APPLY ANALYSIS RUN`.
-   Confirm which abstraction report definitions exist before rendering or refreshing report artifacts.
-   Inspect which features a snapshot is wired to before changing the feature set.
-   Review which datasets and split policies exist before training or evaluation work.

## Real Limitations And Tradeoffs

-   These clauses expose catalog definitions, not materialized runtime artifacts.
-   They do not show execution freshness, materialization state, or queued refresh work. Those are still procedure-level operational surfaces.
-   They are list/discovery clauses, not detailed explainability tools.
-   `SHOW REPORTS` lists report definitions stored in the target database. Private Studio layout state and assistant conversation state are separate operational data.