API Reference & Traversal Rules
The NovaFuse Capability Registry is exposed as a static, machine-readable JSON graph at:
https://novafuse.tech/registry.json
Any CI/CD pipeline, audit engine, or script can fetch this graph directly and traverse it locally using deterministic rules.
Core Traversal Operations
GET
/registry.json
Retrieves the complete Capability registry mapping containing all nodes, version states (NC-1/2/3), introduces list, and dependency edges.
GET
Upstream Closure (Dependencies)
Finds the complete set of parent dependencies required by a given node.
Trace path: Node ➔ depends_on ➔ transitive parents.
GET
Downstream Impact (Blast Radius)
Calculates the blast radius of changes: find all nodes affected if a specific node is mutated.
Trace path: Find all nodes where target node is in their dependency closure.
Example Programmatic Traversal Script (Python)
Use this script in your CI/CD pipeline to query the registry and output the impact radius before deploying system updates:
import urllib.request
import json
def get_impact_radius(node_id):
# Fetch registry graph
url = "https://novafuse.tech/registry.json"
with urllib.request.urlopen(url) as response:
registry = json.loads(response.read().decode())
impacted = set()
def traverse(current_id):
if current_id in impacted:
return
impacted.add(current_id)
# Traverse downstream
for candidate_id, meta in registry.items():
if current_id in meta.get("depends_on", []):
traverse(candidate_id)
traverse(node_id)
# Remove self from impact radius
impacted.discard(node_id)
return list(impacted)
# Example: Compute blast radius of changing the IDNA Reference Model
print("Impacted Nodes:", get_impact_radius("NF-RA-001"))
Interactive API Sandbox
Select an endpoint and input parameters to test the graph traversal logic dynamically:
Sandbox Response Stream
Hit "Send Sandbox Request" to execute...