witdem-analytics 0.2.0__tar.gz → 0.2.2__tar.gz

{witdem_analytics-0.2.0 → witdem_analytics-0.2.2}/.gitignore

@@ -25,3 +25,6 @@ web/tailwind.config.d.ts
 
 # Locally generated live-matrix reports
 examples/product-factory/reports/
+
+# Local screenshots and investigation output
+/artifacts/

witdem_analytics-0.2.2/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

{witdem_analytics-0.2.0 → witdem_analytics-0.2.2}/PKG-INFO

@@ -1,8 +1,15 @@
 Metadata-Version: 2.5
 Name: witdem-analytics
-Version: 0.2.0
+Version: 0.2.2
 Summary: Runtime analytics for agent applications using OpenTelemetry, with optional business semantics through the Witdem SDK.
-Requires-Python: >=3.10
+License-File: LICENSE
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: <3.14,>=3.10
+Requires-Dist: cryptography<51,>=50
 Requires-Dist: duckdb<2,>=1.2
 Requires-Dist: duckle==0.5.11
 Requires-Dist: fastapi<1,>=0.115
@@ -20,41 +27,92 @@ Description-Content-Type: text/markdown
 
 <div align="center">
 
+<img src="docs/assets/witdem-banner.png" alt="Witdem AI — Understand how your AI system actually behaves" width="100%">
+
 # Witdem
 
 **Analytics for AI agents and multi-step AI applications.**
 
 Tracing tells you what executed. Witdem connects those executions to application outcomes: which paths ran, what they cost, where they failed, and whether they achieved the product goal you defined.
 
