Connectivity
Finds weakly and strongly connected regions.
01 / INPUT SURFACE
Declare the system graph
Analysis profile
Modules
The components, agents, stores, or control surfaces in the design.
Gateway
Planner
Tool runner
Memory
Reviewer
Connections
Declare what sends, controls, reads, checks, or returns information to what.
01
02
03
04
05
Declared graph only. Results are review signals, never approval.
02 / XR MACHINE VIEW
Structural evidence
controlexecutionstatesignalgovernance
// Ready for declared graph
Start with an example or map your own system. The engine runs the six structural analysis families already developed in SAVE Core, then returns the measurements without claiming that one score proves a good architecture.
01Strong connectivity
02Module removal
03Structural redundancy
04Cycle classification
05Centrality metrics
06Edge-type analysis
Your graph stays in this browser. It is not uploaded.ENGINE 0.1.0-PILOT · DECLARED-TOPOLOGY-V1
METHOD / WHAT THE ENGINE KNOWS
Structure is evidence.
It is not truth.
RunSAVE analyses the logical communication topology you submit. It does not observe your code, infrastructure, users, data, runtime failures, cost, security, or throughput.
Module removal
Measures added fragmentation when each module is removed.
Redundancy
Finds connections backed by another directed route.
Cycles
Reports cyclic regions and the relationship types declared inside them.
Centrality
Measures where shortest directed paths concentrate.
Edge types
Counts only the relationship types you declared.
FIRST-PARTY EVIDENCE / XEO LITE
INTERNAL CASE · JUNE 2026
SAVE found an orphaned revenue module in a real product graph.
During XEO Lite architecture work, SAVE exposed a module that existed in the design but was absent from the declared relationship map. Adding two missing relationships moved the old heuristic score from 37 to 70 and made the omission visible to the team.
The same review showed that some redundancy and centrality warnings were misleading for a single-file browser app. This pilot therefore publishes the measurements and caveats instead of one overall architecture grade.
AGENT SURFACE
Usable by agents in the browser today
In browsers that support WebMCP, RunSAVE exposes this same local analysis asanalyse_declared_topology. It updates the visible workspace and returns the same evidence receipt without uploading the graph.
This browser has not exposed WebMCP
SAVE ENDPOINT
KEY-PROTECTED BETACall SAVE from your server-side agent.
Send a public or synthetic graph to the standalone API and receive the same structural report. A beta key is required. API graphs are processed on the server; the checker above still runs entirely in your browser.
POST runsave.dev/api/v1/analyse
input runsave.declared-graph.v1
output runsave.declared-topology-report.v1API documentation and beta access →ADJACENT TO AGENT NEXUS
Inspect the system here. Check its service declaration there.
RunSAVE tests topology. The Agent NEXUS Provider Lab tests whether a service manifest matches a buyer’s hard requirements. They stay separate, with a link-only handoff and no application-level graph or report payload transfer.