---
title: nexyron.procedures
url: https://nexyron.tech/docs/cypher/procedures/catalog-and-projections/nexyron-procedures
description: List the currently registered procedures and their output signatures.
---

# nexyron.procedures

## Generic Description

List the currently registered procedures and their output signatures.

Simple example:

```cypher
CALL nexyron.procedures()
```

Catalog and projection procedures manage projected graphs, aggregate views, procedure metadata, and abstraction graph projections used by analytical workflows.

## Consumer-Level Explanation

Use `nexyron.procedures` when list the currently registered procedures and their output signatures is the graph-analysis or operational question you actually need to answer. Keep the call explicit because its `YIELD` columns, row grain, and required runtime state determine how the rest of the Cypher pipeline can safely compose it. Use these procedures when the query needs to inspect or maintain derived structures explicitly instead of assuming they already exist.

## Conceptual Explanation

`nexyron.procedures` should be read as one named procedure contract in the broader Nexyron Cypher surface. The procedure call is not only a syntax hook: it defines what runtime state, projection, registry entry, or graph algorithm is being asked to operate, and it determines which output columns downstream `YIELD`, `WITH`, and `RETURN` stages can safely use.

## More Detailed Explanation

This is the source of truth for what the current build actually exposes. It is especially useful in a codebase where feature flags can materially change what the runtime can do

In practical queries, start by deciding the row grain you want after the call: one row per node, one row per path, one row per registry object, one row per artifact, or one row per summary. Then keep that grain explicit with `YIELD` and named projections. That is the difference between a useful planner-facing example and a vague call that downstream tooling cannot safely compose. For contract-driven procedures, the executable examples on these pages intentionally inspect procedure metadata unless the required named artifacts are created in the same example.

## Advanced Example

This example yields named columns from `nexyron.procedures` and returns a bounded result shape that downstream planner tooling can compose without guessing column names or row grain.

```cypher
CALL nexyron.procedures() YIELD name, description, parameters, output_columns
RETURN name, description, parameters, output_columns ORDER BY name
```

## Real Use Cases

-   tooling bootstrap
-   debugging feature-flagged builds
-   verifying procedure names and columns before writing queries
-   inventory projected graphs, aggregate views, and procedure metadata before running dependent analytics
-   make derived structure maintenance explicit in migrations and operational checks

## Real Limitations And Tradeoffs

-   it is descriptive metadata, not a guarantee that every procedure is cheap or currently useful on your dataset
-   catalog procedures describe or maintain registered structures; they do not validate that the underlying model is analytically appropriate
-   dropping or refreshing derived structures can affect dependent workflows and should be treated as an operational action