Concept
Operational Intelligence
Every governed decision becomes a source of operational knowledge. Operational Intelligence is the umbrella for understanding and controlled improvement derived from evidence you already recorded — signed receipts and deterministic replay. Understand is observation-only. Improve is a separate controlled-analysis path that may produce inert findings and candidate changes. Neither changes active governance.
What it reads from
Only recorded evidence. Every reading traces back to receipts or to a deterministic replay of them, and no reading creates new evidence. If something was never observed, Aarmos says it was not observed rather than reporting a zero.
Coverage is always disclosed
Readings are computed over a fixed window of recent executions, and the window, the number of executions behind it, and the age of the newest and oldest observation are shown alongside every result. Counts come first; shares are secondary. Aarmos never presents a reading as if it covered work it never saw.
Historical decision behavior
Under Operations, The signed-in product includes an evidence-derived historical analytical lens called Decision Effectiveness. It is not a score of decision quality, safety or performance. It groups readings around the Consequence — the proposed business action — rather than around agents:
- Contribution — which participants and inputs the observed outcomes actually depended on. Contribution is not importance, and the table is ordered alphabetically, not ranked.
- Stability — whether Decisions for a Consequence stayed consistent across the window: unchanged, moved, or not observed.
- Counterfactual analysis — replay under an alternate governance configuration to ask which recorded Decisions would have differed. Aarmos reports how many records could be judged out of how many were examined. This is historical analysis, not prediction.
- Overlapping execution — where more than one actor executed the same Consequence. This is an evidence-backed observation about behaviour, never a similarity guess about prompts or code.
Humans decide
A reading can be acknowledged, which records that a person looked at it and made a call. Acknowledgements behave like certificates: they lapse quietly after 90 days and are never escalated into alerts. Any change you make as a result flows back through the normal governed change path.
The Aarmos CLI is not publicly distributed. Commands here are reference examples, not instructions you can run today.
Seeing it from the CLI or the browser
If you work entirely in a terminal, aarmos activity reads the same receipts directly from disk. If you want the richer view in Operations, start the local observation service explicitly:
aarmos observeThe local observation path is explicit and read-only. Evidence may remain local or customer-controlled, or use supported optional configured delivery. For setup and revocation details, use the local runtime guide rather than treating this concept page as a data-handling specification.
For the full walkthrough — the destination URL, remembering a browser, and how to revoke it — see Observe a local runtime.
Readings shown in the browser remain derived from recorded evidence and deterministic replay. Missing or unavailable evidence is not inferred.
Related: AVAR receipts.