Methodology
The Bottleneck Map method.
Sovereign technology does not fail because actors are absent. It fails because founders, capital, buyers, and regulators cannot see each other's constraints in time. The Bottleneck Map tracks where these failures concentrate -- and the method is designed to be transparent, independent, and operator-useful.
Atomic answer
The Bottleneck Map is an analytical product, not a database. Each bottleneck is a pattern Stack & State has observed where two or more actors in the sovereign technology ecosystem cannot see each other's constraints in time to act. Bottlenecks are classified by signal strength (how visible and urgent the pattern is) and source confidence (whether the assessment draws on primary institutional sources, mixed evidence, or Stack & State ecosystem analysis). The map is updated as new signals emerge and is independent of any VC, prime, or government agency.
Source Confidence
How we classify the evidence behind each bottleneck.
Every bottleneck carries one of three source-confidence classifications. This is the primary signal about how much a reader should weight any single assessment.
Primary
Verifiable institutional source.
The claim draws on a named, publicly verifiable institutional source: government database (USASpending.gov, SAM.gov, FPDS), official report (GAO, IEA, USGS, CRS), regulatory filing (Federal Register, BIS rulemaking), or public company filing (10-K, 8-K, annual report). A visible public source note must appear on the page. If no source note is visible, the classification should be treated as mixed or analytical until reviewed.
Mixed
Public data plus analytical interpretation.
The claim combines public data with analytical interpretation of market conditions. The underlying public source is cited, but the classification direction, severity, or urgency reflects Stack & State editorial judgment. Treat as source-reviewed directionally, not as a quantified finding.
Analytical
Ecosystem observation and pattern recognition.
The claim reflects Stack & State ecosystem observation and pattern recognition. Analytical classifications represent our best assessment, not verified fact. They are hypotheses for navigation -- not verified factual findings -- and should not be used as legal, investment, procurement, or compliance advice.
Primary confidence requires a visible public source note on the relevant page. If a bottleneck is classified as primary but the source note is absent, that is a production error. Send a correction: /connect/
Signal Strength
How we assess the urgency and visibility of a bottleneck.
Source confidence tells you how well supported a claim is. Signal strength tells you how much it matters right now. These two dimensions are independent: a bottleneck can be highly visible (high signal strength) but supported only by analytical observation (analytical confidence), or well-sourced (primary confidence) but only emerging (medium signal strength).
High
Active constraint visible across multiple ecosystem signals.
Multiple sources -- program offices, founders, capital allocators, procurement data -- are reporting the same friction point. The bottleneck is reshaping behavior (product roadmaps, investment decisions, procurement timelines) and the cost of ignoring it is rising. High-signal bottlenecks should shape near-term decisions.
Medium
Pattern is visible but not yet driving decisions cross-ecosystem.
The bottleneck is observed in specific segments but has not yet generalized across layers. It may be emerging, localized, or dependent on a policy or market event that has not yet occurred. Medium signals are worth tracking; they may become high signals in the next 1--2 quarters.
Watch
Early indicator. Ecosystem evidence is insufficient to elevate.
The pattern has been noted from one or two sources but the signal is not yet strong enough to shape operator decisions. Watch signals are hypotheses that will either be validated or retired as more evidence accumulates.
Layer framework
How bottlenecks are scored across the 10 layers.
Each bottleneck is assigned to one of ten layers. A bottleneck can only appear in one layer -- the one where the primary constraint operates. A founder facing an export-control constraint may also have a capital constraint, but if the root cause is classification uncertainty (Layer 5: Export Controls & Compliance), that is where the bottleneck is mapped.
Layer 1
Materials & Processing
Rare earths, battery minerals, advanced alloys, graphite, uranium fuel, processing, separation, refining.
Layer 2
Energy & Power
Nuclear/SMR, grid infrastructure, power for AI data centers, transmission, licensing.
Layer 3
Compute & AI Infrastructure
Sovereign cloud, AI chips, model weights, data centers, FedRAMP/IL5 compliance.
Layer 4
Autonomy & Robotics
Drone platforms, autonomous systems, sensor fusion, edge inference, export-license clarity.
Layer 5
Export Controls & Compliance
ITAR, EAR, CFIUS, entity list, BIS rulemaking, compliance-as-code tools.
Layer 6
Non-Dilutive Capital
SBIR, STTR, DIU OTA, DARPA, DPA Title III, OSC, DOE LPO, ARPA-E, transition planning.
Layer 7
Government Buyers
Procurement authority, requirements definition, OTAs, program-of-record paths, technical evaluation capacity.
Layer 8
Strategic Capital & CVCs
Corporate venture, strategic investment, JDA structures, offtake-linked capital, technical co-evaluation.
Layer 9
Sovereign & Allied Capital
Sovereign wealth funds, development finance, allied industrial policy, NATO/EDF, technical due diligence.
Layer 10
Founders & Industrial Operators
Product, technology, team, procurement access, regulatory translation, strategic buyers, non-dilutive capital.
A bottleneck that spans multiple layers -- e.g., a founder who cannot access non-dilutive capital because a program office cannot evaluate their technology -- is assigned to the layer where the primary failure originates. If the root cause is a government buyer evaluation gap, it goes in Layer 7. If the root cause is a capital program design flaw, it goes in Layer 6.
Update cadence
When and how the map changes.
The Bottleneck Map is updated as new signals emerge, not on a fixed calendar. Bottlenecks can be added, reclassified, strengthened, weakened, or removed.
Triggers for change
What moves a bottleneck.
A new public-source signal (program award, regulatory change, capital commitment, permitting decision). A credible operator signal from a founder, buyer, or capital allocator that changes the visibility or urgency of a constraint. A correction to an existing classification. A bottleneck that is observed to be resolving (offtake commitments materialize, licensing pathways open, technical evaluation capacity is built).
"What would change this assessment"
Each bottleneck carries a change condition.
Every bottleneck on the map includes a line: "What would change this assessment." This is the specific, observable event that would move the bottleneck's signal strength or source confidence. For a capital bottleneck, it might be a visible long-term purchase agreement. For a regulatory bottleneck, it might be clearer agency guidance. This condition makes the map falsifiable -- and therefore useful.
Last reviewed date
Every bottleneck carries a review date.
Each bottleneck on the map shows the date it was last editorially reviewed. This is not the date the bottleneck was first identified -- it is the date the assessment was last confirmed against current signals. Bottlenecks that have not been reviewed in 90+ days carry a notice to that effect.
Corrections
Public and visible.
If a bottleneck classification is found to be incorrect -- whether based on new evidence or an error in the original assessment -- it is corrected on the map and the change is noted on the relevant page. Send corrections: /connect/.
Editorial independence
An independent map, not a VC house organ.
The Bottleneck Map is an editorial and analytical product of Stack & State, published by Juncture Labs. It is not sponsored, funded, or directed by any venture capital firm, defense prime, government agency, or corporate entity. The map does not exist to generate deal flow for a specific fund, to promote portfolio companies, or to advance any institutional agenda.
No paid placement
Companies, sponsors, members, and investors cannot buy placement on the map, influence bottleneck classification, or pay for favorable signal-strength ratings.
No portfolio bias
Stack & State has no investment portfolio. The map does not exist to surface deal flow for a parent fund or strategic partner. If a company appears on the map, it is because they solve a bottleneck, not because anyone paid or invested.
Not a government mouthpiece
Stack & State is not affiliated with any government agency, program office, or procurement organization. The map tracks government programs as actors in the ecosystem -- not as endorsers of the map.
Separated from membership
Membership and introduction access are separate from editorial selection and bottleneck classification. Joining the membership layer does not change how a company, program, or constraint is classified. The editorial firewall is structural, not a promise.
Stack & State is the publication arm of Juncture Labs. Juncture Labs is a venture studio at the intersection of frontier technology and sovereign capability. The studio may build, invest in, or advise companies operating in the sovereign technology ecosystem. When a company with a Juncture Labs relationship appears on the map or in the briefing, that relationship is disclosed. The editorial firewall is maintained by: (1) separate decision-makers for editorial classification and studio investment activity, (2) mandatory disclosure when a relationship exists, and (3) the "what would change this assessment" condition, which makes every classification falsifiable by anyone with better information.
Limitations
What the map is not.
Not a database
The Bottleneck Map is an analytical product. It does not attempt to catalog every constraint in the sovereign technology ecosystem -- it identifies the patterns that are most visible, most consequential, and most actionable for bilingual architects.
Not investment advice
Signal strength and source-confidence classifications are analytical assessments, not investment recommendations. High signal strength does not mean "invest here." It means "this constraint is visible and urgent."
Not legal or compliance advice
Classifications that reference regulatory frameworks (ITAR, EAR, CFIUS, FedRAMP) are analytical observations about ecosystem constraints, not legal interpretations. Consult qualified counsel for compliance decisions.
Not procurement advice
Program references (SBIR, DIU, DPA Title III, OSC, DOE LPO) are ecosystem-level descriptions, not eligibility determinations or application guidance. Program details change. Verify with primary sources.