A pre-apply infrastructure risk gate that joins declared change plans to versioned service maps, traces, ownership, criticality, recent observations, and reviewer-approved deployment policy.
Genesis score7.40/10
Make Blastgraph real.0/500
500 more votes and Blastgraph is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
2Open service-map validators
0Direct runtime gates found
Never assumedComplete dependency graphs
The case
Open service-map and observability projects validate runtime dependency discovery, while existing infrastructure-plan products focus on declared state. No commercial gate using observed runtime graphs was identified. Blastgraph's advantage is a customer-specific dependency history, but observed traffic is incomplete: dormant, scheduled, failover, administrative, storage, queue, DNS, identity, and data dependencies may not appear. The product should present evidence and uncertainty, require explicit policy, and never claim a graph is the complete blast radius.
Who pays — and why
The platform engineering, site reliability, infrastructure, or change-management team reviewing human- and agent-proposed production changes.
What it unlocks
A time-aware graph joining declared resources, observed calls, traces, identities, queues, data stores, owners, environments, criticality, incidents, and evidence freshness
A change-impact analysis that separates direct declarations, observed runtime edges, inferred candidates, missing coverage, stale evidence, and unknown dependencies
Policy-driven hold, review, canary, test, maintenance-window, rollback, and approval requirements with execution and reconciliation history
How Genesis scored it
7.40across seven criteria
8
Productive tension
Fast automated change review must preserve incomplete observation, human authority, safe rollout, and rollback.
8
Temporal window
Current open runtime maps and emerging change-risk tools validate timing.
5
Convergence
Several connected ideas support the direction but external convergence is moderate.
Why it scored well
Live service-map primitives, an undeclared-dependency problem, clear platform buyers, and no identified runtime gate support the concept.
What's holding it back
Runtime evidence is incomplete, integrations are deep, no structural incumbent barrier exists, and a false negative at the gate can be dangerous.
Signals detected5 sources crossed
SignalCilium Hubble research carried in Genesis
SignalPixie research carried in Genesis
Signalcompetitor comparison carried in Genesis
Signalmarket scan carried in Genesis
SignalGenesis moat limitation
Direction briefblastgraph.md
blastgraph.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.
