Dependency Atlas
See where Israel relies on external suppliers, which systems are most exposed, and where resilience investment may matter.
Start with the question you need to answer. Each app makes its inputs, assumptions, and next research step visible.
Pick a starting point below. You can move between tools as your research question becomes more specific.
Map a strategic dependency, test how it behaves under pressure, and inspect the assumptions behind the result.
See where Israel relies on external suppliers, which systems are most exposed, and where resilience investment may matter.
Apply a disruption and severity level to see the resulting system pressure, response themes, and research priorities.
Change the published scoring weights and see which capital priorities move when your assumptions change.
Move from a strategic question to relevant companies, public-market context, coverage gaps, and side-by-side evidence.
Search source-verified company profiles by sector, strategic theme, entity type, and research signal.
See which strategic priorities have identifiable company matches and where the research still shows a coverage gap.
Compare constituent weights, sector concentration, strategic themes, and overlap across Israeli market indices.
Compare two to four database entries across entity type, exposure, evidence, status, and source freshness.
Turn the evidence you found into a focused question set or a shareable mission-level research brief.
Choose a sector, exposure, and entity type to assemble a cited question set for a first diligence call.
Combine a scenario, critical capabilities, company matches, evidence gaps, and diligence prompts in one brief.
These apps organize cited public research so that strategic dependencies, scoring assumptions, company matches, and missing evidence are easier to inspect. They do not predict returns, recommend investments, or replace technical, commercial, legal, tax, or regulatory diligence.
The Dependency Atlas is the source-of-truth surface for the strategic exposure model. It starts with cited public inputs and makes the dependency categories, source countries, capital priorities, scoring factors, and update date visible. The Scenario Simulator reuses those published inputs to explore what may happen under a defined disruption. It is a structured thought exercise, not a forecast of timing, probability, market performance, or government action.
The Assumption Sensitivity Explorer shows how the priority queue changes when a reader changes the model weights. A ranking move reflects the selected assumptions; it does not establish that one sector, company, or intervention is objectively superior. Readers should inspect both the baseline and the changed contributions before drawing a conclusion.
Company results come from the Claw & Talon database. Matches are based on visible sector fit, entity type, strategic tags, and published relevance signals. A match is a research lead, not an endorsement, customer claim, procurement assessment, or confirmation that a company can solve the full strategic need. The Capability Gap Tracker is intentionally conservative about this distinction: an identifiable match may narrow the search without proving that the capability is available at the necessary scale, maturity, security level, or price.
The public app layer does not estimate valuation, investment access, founder quality, customer references, technical performance, production capacity, procurement timing, export-control outcomes, or whether a company is currently raising capital. Those questions require current primary evidence and, in some cases, qualified professional advice. Source dates are shown so readers can see when an input may need to be refreshed.
Entity types also matter. A private startup, public company, acquired asset, fund, defense prime, government-owned company, and ecosystem reference cannot be compared as if they represent the same kind of opportunity. The Company Comparison Matrix keeps those differences visible and warns when unlike entity kinds appear together. Its output is a structured reading aid, not a normalized investment score.
The Diligence Question Builder draws from the canonical Learn checklists to help prepare a first conversation. The Mission Stack Builder combines those questions with scenario and capability research so gaps are easier to discuss. Neither tool verifies an answer or converts a public claim into diligence evidence. A useful brief should still end with source review, customer and technical verification, and a clear statement of what would confirm or weaken the thesis.
Begin with a specific question rather than a desired conclusion. Use the Atlas or Simulator to define the exposure, then inspect the source and assumption behind each important result. Continue into the database and comparison tools only after the relevant sector and capability are clear. Record missing evidence alongside positive signals, and distinguish what is directly sourced from what is inferred.
The apps are intentionally ad-disabled and stop before transaction advice. Their purpose is to make public research easier to audit and to produce better follow-up questions. When the evidence is incomplete, the correct output is a visible gap—not a confident recommendation.