xrtm 0.8.8

The xRtm Framework (Generative Forecasting).

XRTM: AI for event forecasting

XRTM is the product-first shell for running event-forecasting workflows, inspecting the scored artifacts, and choosing CLI or WebUI for the same released local product tasks.

Start here

If you arrived from xrtm.org, PyPI, or this repository, use the authoritative first-success guide: docs/getting-started.md.

That guide walks the released xrtm==0.8.8 journey in one place:

1. install XRTM
2. choose a CLI-led or WebUI-led first-success path
3. inspect the latest run, report, and exports
4. run a named workflow from the Start or Workflow detail surface
5. use Operations for profiles, monitors, and cleanup
6. use Hub at / or /hub for templates, readiness, recent work, and quick entry into the rest of the local product
7. use Studio at /studio (with /workbench compatibility) or the shared CLI authoring layer to create from scratch, template, or clone, then author safe workflow fields plus node/edge/entry changes, validate, run, and compare
8. use the released Playground lane for one custom question first, graph/canvas trace linkage, read-only step inspection, and explicit save-back to workflow/profile on the deterministic release baseline
9. inspect run evidence in Observatory at /observatory
10. choose your next path

The 0.8.8 release is a deterministic stabilization-and-hardening release. It keeps the bounded local Hub → Studio → Playground → Observatory product spine, hardens release-critical WebUI/API and clean-room validation paths, and does not claim a calibration dashboard, API/webhook control plane, arbitrary code/plugin graph editing, full persistent collaborative canvas layout, or a commercial runtime path without separate validation.

Current source tip also includes a fuller future-release candidate product train: Batch Runner, immutable Version snapshots, local API Control, signed webhook delivery, version-aware Observatory analytics, and the more focused three-panel Studio/Playground surfaces. Those source-visible capabilities are tracked in docs/next-release-feature-track.md and should stay out of release claims until package/docs/gates move together.

This README intentionally stays short so the first-run commands live in one place.

After your first successful run

• Researcher: use the researcher workflow on xrtm.org
• Operator: continue with the Operator Runbook
• Developer: move to the Python API Reference and integration examples

Documentation

• Getting Started Guide
• Operator Runbook
• Python API Reference
• Integration Examples
• Interface Parity Matrix for the current CLI/WebUI capability map and next parity targets
• 0.8.x Feature Track for the released 0.8.8 deterministic stabilization spine and future bounded surfaces
• Stack Versioning Policy for xrtm as the product-anchor release and cross-repo version ownership
• Full documentation: xrtm.org

License

Apache 2.0 — see LICENSE for details.