01 / Map the landscape
Identify technologies, players, IP activity and areas where innovation is concentrated.
Strategy RootLens
Explore directions. Read the evidence. Decide your next move.
Protect your saved workspace
Initialization stopped. Do not reset or clear browser storage. Download a raw copy before investigating the error.
This copies only this browser origin's Strategy storage, including malformed text. No upload or automatic repair. It may contain confidential notes: keep it private. This file is not accepted by the normal workspace importer; use a known-good workspace backup for normal restoration.
Where should we focus strategically?
Track innovation, investment, maturity and industrialisation across technology domains. Turn the evidence into priorities for research, partnerships and technology development. No product-specific fit assessment is required.
02 / Read the trajectory
Separate active investment, demonstrated maturity and announced commercial milestones.
03 / Set strategic direction
Choose where to monitor, investigate, collaborate or develop. Record a planning horizon and the signals that would change direction.
Technology domains
This app supports technology strategy; it does not confirm a root cause or approve a technology. Its evidence loop supports technology strategy and research priorities. No synthetic company scores, automated maturity or invented priorities are included.
01 / YOUR OBJECTIVE
What do you want to achieve?
Hypothesis templates with maintained domain evidence. AI synthesis and live research are not connected.
02 / EXPLORE YOUR DIRECTIONS
Three routes to examine
Unverified hypothesis templates with maintained domain context, not AI synthesis or live research. Support or counterevidence requires an explicit interpretation.
Edits stay in this browser and are included in the workspace backup. Valid edits are also saved when switching direction or leaving Strategy.
Enterprise technology portfolio
Review technology directions across domains, business functions and strategic themes. Empty domains show research gaps, not invented knowledge.
Knowledge coverage by domain
Classification and decisions remain local to this browser; this is not a shared enterprise database. Use public or non-confidential examples here.
Technology landscape
Optional technical benchmarking
Technical evidence can inform strategy without requiring a product-specific fit assessment. Compare alternatives within the same engineering function. Scores are analyst screening assessments; the roadmap does not infer priorities from them.
Scores: 1 = least favourable, 5 = most favourable. Blank = unknown. A total is shown only when all weighted criteria are assessed. Weights and ratings are editable and saved in this browser. Backup workspace includes comparison weights; older backups without weights retain this browser's settings. Keep workspace backups private. Comparison CSV is not a restorable workspace backup.
Evidence into decisions
Review one technology family and strategic scope at a time. The matrix uses analyst ratings; the timeline uses dated source events.
01 / Technology decision matrix
Development commitment × relevance to the stated strategic objective.
Assessment scale
Commitment: 1 = isolated exploration; 2 = active research; 3 = sustained prototype/testing effort; 4 = pilot or integration activity; 5 = production activity supported by dated evidence. This is an analyst judgement of development effort, not a technical readiness rating.
Strategic relevance: 1 = peripheral; 2 = limited fit; 3 = plausible candidate; 4 = addresses a major priority; 5 = central to the stated strategic objective. Record the market, technology domain or differentiation goal in the scope and rationale. Existing assessments retain their original scope; technical-context ratings are not automatically converted into strategic ratings.
The split at 3 is a screening convention. Missing data remain unplotted. Equal coordinates share one marker; the numbered table identifies every technology.
02 / Bubble benchmarking
Benefit, integration, technical maturity and confidence remain separate.
Edit these 1–5 ratings in “Compare & prioritise”. Circle area represents the rating. A question mark means unknown.
03 / Evidence timeline & next gates
Documented events, their validation scale and the next evidence to obtain.
Publication dates do not establish readiness. Undated sources remain in the table. Future actions carry no assumed completion date or projected maturity.
Explore maintained evidence
Find reported results, limitations and the next verification before opening an editor. This is the maintained register, not live research or AI analysis.
Every search word must occur in a reading or its linked documents. Filters do not establish absence of counterevidence. All references of a visible reading stay available, even if they do not match the filters.
Editorial readings
Verification queue
Turn documented gaps into a research worklist. Filters do not assign maturity or priority: they expose the evidence still needed before changing strategic direction.
Publication or revision dates are shown exactly as recorded. “Not stated” remains unknown; it is not converted into a score or maturity level.
A transparent working method
01 / Source record
Direct URL, actual review date, next verification and publication date when stated. Document revision marks and listing dates are distinguished. An undated source remains undated.
02 / Evidence quality
Evidence briefings distinguish cooling, propagation, early-warning and off-gassing experiments from model-level evidence; review depth, validation scale and missing methods are explicit; a patent entry records a published disclosure. No vehicle qualification or exhaustive patent search is claimed.
03 / Decision discipline
Separate documented evidence, supplier claims, inference, missing data and next validation action. Matrix axes require a context, rationale and date; commitment, maturity and confidence remain distinct. Unknown is never scored as average.
04 / Nexus deployment
Source includes a Node server and Dockerfile. This prototype stores edits locally in the browser. Shared storage, SSO and automatic online research require approved Nexus integration.
Technology strategy roadmap
Planning horizons are your strategic choices, not predicted technology readiness. Missing horizons remain unscheduled.
From your selected hypothesis
Actions below follow the current filters, not this hypothesis objective. Other filters were cleared on entry; the current scope is shown below. No action, date or evidence stance has been assigned.
The dossier follows these filters, keeps incomplete decisions visible and includes full linked source details. Context sources do not automatically support a decision.