Discovery Queries And Exports

Railiance Fabric includes a first CLI surface for inspecting local declaration graphs and projecting them into the current financial Fabric baseline.

All commands accept a repo root, fabric/ directory, or declaration files. When paths are omitted, commands read ./fabric.

Providers

List providers for a capability type or capability id:

railiance-fabric providers runtime-secrets
railiance-fabric providers railiance-platform.openbao.runtime-secrets

Output columns:

provider_id    service_id    lifecycle    environments    interfaces

Consumers

List consumers of a capability type/id or interface type/id:

railiance-fabric consumers runtime-secrets
railiance-fabric consumers railiance-platform.openbao.kv-v2

Output columns:

consumer_service_id    dependency_id    requires    provider_capability_id    provider_interface_id    status

Dependency Path

Show dependency paths for a service:

railiance-fabric dependency-path flex-auth.api

This walks declared dependencies and binding assertions recursively through provider services.

Unresolved Dependencies

Show dependencies with no matching provider or a missing/disputed binding:

railiance-fabric unresolved

Blast Radius

Show consumers affected by an interface type or interface id:

railiance-fabric blast-radius openbao-kv-v2-mount
railiance-fabric blast-radius railiance-platform.openbao.kv-v2

Exports

Export the graph as JSON:

railiance-fabric export --format json

Export the graph as Mermaid:

railiance-fabric export --format mermaid

Export the graph as the manifest-compatible graph explorer payload:

railiance-fabric export --format graph-explorer

Export the graph as the financial Fabric baseline projection:

railiance-fabric export --format financial

The JSON export has two top-level arrays:

nodes: service, capability, interface, dependency, and binding nodes
edges: graph relationships such as provides, exposes, available_via, consumes, binds:<status>, and uses_interface

Canon-aligned exports also carry mapping metadata beside the existing Fabric terms: nodes include canon_category, canon_anchor, mapping_fit, and evidence_state; edges include canonical_type, display_only, mapping_fit, and evidence_state.

The graph explorer payload wraps those nodes and edges as Cytoscape-compatible elements with stable keys, layers, display state, visual facets, source references, and deep links. The registry service exposes the same projection at GET /exports/graph-explorer.

The financial export emits railiance.fabric/v1alpha2 / financial-fabric-v1. It combines the current legacy graph evidence with fabric/financial/railiance-netkingdom.yaml, assigning inherited ownership and fabric containment for the current single Railiance fabric. Use it as the reset contract and State Hub vNext handoff artifact.

3.0 KiB Raw Blame History