Discovery Queries And Exports

Railiance Fabric includes a first CLI surface for inspecting local declaration graphs.

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

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

Show dependency paths for a service:

railiance-fabric dependency-path flex-auth.api

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

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

railiance-fabric unresolved

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

Export the graph as JSON:

railiance-fabric export --format json

Export the graph as Mermaid:

railiance-fabric export --format mermaid

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