Typed nodes and edges
Station indexes expose cycle and line membership, stakeholder involvement, attached resources, and next-station edges. Reverse indexes make stakeholder, resource, cycle, line, and goal lookups direct.
Graph architecture
The method, as a queryable graph
APIOps Cycles compiles its catalog into typed adjacency indexes. Cycles, lines, stations, stakeholders, goals, and resources retain stable identities while their relationships become directly traversable.
Open method-graph.jsonFor implementers
Deterministic context, built ahead of time
The build step validates references, deduplicates edges, and emits a static graph. The browser can resolve context and rank routes without a database, opaque recommendation service, or network round trip.
Validated compilation
The generator rejects dangling station, cycle, line, stakeholder, and resource references. Stable sorting makes generated output reviewable, cacheable, and suitable for version control.
Order has semantics
Cycle station order remains canonical journey order. Goal paths are derived from the intersection of recommended cycles and lines, preserving that order as the final resolution tie-breaker.
Explainable ranking
A station is strongly emphasized when it matches both role and goal, moderately emphasized when it matches either, and otherwise left unchanged. Recommended next stations use the same explicit score.
Route-aware identity
The same station may occur in several cycles. An explicit cycle in the URL is promoted only when the graph confirms membership, so shared content keeps its journey context.
Portable artifact
The versioned method-graph.json output is published with the open data, allowing search, visualization, agents, and other clients to share the site's relationship model.
Put it to work
Inspect the graph as data
Download the generated graph, compare its indexes, and build a traversal that fits your own toolchain.
Open method-graph.json