Dashboard

Orloi includes a default dashboard for teams that want a useful interface without building their own.

The dashboard is a view on top of the data stored in Postgres. It does not replace the underlying changelog contract.

What the dashboard shows

The dashboard can surface:

• engine status
• last raw event time
• latest compacted event time
• compaction lag
• recent activity
• reports
• metrics
• alerts and process signals

It is designed to answer practical operational questions:

• What happened recently?
• Which metrics changed?
• Which records or workflows need attention?
• What did the daily or weekly report say?
• Which processes appear to be slowing down or repeating?

Before relying on an insight, check freshness: selected scope, engine status, last raw event time, latest compacted event time, compaction lag, and latest report status.

Freshness checks

Signal	Meaning	If stale
Last raw event time	Orloi is receiving Airtable changes.	Check Airtable connection and scope.
Latest compacted event time	Raw events are being processed into readable history.	Check processing status.
Compaction lag	Raw events are waiting to become compacted events.	Check processing status before trusting summaries.
Latest report status	Report generation state.	Check AI and report configuration.

Reports

Daily and weekly reports summarize Airtable activity into an operations briefing.

Reports are useful when the team wants to understand what changed without manually checking views, filters, Slack updates, and individual records.

Report generation can have separate stages: collecting report data, preparing AI report context, writing the report, saving it, and optionally sending email. If a report is delayed or failed, the dashboard shows stage details when that information is available.

Metrics

Metric cards show computed signals from activity history.

Examples include volume of new records, completed work, reopened work, handoffs, source activity, status transitions, and other configured or surfaced metrics.

Metrics are more useful with enough history. When Orloi has limited history, comparisons and anomaly language should stay conservative. A new metric may show values before it has enough prior windows to make confident claims.

Metric details can link back to the raw events that contributed to a stored metric value while those raw events remain in hot storage.

Processes and trends

Process and trend surfaces help reveal movement over time.

They can show common paths records take, recurring transitions, repeated manual work, bottlenecks, or unusual changes in activity volume.

For inspection, Orloi uses compacted events as the readable evidence layer. Raw events are available for deeper audit and debugging detail.

Dashboard is optional

The dashboard is the default interface, but the stored Postgres history remains available for SQL, BI tools, custom UIs, and AI agents.