A graph-aware control layer that traces inter-agent handoffs, applies deterministic trust boundaries, scores bounded propagation risks, and quarantines selected edges before reviewed high-impact actions.
Genesis score7.23/10
Make Contagraph real.0/500
500 more votes and Contagraph 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
1Named attack paper confirmed
0Graph-aware commercial peers found
0Detector-only irreversible actions
The case
Creator and media systems increasingly chain research, drafting, editing, rights, publishing, and audience agents. One poisoned instruction, unsupported claim, or malformed state can propagate through several steps. Contagraph records the graph and enforces source, schema, permission, provenance, and action boundaries before using behavioral detectors as an additional signal. It never diagnoses an agent as hallucinating, assumes correlation means contagion, guarantees quarantine before harm, or lets one probabilistic score stop irreversible work without defined policy and human review.
Who pays — and why
AI platform, security, reliability, trust and safety, and media-operations teams running multi-agent content or creator pipelines with public or commercial actions.
What it unlocks
A runtime graph of tenant, agent identity and version, role, node, edge, message, source, schema, trust zone, permission, memory, tool, action, destination, and owner
Deterministic ingress, egress, schema, provenance, instruction, permission, data-class, destination, and action gates that operate before behavioral scoring
Bounded detectors with version, training and validation scope, evidence features, confidence, false-result history, drift, competing explanations, and unsupported states
Policy-driven allow, sanitize, hold, reroute, shadow, throttle, quarantine, require approval, kill-signal, recovery, correction, and incident evidence with provider readback
How Genesis scored it
7.23across seven criteria
8
Temporal window
Growing 2026 research and early commercial circuit breakers create a current window.
8
Buyer persona
Teams running multi-agent pipelines with public actions are concrete.
5
Convergence
The concept has several direct connections but no inbound bank support.
Why it scored well
A named academic attack class, growing research, live circuit-breaker products, and no reviewed graph-aware commercial peer establish a serious technical wedge.
What's holding it back
Detection validity is unproven, labeled propagation data are scarce, false positives can halt production, integration is ULTRA, and incumbents can expand.
Signals detected4 sources crossed
Signalacademic research carried in Genesis
Signalcompetitor research carried in Genesis
Signalmarket research carried in Genesis
SignalGenesis competitive search
Direction briefcontagraph.md
contagraph.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.
