Omen (Chinese: 爻) is an open-source strategic reasoning engine powered by Explainable AI (XAI). It combines ontological modeling of strategic phenomena with counterfactual analysis of uncertainty, delivering verifiable, traceable, and explainable insights for decision-makers.
Concepts | Quick Start | Case Templates | Roadmap
🪄 Capabilities
Analyze, Simulate, Explain.
Omen does not predict the future. It is a reasoning engine built for complexity. By mapping causal chains and logical dependencies, it generates replayable, comparable branching paths, revealing weak signals, critical points, and evolving ecosystems, and helping decision-makers gain clarity in complexity:
- 🔄 Substitution Logic: Which technology will replace another under what critical conditions?
- 🛡️ Capability Evolution: Which core capabilities will be enhanced first, and which will coexist long-term?
- 🏆 Strategy Wins: Which strategy combinations are more likely to win the market, capital, and developer ecosystem?
- ⏳ Time Windows: When is the optimal timing for in-house development, alliances, M&A, or contraction?
Through explainable reasoning chains, Omen reveals how technological evolution reshapes markets, helping strategic decisions decode the omens from the chaos.
✨ Core Features
| Feature Module | Description |
|---|---|
| 🧬 Technology Capability Modeling | Deconstructs complex tech stacks into quantifiable, comparable capability dimensions (e.g., latency, throughput, ease of use, ecosystem richness). |
| 🤖 Strategic Agent Simulation | Defines different types of market participants (startups, giants, open-source communities, regulators), endowing them with goals, resources, and constraints. |
| 📈 Market Evolution Reasoning | Simulates dynamic changes in adoption rates, market share, cost structures, cash flow, and ecosystems. |
| ⚡ Critical Point Identification | Automatically discovers key thresholds for "when substitution occurs" and "why it happens at this moment." |
| 🔮 Counterfactual Analysis | Answers "What would have happened if event X had not occurred, or if strategy Y had been adopted?" |
| 📖 Result Explanation Engine | Outputs key turning points, causal chain deductions, and strategic implications, rejecting black-box conclusions. |
📊 Typical Outputs
A complete reasoning session typically answers the following questions:
- Substitution? Will the new technology completely replace the old one, or form a complement?
- Time Window? When is the specific time window for substitution or turning points?
- Key Drivers? Which variables (e.g., cost reduction speed, API compatibility) are the decisive factors?
- Winners and Losers? Which entities suffer first, and which benefit unexpectedly?
- Strategy Effectiveness? Under what circumstances is an "open ecosystem" superior to "vertical integration"?
- Endgame Form? Does it move towards monopoly, oligarchic balance, or fragmented coexistence?
🚀 Quick Start
🏗️ Installation
Environment requirements: Python 3.12+ with pip package manager.
git clone https://github.com/StrategyLogic/omen.git
cd omen
pip install --upgrade pip setuptools wheel
pip install -e .
🌰 View Example
If you want to quickly see Omen in action, a visualized sample case and its results are available in the sample directory. Run:
streamlit run sample/app/scenario_planning.py
Then open http://localhost:8501 in your browser to explore the full strategic reasoning flow.
🎵 Run Built-in Case
If you want to run a complete end-to-end workflow, we have prepared a built-in case simulating SAP's acquisition of Reltio in March 2026. The case document is cases/sap_reltio_acquisition.md, and it can be run end-to-end with the following commands:
Step 1. Analyze
Omen's Analyze module combines strategy methodology and the data pipeline, allowing you to generate strategic insights and machine input artifacts from the source document with a single command.
Situation Analysis
# analyze the built-in case and pack it as "sap" alias
omen analyze situation --doc sap_reltio_acquisition --pack-id sap
This step generates the Situation Artifact and creates a package named sap for consistent use in subsequent steps.
Scenario Planning
Omen v0.1.9 provides deterministic A/B/C scenario planning capabilities.
- Scenario A: Offensive branch
- Scenario B: Defensive branch
- Scenario C: Confrontational branch
You can directly use the sap alias to locate the generated situation artifact from the previous step:
omen scenario --situation sap
This step generates the scenario pack artifact under data/scenarios/sap/ for simulation.
Step 2. Simulate
Omen's simulation engine can reason across different scenarios. Use the scenario pack generated in the previous step to run simulation:
omen simulate --scenario data/scenarios/sap/scenario_pack.json
This step generates reasoning traces and writes the deterministic result to output/sap/result.json.
Step 3. Explain
Omen's explanation module interprets simulation outcomes and traces back key decision points and risk items (known unknowns) from the situation artifact to generate decision-ready insights and recommendations:
omen explain --pack-id sap
This step generates a structured explanation artifact at output/sap/explanation.json.
Launch UI
Omen also provides a Streamlit-based UI application for visualizing the full strategic reasoning flow.
streamlit run app/scenario_planning.py
End-to-End Flow
More details
You can click on each panel on the page to inspect the full chain of outputs from source document to situation artifact, scenario artifact, simulation result, and explanation artifact.
👥 Target Audience
Omen is built for the following roles:
- Technology Strategy Teams
- Product & Platform Leads
- AI Infrastructure Researchers
- Open Source Ecosystem Observers
- Investors & Industry Analysts
🎬 Showcase
Strategic Actor Analyze
Strategic Reasoning Cases
- 🧩 Acquisition: SAP vs Reltio
- 🗺️ Ontology Games: Database vs AI Memory
- ⚔️ Vector Database vs AI Memory
More scenarios are under development (contributions welcome):
Agent InfrastructurevsWorkflow PlatformsVertical AIvsGeneral AI StackOpen Source ModelsvsClosed Commercial APIsData GovernancevsAI-Native Knowledge Systems
📃 License
Omen is under AGPL-3.0-or-later, the project is developed and maintained by StrategyLogic®.
Note: If you wish to use Omen in a closed-source environment or provide it as a SaaS service without open-sourcing your code, please contact us for a commercial license.
🌟 Vision
Omen aims to become an open strategic reasoning workstation:
It does not output a single answer, but helps people systematically understand how the future branches; and understand which conditions shape the outcome; and understand which actions can change the path.
If you are interested in technological evolution, market substitution, strategic modeling, or multi-agent reasoning, you are welcome to join us in interpreting the omens of this chaotic world together.
Simulate the Signs. Reveal the Chaos.
Metadata
Release files for omenai 0.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| omenai-0.1.9.tar.gz | 133.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omenai-0.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 297.1 kB
Release files / omenai-0.1.9.tar.gz
| Download URL | omenai-0.1.9.tar.gz |
|---|---|
| Size | 133.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f0aeb965bee845521174b933a746c76f6f74ec2881863275386c8fcc3fb7778
|
|
BLAKE2b-256 checksum How to use checksums |
93aa83bae76d7af31132ec01f6c43a47d4bde5ee4a9c8b0341c1184356c50e89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.
Transparency logRelease files / omenai-0.1.9-py3-none-any.whl
| Download URL | omenai-0.1.9-py3-none-any.whl |
|---|---|
| Size | 164.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55a5ce5ebb34179404f8811ac3f421d43f058bfe2b2252472a69304c8455605b
|
|
BLAKE2b-256 checksum How to use checksums |
47aa4bb2a8b3539cbe348d55d45134810554e9efd919b4d3bf308f6c9175a8f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 12, 2026.
Transparency log