-[Get started](docs/getting-started.md) · [YAML contracts](docs/contract-tutorial.md) · [Haystack](docs/integrations/haystack.md) · [Frameworks](#integration-status) · [Providers](docs/providers.md) · [Troubleshooting](docs/troubleshooting.md)
+[![Tests](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml/badge.svg)](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml)
+[![SDK on PyPI](https://img.shields.io/pypi/v/witdem-sdk?label=witdem-sdk)](https://pypi.org/project/witdem-sdk/)
+[![Analytics on PyPI](https://img.shields.io/pypi/v/witdem-analytics?label=witdem-analytics)](https://pypi.org/project/witdem-analytics/)
+[![npm](https://img.shields.io/npm/v/witdem/latest?label=npx%20witdem)](https://www.npmjs.com/package/witdem)
+[![Python](https://img.shields.io/badge/Python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13-blue)](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+[Get started](docs/getting-started.md) · [YAML contracts](docs/contract-tutorial.md) · [Frameworks](#integration-status) · [Providers](docs/providers.md) · [Contributing](CONTRIBUTING.md) · [Security](SECURITY.md)
 
 </div>
 
+## See Witdem in action
+
+From one-line setup and two-line instrumentation to a measured run, its
+execution graph, business outcome, cost, and contract evidence.
+
+<p align="center">
+  <a href="https://cdn.jsdelivr.net/gh/ebrahimisoheil/witdem-oss@37e335d/docs/assets/witdem-demo.mp4">
+    <img src="docs/assets/witdem-demo-poster.jpg" alt="Watch the Witdem installation and analysis walkthrough" width="100%">
+  </a>
+  <br>
+  <a href="https://cdn.jsdelivr.net/gh/ebrahimisoheil/witdem-oss@37e335d/docs/assets/witdem-demo.mp4"><strong>▶ Watch the 1:48 installation-to-analysis walkthrough</strong></a>
+</p>
+
 ## First run
 
-Start the local receiver, ELT worker, and dashboard:
+Choose one backend launcher. Applications use `witdem-sdk` with either path.
+
+Docker-managed (requires Docker Compose):
+
+```bash
+npx -y witdem@latest up
+```
+
+Native Python (requires Python and [pipx](https://pipx.pypa.io/)):
+
+```bash
+pipx install witdem-analytics
+witdem up
+```
+
+Both start the receiver, ELT worker, and dashboard, wait for health, open
+`http://localhost:8501`, and preserve data across `down` and upgrades. Their
+lifecycle vocabulary is the same:
 
 ```bash
-npx -y witdem@0.2.0 up
+npx -y witdem@latest status   # Docker path
+witdem status                     # pipx path
+npx -y witdem@latest logs receiver
+witdem down
 ```
 
-That pulls the version-matched container, starts all three services, waits for
-them to become healthy, and opens `http://localhost:8501`. Docker with Compose
-is the only prerequisite. Data persists across `down` and package upgrades.
+Check releases and compatibility without changing packages or data:
 
 ```bash
-npx -y witdem@0.2.0 status
-npx -y witdem@0.2.0 logs
-npx -y witdem@0.2.0 down
+npx -y witdem@latest update --check
+witdem update --check
 ```
 
-Add the SDK to an existing Haystack 3 project from the checkout:
+See the [upgrade guide](docs/upgrade.md) for exact NPX, pipx, and SDK commands.
+
+Add the SDK to an existing Haystack 3 project:
 
 ```bash
-python -m pip install -e "/path/to/Witdem-Analytics/witdem-sdk[haystack]"
+python -m pip install "witdem-sdk[haystack]"
 export WITDEM_ENDPOINT=http://localhost:4318
 ```
 
+From the application project, create the YAML contract and then edit it to
+describe that application's result:
+
+```bash
+witdem-sdk init --runtime haystack
+```
+
+This creates `.witdem/witdem.yaml`. It does not inspect or rewrite application
+code, and it will not replace an existing contract unless `--force` is used.
+
 Wrap the pipeline once. Its existing `run`, `run_async`, and `run_async_generator` calls stay unchanged:
 
 ```python
@@ -91,8 +149,6 @@ contracts:
 
 Run the application normally. The execution and its business result appear at **http://localhost:8501**.
 
-> `witdem-sdk` 0.2.0 is not yet published to the package index. The source-checkout command above is the verified installation path for this release. Publishing the package is the remaining installation launch blocker.
-
 ## What you get
 
 - Actual execution paths, branches, loops, retries, tools, model calls, and failures
@@ -114,6 +170,7 @@ Statuses reflect current implementation and test evidence, not roadmap intent.
 | [LangGraph](docs/integrations/langgraph.md) | **Beta** | Compiled graphs, nodes, tools, models, errors, sync/async invocation and streaming |
 | [LangChain](docs/integrations/langchain.md) | **Beta** | Runnables, chains, chat/LLM calls, tools, retrievers, sync/async invocation and streaming |
 | [Native Python](docs/integrations/native-python.md) | **Supported** | Execution, operation, model, tool, decision, evaluation, outcome, and metric primitives |
+| [Direct OpenAI SDK](docs/integrations/openai.md) | **Beta** | Responses, Chat Completions, embeddings, sync/async and streaming calls, usage, tool-call IDs |
 | [OpenAI Agents](docs/integrations/openai-agents.md) | **Beta** | Native trace processor, agents, generations, tools, handoffs, sync/async workloads |
 | [Anthropic Messages and Claude Agent SDK](docs/integrations/anthropic.md) | **Beta** | Messages calls, usage, tool-use IDs, multi-turn workloads, Claude Agent message streams |
 | [Hugging Face smolagents](docs/integrations/smolagents.md) | **Beta** | Official OpenInference agent, step, model, and tool spans; sync and streaming execution |
@@ -122,6 +179,8 @@ Statuses reflect current implementation and test evidence, not roadmap intent.
 | Generic provider calls | **Experimental** | Sync/async callable wrapper with explicit provider/model and observed result metadata |
 | Standard OTLP/HTTP | **Supported** | Generic OpenTelemetry, OTel GenAI, and OpenInference evidence |
 
+Witdem also normalizes retrieval, reranking, search, embeddings, OCR, tools, evaluations, image, audio, video, and extension operations without inferring vendors. See [AI operations and evaluations](docs/ai-operations.md).
+
 See [`compatibility.json`](compatibility.json) for machine-readable version constraints and [Providers](docs/providers.md) for the difference between native, framework-observed, and generic support.
 
 ## Providers
@@ -157,9 +216,8 @@ The runnable [Haystack parallel pipeline](examples/haystack/pipeline/README.md)
 
 ## Self-hosting
 
-The npm launcher is the recommended local backend path. It is deliberately a
-small, dependency-free Docker launcher rather than a second implementation of
-Witdem. It never runs an npm `postinstall` script.
+NPX is the Docker-managed path; pipx is a genuinely native, Node-free and
+Docker-free path. The npm package never runs a `postinstall` script.
 
 | Service | Address | Purpose |
 | --- | --- | --- |
@@ -168,21 +226,14 @@ Witdem. It never runs an npm `postinstall` script.
 | ELT worker | internal | Duckle transformation into dashboard-ready DuckDB tables |
 
 ```bash
-npx -y witdem@0.2.0 status
+npx -y witdem@latest status
 curl http://localhost:4318/readiness
 curl http://localhost:8501/health
 ```
 
-For source development, clone the repository and run `docker compose up -d`.
-See [Running Witdem with npx](docs/npm-launcher.md) for ports, lifecycle, image
-pinning, and troubleshooting.
-
-The Python-only development path is also available:
-
-```bash
-uv sync
-uv run witdem dev --open
-```
+See [Operations](docs/operations.md) for lifecycle, ports, logs, data,
+backup/recovery, and [Development](docs/development.md) only when contributing
+to Witdem itself.
 
 ## Documentation
 
@@ -191,6 +242,7 @@ uv run witdem dev --open
 - [Concepts: tracing and business meaning](docs/concepts.md)
 - [Tutorial: defining a YAML contract](docs/contract-tutorial.md)
 - [YAML configuration](docs/configuration.md)
+- [Workflow definitions, compilation, and replay](docs/workflow-replay.md)
 - [Haystack](docs/integrations/haystack.md)
 - [LangGraph](docs/integrations/langgraph.md)
 - [LangChain](docs/integrations/langchain.md)
@@ -203,8 +255,26 @@ uv run witdem dev --open
 - [Troubleshooting](docs/troubleshooting.md)
 - [Examples](docs/examples.md)
 - [Operations](docs/operations.md)
+- [CLI reference](docs/cli-reference.md)
+- [Upgrade and compatibility](docs/upgrade.md)
+- [Architecture and data flow](docs/architecture.md)
+- [Release notes](docs/changelog.md)
+- [Performance and lifecycle implementation report](docs/implementation-report.md)
 - [Development and contributing](docs/development.md)
 
+## Community
+
+Witdem is built in the open. Bug reports, integration examples, documentation
+improvements, and focused code contributions are welcome.
+
+- Read [Contributing](CONTRIBUTING.md) before opening a pull request.
+- Participate under the [Code of Conduct](CODE_OF_CONDUCT.md).
+- Report vulnerabilities privately according to the [Security policy](SECURITY.md).
+
+## License
+
+Witdem is licensed under the [Apache License 2.0](LICENSE).
+
 ## Built with
 
 <table>

{witdem_analytics-0.2.0 → witdem_analytics-0.2.2}/README.md

@@ -1,40 +1,91 @@
 <div align="center">
 
+<img src="docs/assets/witdem-banner.png" alt="Witdem AI — Understand how your AI system actually behaves" width="100%">
+
 # Witdem
 
 **Analytics for AI agents and multi-step AI applications.**
 
 Tracing tells you what executed. Witdem connects those executions to application outcomes: which paths ran, what they cost, where they failed, and whether they achieved the product goal you defined.
 
-[Get started](docs/getting-started.md) · [YAML contracts](docs/contract-tutorial.md) · [Haystack](docs/integrations/haystack.md) · [Frameworks](#integration-status) · [Providers](docs/providers.md) · [Troubleshooting](docs/troubleshooting.md)
+[![Tests](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml/badge.svg)](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml)
+[![SDK on PyPI](https://img.shields.io/pypi/v/witdem-sdk?label=witdem-sdk)](https://pypi.org/project/witdem-sdk/)
+[![Analytics on PyPI](https://img.shields.io/pypi/v/witdem-analytics?label=witdem-analytics)](https://pypi.org/project/witdem-analytics/)
+[![npm](https://img.shields.io/npm/v/witdem/latest?label=npx%20witdem)](https://www.npmjs.com/package/witdem)
+[![Python](https://img.shields.io/badge/Python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13-blue)](https://github.com/ebrahimisoheil/witdem-oss/actions/workflows/test.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+[Get started](docs/getting-started.md) · [YAML contracts](docs/contract-tutorial.md) · [Frameworks](#integration-status) · [Providers](docs/providers.md) · [Contributing](CONTRIBUTING.md) · [Security](SECURITY.md)
 
 </div>
 
+## See Witdem in action
+
+From one-line setup and two-line instrumentation to a measured run, its
+execution graph, business outcome, cost, and contract evidence.
+
+<p align="center">
+  <a href="https://cdn.jsdelivr.net/gh/ebrahimisoheil/witdem-oss@37e335d/docs/assets/witdem-demo.mp4">
+    <img src="docs/assets/witdem-demo-poster.jpg" alt="Watch the Witdem installation and analysis walkthrough" width="100%">
+  </a>
+  <br>
+  <a href="https://cdn.jsdelivr.net/gh/ebrahimisoheil/witdem-oss@37e335d/docs/assets/witdem-demo.mp4"><strong>▶ Watch the 1:48 installation-to-analysis walkthrough</strong></a>
+</p>
+
 ## First run
 
-Start the local receiver, ELT worker, and dashboard:
+Choose one backend launcher. Applications use `witdem-sdk` with either path.
+
+Docker-managed (requires Docker Compose):
+
+```bash
+npx -y witdem@latest up
+```
+
+Native Python (requires Python and [pipx](https://pipx.pypa.io/)):
+
+```bash
+pipx install witdem-analytics
+witdem up
+```
+
+Both start the receiver, ELT worker, and dashboard, wait for health, open
+`http://localhost:8501`, and preserve data across `down` and upgrades. Their
+lifecycle vocabulary is the same:
 
 ```bash
-npx -y witdem@0.2.0 up
+npx -y witdem@latest status   # Docker path
+witdem status                     # pipx path
+npx -y witdem@latest logs receiver
+witdem down
 ```
 
-That pulls the version-matched container, starts all three services, waits for
-them to become healthy, and opens `http://localhost:8501`. Docker with Compose
-is the only prerequisite. Data persists across `down` and package upgrades.
+Check releases and compatibility without changing packages or data:
 
 ```bash
-npx -y witdem@0.2.0 status
-npx -y witdem@0.2.0 logs
-npx -y witdem@0.2.0 down
+npx -y witdem@latest update --check
+witdem update --check
 ```
 
-Add the SDK to an existing Haystack 3 project from the checkout:
+See the [upgrade guide](docs/upgrade.md) for exact NPX, pipx, and SDK commands.
+
+Add the SDK to an existing Haystack 3 project:
 
 ```bash
-python -m pip install -e "/path/to/Witdem-Analytics/witdem-sdk[haystack]"
+python -m pip install "witdem-sdk[haystack]"
 export WITDEM_ENDPOINT=http://localhost:4318
 ```
 
+From the application project, create the YAML contract and then edit it to
+describe that application's result:
+
+```bash
+witdem-sdk init --runtime haystack
+```
+
+This creates `.witdem/witdem.yaml`. It does not inspect or rewrite application
+code, and it will not replace an existing contract unless `--force` is used.
+
 Wrap the pipeline once. Its existing `run`, `run_async`, and `run_async_generator` calls stay unchanged:
 
 ```python
@@ -71,8 +122,6 @@ contracts:
 
 Run the application normally. The execution and its business result appear at **http://localhost:8501**.
 
-> `witdem-sdk` 0.2.0 is not yet published to the package index. The source-checkout command above is the verified installation path for this release. Publishing the package is the remaining installation launch blocker.
-
 ## What you get
 
 - Actual execution paths, branches, loops, retries, tools, model calls, and failures
@@ -94,6 +143,7 @@ Statuses reflect current implementation and test evidence, not roadmap intent.
 | [LangGraph](docs/integrations/langgraph.md) | **Beta** | Compiled graphs, nodes, tools, models, errors, sync/async invocation and streaming |
 | [LangChain](docs/integrations/langchain.md) | **Beta** | Runnables, chains, chat/LLM calls, tools, retrievers, sync/async invocation and streaming |
 | [Native Python](docs/integrations/native-python.md) | **Supported** | Execution, operation, model, tool, decision, evaluation, outcome, and metric primitives |
+| [Direct OpenAI SDK](docs/integrations/openai.md) | **Beta** | Responses, Chat Completions, embeddings, sync/async and streaming calls, usage, tool-call IDs |
 | [OpenAI Agents](docs/integrations/openai-agents.md) | **Beta** | Native trace processor, agents, generations, tools, handoffs, sync/async workloads |
 | [Anthropic Messages and Claude Agent SDK](docs/integrations/anthropic.md) | **Beta** | Messages calls, usage, tool-use IDs, multi-turn workloads, Claude Agent message streams |
 | [Hugging Face smolagents](docs/integrations/smolagents.md) | **Beta** | Official OpenInference agent, step, model, and tool spans; sync and streaming execution |
@@ -102,6 +152,8 @@ Statuses reflect current implementation and test evidence, not roadmap intent.
 | Generic provider calls | **Experimental** | Sync/async callable wrapper with explicit provider/model and observed result metadata |
 | Standard OTLP/HTTP | **Supported** | Generic OpenTelemetry, OTel GenAI, and OpenInference evidence |
 
+Witdem also normalizes retrieval, reranking, search, embeddings, OCR, tools, evaluations, image, audio, video, and extension operations without inferring vendors. See [AI operations and evaluations](docs/ai-operations.md).
+
 See [`compatibility.json`](compatibility.json) for machine-readable version constraints and [Providers](docs/providers.md) for the difference between native, framework-observed, and generic support.
 
 ## Providers
@@ -137,9 +189,8 @@ The runnable [Haystack parallel pipeline](examples/haystack/pipeline/README.md)
 
 ## Self-hosting
 
-The npm launcher is the recommended local backend path. It is deliberately a
-small, dependency-free Docker launcher rather than a second implementation of
-Witdem. It never runs an npm `postinstall` script.
+NPX is the Docker-managed path; pipx is a genuinely native, Node-free and
+Docker-free path. The npm package never runs a `postinstall` script.
 
 | Service | Address | Purpose |
 | --- | --- | --- |
@@ -148,21 +199,14 @@ Witdem. It never runs an npm `postinstall` script.
 | ELT worker | internal | Duckle transformation into dashboard-ready DuckDB tables |
 
 ```bash
-npx -y witdem@0.2.0 status
+npx -y witdem@latest status
 curl http://localhost:4318/readiness
 curl http://localhost:8501/health
 ```
 
-For source development, clone the repository and run `docker compose up -d`.
-See [Running Witdem with npx](docs/npm-launcher.md) for ports, lifecycle, image
-pinning, and troubleshooting.
-
-The Python-only development path is also available:
-
-```bash
-uv sync
-uv run witdem dev --open
-```
+See [Operations](docs/operations.md) for lifecycle, ports, logs, data,
+backup/recovery, and [Development](docs/development.md) only when contributing
+to Witdem itself.
 
 ## Documentation
 
@@ -171,6 +215,7 @@ uv run witdem dev --open
 - [Concepts: tracing and business meaning](docs/concepts.md)
 - [Tutorial: defining a YAML contract](docs/contract-tutorial.md)
 - [YAML configuration](docs/configuration.md)
+- [Workflow definitions, compilation, and replay](docs/workflow-replay.md)
 - [Haystack](docs/integrations/haystack.md)
 - [LangGraph](docs/integrations/langgraph.md)
 - [LangChain](docs/integrations/langchain.md)
@@ -183,8 +228,26 @@ uv run witdem dev --open
 - [Troubleshooting](docs/troubleshooting.md)
 - [Examples](docs/examples.md)
 - [Operations](docs/operations.md)
+- [CLI reference](docs/cli-reference.md)
+- [Upgrade and compatibility](docs/upgrade.md)
+- [Architecture and data flow](docs/architecture.md)
+- [Release notes](docs/changelog.md)
+- [Performance and lifecycle implementation report](docs/implementation-report.md)
 - [Development and contributing](docs/development.md)
 
+## Community
+
+Witdem is built in the open. Bug reports, integration examples, documentation
+improvements, and focused code contributions are welcome.
+
+- Read [Contributing](CONTRIBUTING.md) before opening a pull request.
+- Participate under the [Code of Conduct](CODE_OF_CONDUCT.md).
+- Report vulnerabilities privately according to the [Security policy](SECURITY.md).
+
+## License
+
+Witdem is licensed under the [Apache License 2.0](LICENSE).
+
 ## Built with
 
 <table>