Skip to main content
Observatory availability. In FlowX.AI 6.0, Observatory runs on environments operated by FlowX. It isn’t included in client deployments in this release.
The Agentic Readiness Index (ARI) answers one question: is this workflow ready for the level of autonomy it runs at? Open it from Governance › Readiness Index. Each workflow gets a deterministic, audit-defensible score from 0 to 100 across four dimensions (Autonomy, Audit-Trace, Reversal Rate and ROI), a Green, Amber or Red band, and the evidence behind the number.

​
What does the page show?

  • Org readiness: the composite readiness for the selected organization. It’s also the Agentic readiness card on the Governance Hub, weighted by exposure across scored workflows.
  • Workflow readiness scores: one row per workflow with its composite score, band and any Blocking gate that fired. Use Recompute on a row or Recompute all to rescore.
  • Scoring models: the published scoring models available to the org.
Open a workflow’s drill-down to see the Dimension breakdown, its Declared autonomy, the state of each control, the Score history and the publishing actions. A score marked Provisional (insufficient data) left out at least one dimension because there wasn’t enough data for it in the scoring window.

​
How is a workflow scored?

ARI computes four dimension scores from 0 to 100, then combines them with the weights of the selected scoring model. Scoring is deterministic and uses no LLM: the same inputs and the same scoring model version always produce the same score.
The reversal rate is an estimate. It’s derived from discarded and overridden actions, not from a dedicated reversal event.
A dimension with no data in the window (no executions, no autonomous actions, or not enough ROI data) is left out of the composite, and the score is marked provisional.

​
Scoring models

A published scoring model never changes. Any change to weights or thresholds ships as a new model version, so every score stays reproducible from its inputs and its model version.

​
Bands

​
What are blocking gates?

A blocking gate caps the band at Red whatever the composite score, and the workflow row shows which gate fired. Each gate is checked on its own: A workflow counts as high risk when its risk classification is high, critical or unacceptable.

​
How do autonomy levels and controls work?

Each workflow carries a Declared autonomy level. A workflow nobody has classified shows Default (never declared). To change it, select Edit in the drill-down, pick the Autonomy tier and enter a Note, which is required. The Autonomy dimension checks five control families: Approval gate, Reversibility, Kill switch, Scoped authorization and Escalation path. Higher autonomy requires more of them: High-risk workflows also require an approval gate, a kill switch and reversibility at every level. Set each control’s state to Present, Partial or Absent in the drill-down, with an Evidence URL and a note.

​
How do I share a score?

From a workflow’s drill-down:
  • Evidence pack (PDF) exports the score with its evidence for an auditor or risk committee.
  • JSON exports the same score as structured data.
  • Publish score sends the latest score and band to the org’s webhooks subscribed to the ari.score.published event, with an optional note. Nothing is written to FlowX core. The drill-down then shows when the score was last published and by whom.

Governance

The Governance Hub and the rest of the controls layer.

Risk Hub

Six-dimensional risk score per app.

ROI & value

The ROI Hub numbers that feed the ROI dimension.

EU AI Act

How Observatory maps to the EU AI Act.
Last modified on November 9, 2026