quicue

Selected Node

Name -

Depth -

Dependents -

Types

quicue Analysis

Selected Edge

From -

To -

Relation depends_on

JSON-LD IRI

-

Node Colors (Criticality)

0 dependents max dependents

More critical resources (more dependents) appear redder. Enable Impact mode to see what fails if a resource goes down.

Controls

Click node/edge to select

Drag to pan

Scroll to zoom

Double-click to fit

/ search nodes

Esc close modals

API Explorer

Interactive query patterns for the infrastructure graph. Select parameters and click Run to see live results.

QUERY #ImpactQuery

Find all resources affected if target fails (blast radius analysis).

CUE: impact: #ImpactQuery & {Graph: infra, Target: "-"}

Target Node

QUERY #DependencyChain

Get the dependency path from target up to root(s).

CUE: chain: #DependencyChain & {Graph: infra, Target: "-"}

Target Node

QUERY #PathFinder

Find shortest path between any two nodes in the graph.

CUE: path: #PathFinder & {Graph: infra, From: "-", To: "-"}

From Node

To Node

QUERY #ImmediateDependents

Direct dependents only (not transitive). Nodes that directly depend on target.

CUE: deps: #ImmediateDependents & {Graph: infra, Target: "-"}

Target Node

GET #CriticalityRank

Rank resources by dependent count (most critical first).

CUE: crit: #CriticalityRank & {Graph: infra}

GET #GroupByType

Group resources by their @type array.

CUE: byType: #GroupByType & {Graph: infra}

GET #InfraGraph.topology

Layer ordering by dependency depth. Layer 0 = roots.

CUE: infra.topology

GET #ValidateGraph

Check for missing deps, self-refs, cycles, empty types.

CUE: validate: #ValidateGraph & {Input: resources}

DIFF Graph Diff

Compare current graph with a previous state. Paste previous JSON or export output.

EXPORT Graph Formats

Export current graph to various formats for external tools.

CUE Unification: Interface → Provider → Instance

Toggle layers to see how abstract constraints become concrete commands. Switch providers to see same resource, different commands.

Provider

Action

dns-server.actions.console

CUE Expression

Evaluates To

Interface

Schema: what fields must exist

Provider

Template with UPPERCASE params

Instance

Binds concrete values to params

./quicue eval 3-layer

Dependency Layers (Timeline)

Resources organized by depth. Layer 0 = roots (no dependencies). Startup order: top to bottom. Shutdown order: bottom to top.

Startup Sequence

Resources at each layer can start in parallel once all resources in the previous layer are ready.

Click a node to see its impact in the graph view.

Resources by Type

Resources grouped by their @type array. Resources can have multiple types.

Type Categories

Semantic (DNSServer, Database)

Implementation (LXCContainer, VM)

Classification (CriticalInfra)

Graph Analysis

Live analysis of the current graph. Click items to highlight in graph view.

Bottlenecks (Fan-In) -

Resources with 3+ dependents are critical bottlenecks.

Single Points of Failure -

Resources with dependents but no redundant peer of same type at same layer.

Coupling Points -

Resources where 30%+ of the graph depends on them (shared dependencies).

Path Finder A to B

Find dependency path between two resources:

What-If Simulation healthy

Select resources to simulate as DOWN (Ctrl+click for multiple):

Cascade Simulation select node

Select a resource to simulate failure cascade:

Validation -

Change History

Track infrastructure changes over time. Load git history or view embedded changes.

Timeline

No history data available. Click "Load Git History" to import commit data.

Import

Import infrastructure definitions from external sources.

tf Terraform State Drop .tfstate or click

pu Pulumi Stack Drop stack.json or click

Load JSON from URL (CORS must be enabled)

About This View

Sankey diagram shows dependency flow from roots to leaves. Width indicates number of downstream dependents.

Statistics

Nodes -

Edges -

Max Depth -

Add Resource (Simulation)

Load JSON-LD