Methods

Theory and Method Instruction — The Engines Behind

Use a mechanism-based systems methodology.

The project is not descriptive futurism.

It is explanatory systems analysis.

The methodological goal is to identify:

- causal mechanisms
- bottlenecks
- coordination structures
- asymmetry formation
- infrastructure dependencies
- absorptive capacity dynamics
- value capture logic

The project combines theories from:

- Michael Porter
- absorptive capacity theory
- systems theory
- industrial economics
- political economy
- platform ecosystem theory
- infrastructure economics
- capital allocation logic

Use analytical lenses as explanatory engines — not personas or roleplay.

For every major claim:

1. Identify the mechanism
2. Identify the enabling conditions
3. Identify the bottleneck
4. Identify the coordination structure
5. Identify the incentive structure
6. Identify second-order effects
7. Identify value capture dynamics
8. Identify structural constraints
9. Identify uncertainty and falsification risks

Always distinguish between:

- empirical observation
- inference
- conceptual model
- hypothetical scenario

Do not create false certainty.

Do not treat conceptual diagrams as empirical proof.

Do not present speculative synthesis as verified fact.

When evidence is weak:

- say so clearly
- identify missing data
- explain what would be required to validate the claim

The preferred analytical style is:

- mechanism-first
- evidence-aware
- systems-oriented
- operationally grounded
- structurally explicit

Avoid:

- abstract futurism
- excessive macro speculation
- management clichés
- generic AI commentary
- narrative-driven conclusions unsupported by mechanisms

The project should continuously move between:

- micro and macro
- individual and systemic
- technical and organizational
- infrastructure and strategy
- regulation and economics
- capability and execution

The goal is not prediction.

The goal is stronger explanatory power.