`nexyron.intervention_list`

Generic Description

nexyron.intervention_list lists the current catalog or artifact entries for this semantic family.

CALL nexyron.procedures()
YIELD name, description, parameters, output_columns
WHERE name = 'nexyron.intervention_list'
RETURN name, description, parameters, output_columns

Abstraction-platform registry procedures create, list, read, and inspect named contracts such as abstractions, features, datasets, snapshots, models, policies, interventions, scenarios, and split policies.

Consumer-Level Explanation

This page documents one abstraction platform procedure in the same one-page-per-surface style used by the stronger algorithm references.

Parameters

• This procedure takes no explicit parameters.

Output Columns

• Returned columns depend on the family, but the rows enumerate currently registered or materialized entries.

Example Contract Prerequisite

The executable Cypher blocks on this page query nexyron.procedures() so they work in an empty database and stay synchronized with the live procedure registry. A direct CALL nexyron.intervention_list(...) requires the named abstraction contracts, artifacts, features, snapshots, datasets, models, or policies referenced by that call to exist first; otherwise the runtime correctly fails with an unknown-contract error rather than inventing state.

Conceptual Explanation

This procedure stays inside the same Cypher, semantic-contract, and artifact runtime as the rest of Nexyron. That matters because catalog visibility, materialization state, freshness, and dependency shape are part of the same database contract rather than hidden external service state.

More Detailed Explanation

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 abstraction procedures, the executable examples on these pages intentionally inspect procedure metadata unless the required named artifacts are created in the same example.

Advanced Example

CALL nexyron.procedures()
YIELD name, parameters, output_columns
WHERE name = 'nexyron.intervention_list'
RETURN name,
       [p IN parameters | p.name] AS parameter_names,
       output_columns
ORDER BY name

Real Use Cases

• Register reusable member-retention contracts once, then let snapshots, datasets, models, and policies reference those names instead of duplicating raw Cypher in every workflow.
• Keep admin and product teams aligned around one shared abstraction contract for members, households, facilities, interventions, and churn labels during quarterly retraining cycles.

Real Limitations And Tradeoffs

• This procedure exposes or drives abstraction-platform runtime state. It does not replace the need for well-defined upstream features, snapshots, datasets, models, or policies.
• When artifacts are stale, the correctness question is usually upstream contract quality first, not only refresh mechanics.
• the procedure fails correctly when required contracts or artifacts do not exist; examples should not imply automatic state creation
• model, policy, and causal outputs are only as defensible as the registered data, temporal, and treatment contracts