Signals Tab: Investigate Workflow Waste and Deterministic Anomalies

The Signals tab (/enterprise/orgs/{org_id}/signals) helps organization administrators find recurring AI-work patterns and investigate deterministic anomaly findings with the sessions behind them.

​

Date range

The page opens to the last 30 days. Set From and To dates or select Last 30 days to reset the range. The range applies slightly differently to each section:

• The Signals matrix includes signal periods written during the selected window.
• Anomaly reports include findings whose latest occurrence falls inside the selected window.
• The selected To day is included; the frontend sends the following day as the API’s exclusive upper bound.

​

Signals matrix

Signals group recurring patterns by team and project so you can see where enablement, policy, or durable project context will have the most leverage. Each populated cell shows:

• Projected tokens per week when the signal has an estimate.
• Open signal count when projected-token coverage is unavailable.
• A stronger color for a larger projected opportunity or open count within that matrix.
• Linked evidence sessions when the cell is clickable.

The page provides three views:

• P4 · Users with waiting sessions — sessions, qualifying wait events, maximum and total wait, the worst session, and a direct evidence-session link.
• Teams × patterns — concentration across a team, best used for shared conventions, policy, and enablement rather than individual performance review.
• Projects × patterns — concentration by codebase. Projects with the same configured display name are merged into one row.

For P4 project cells, the value is the number of affected sessions. Elapsed wait time is not converted into token savings.

​

How to investigate a Signal

1. Find concentration — start with the darkest or largest populated cells.
2. Choose the owner — team rows usually point to a policy or enablement owner; project rows point to a codebase owner; P4 user rows identify exact sessions to review.
3. Open evidence — inspect linked sessions before deciding whether the pattern needs a change.
4. Read the pattern details — select a code in What the pattern codes mean for examples, recommended admin actions, and interpretation guardrails.

​

Pattern catalog

​

Monthly CSV report

Select Export YYYY-MM CSV to download the current month’s organization-, team-, and project-scoped Signals. The report includes the period, scope, pattern, status, evidence count, idle minutes, measured opportunity tokens, and projected tokens. Member identities are not included.

​

Anomaly reports

Anomaly reports are nightly deterministic checks over completed session data. They are not AI-generated classifications. The header shows the number of open findings and the number currently marked high or critical. Filter the list by:

• Status: open, new, acknowledged, resolved, dismissed, or all.
• Severity: warning, high, critical, or all.
• Detector.
• The page-level date range.

Each finding shows its detector code, severity, status, subject, latest occurrence, occurrence count, evidence summary, and linked sessions when available.

​

Detectors

​

Finding status workflow

• Acknowledge a new finding when it is under review.
• Resolve it when the relevant work or remediation is complete.
• Dismiss it when the finding is expected behavior or a false positive.
• Resolved and dismissed findings are closed and cannot transition to another status.

​

Who sees it

The Signals tab, organization matrix, anomaly findings, status actions, and monthly CSV export are administrator-only. The navigation hides this tab from team leads and developers, and the backend enforces the same boundary. For the surrounding operating model, see Enterprise Observability. Use Sessions to continue a broader investigation and Tokens for organization-wide consumption and measured context reduction.