Concept

Operational Intelligence

Every governed decision becomes a source of operational knowledge. Operational Intelligence is the set of readings Aarmos derives from evidence you already recorded — signed receipts and deterministic replay. It explains historical behaviour. It does not make organizational decisions, generate recommendations, or score you.

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.

Decision Effectiveness

Under Operations, Decision Effectiveness groups readings around the Decision — the 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 a decision behaved consistently across the window: unchanged, moved, or not observed.
• Counterfactual analysis — replay under an alternate governance configuration to see what would have happened. Aarmos reports how many executions could be judged out of how many were examined.
• Overlapping execution — where more than one actor executed the same Decision. 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.

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 observe

The service binds to loopback only and is read-only. Nothing starts it for you — no other command opens a browser or prints a credential. It prints a short-lived, single-use pairing code and the exact address to open; the browser then exchanges that code over loopback for a scoped, read-only grant that expires when the session ends. No token ever travels in a URL, and no evidence leaves your machine.

For the full walkthrough — the destination URL, remembering a browser, and how to revoke it — see Observe a local runtime.

Everything the browser shows is derived from the signed receipts on disk and reproducible from them. The receipts remain the only source of truth; the observation surface stores nothing.

Related: Decision governance and AVAR receipts.