A tour of the console

This page is a map of the console: what each screen is for, where it is, and which guide to read when you need to act on it. What you see depends on your role: the console hides controls your role cannot use (the gear, New filter, Stop or hold), as a convenience. The server enforces every role, whatever the screen shows.

The header

Every signed-in page has the same header.

Where	What it is
Left: Dashboard, Filters	The two places in the console. The logo also goes to the dashboard.
Right: the bell	Alerts. Its count is the number of faults plus the items waiting on someone, except the two kinds of banner below. It shows `?` when the count could not be read.
Right: the gear icon	Administration. Shown to admins only.
Right: the person icon	Your account: your username and role, Appearance (Auto, Light, Dark), Documentation (these pages, in a new tab), Change password and Sign out.

A Mock data label beside the bell means demonstration data is loaded and real filters are hidden. Banners under the header warn about a default administrator password and about the Kindo connection; they stay until the condition is fixed.

There is no New filter link in the header. Operators and admins start a filter from the Filters page, the dashboard’s Filters panel, or the setup checklist (see Create a filter).

The footer shows Sift’s version, and the environment name when it is not production.

The dashboard

The dashboard at / has two forms.

While Sift is being set up it is a checklist, Get Sift running, with five steps (Step 2 of 5) and who does each:

Step	Who
Connect to Kindo	admin
Choose Sift’s model	admin
Create your first filter	operator
Sift learns in shadow	Sift
Approve a threshold and start filtering	operator

If you cannot act on the current step, you see who can instead of a button. A System panel lists deployment warnings. The first two steps are in Connect Kindo.

Once the first three steps are done, the dashboard shows the fleet. Its panels:

The page line: how many filters and how many are filtering, and the reporting window (7d, 30d, 90d; 30 days by default). Under the title, As of 14:02:31 says how fresh the page’s figures are (below).
The system line: four readings, Kindo, Workers, Ingest and Delivery. System details opens the detail.
Road to production: how many filters are at each stage (Draft, Shadow, Proposed, Filtering) and the step each one is on.
Needs attention: what needs a person now, worst first. Filter rows link to the filter’s Actions tab; Kindo and Deployment rows link to Alerts, as do All alerts and +{n} more in Alerts. The chips are All, Faults and For reviewers, each with its count; for a reviewer, For reviewers is selected. With nothing urgent the panel is titled Nothing urgent, and with nothing at all it says Nothing needs you. (a reviewer sees No gold sets waiting for you.).
The window panel, Last {n} days: Agent runs avoided (Agent runs saved once a filter groups escalations; Would have filtered while no filter is filtering), and The risk taken for it: the miss rate and escalations undelivered.
Every day: daily bars of filtered, would-filter and escalated events. While nothing needs attention, the window panel takes the full width and draws these bars itself.
Filters: the first eight filters that are not retired, with Show all {n}, and New filter for operators and admins.
Recent decisions: the last five decisions in the window, with who made them (a person, or Sift). Admins get a link to the Audit log.

The order depends on whether any filter is filtering yet:

While no filter is filtering	Once a filter is filtering
Page line, system line	Page line, system line
Road to production	Needs attention beside the window panel
Needs attention beside the window panel	Every day
Every day	Filters
Filters	Road to production beside Recent decisions
Recent decisions

Watch a running filter explains the figures.

As of

The dashboard’s and the Filters page’s figures are kept ready in advance, so the pages open at once. The line under the title says when they were counted: As of 14:02:31 is the oldest moment among the page’s figures, in your own time zone and your browser’s clock format. The checklist shows it too.

How old a figure can be: up to a minute.
What refreshes them at once: a filter’s state change, an approval or rejection, a saved spec, a corrected label, pausing or resuming, pairing an agent, acknowledging a cutover, and switching the verdict check on or off, as well as connecting Kindo or choosing Sift’s model. New events, scores, agent runs and new labels show within the minute.
updating… after the time means a figure was being recounted when the page asked. The page asks again a few seconds later and the word goes; if the recount takes longer, the newer figure arrives with the page’s next refresh.
What is always current: a filter’s own page, and every decision Sift makes (an approval gate, the label floor, a health verdict on Actions). None of them use these ready-made figures.

There is no line when an operator has switched this off (see Configuration): every figure is then counted when the page asks for it.

Alerts

The bell opens Alerts: every condition that is true now, in two groups, Faults (n) (something is broken) and Waiting on you (n) (nothing is broken, but nothing moves until someone acts). Rows cannot be dismissed; each clears when its condition does. See Health, Actions and alerts.

The Filters page

Filters lists every filter, with its own reporting window (7d, 30d, 90d) and a chart of where the window’s events went. Under the title, As of and updating… say how fresh the table and the chart are, as on the dashboard (As of).

Chips narrow the list, each with its count: All, Needs attention, Building (draft, authoring), Running (shadow, proposed, active), Inactive (paused, retired).
The table’s columns are Filter, State, Events, Filtered, Miss rate, Runs avoided, Grouped and 14 days. Click Events, Filtered, Miss rate, Runs avoided or Grouped to sort, again to reverse, and a third time for the default order.
Operators and admins see New filter, and any conversation they left before creating a filter, as a draft in progress with the time it expires.

A filter’s state shows as a badge: its lifecycle state (shadow, proposed), or Filtering when it is filtering. A second badge, Attention or Fault, links to what needs doing. States, badges and health codes lists them all.

A filter’s page

Open a filter to see its header and tabs. The header has its name, id, version and deciding recipe, its badges, and when its source was last polled. Operators and admins also get Stop or hold, offering only the moves the state allows: Stop filtering while the filter is active, and Hold events while it is in shadow, proposed or active. Other states have no menu. See Hold, stop, resume or retire a filter.

Tab	What it is for	Guide
Actions	What the filter needs, who should act, and its setup steps. The filter opens here when it has any ask, Sift’s own progress included; the tab’s count is only what is owed a person. Absent once a filter is retired.	Work through Actions
Overview	A band for where the filter stands (setting up, the threshold decision, events held, retired) or where its events went, then Every day, Is it safe, How it decides, Ingest and delivery, Recently and Reference.	Watch a running filter
Settings	Every setting, in sections (General, Source, Labels, Pipeline, Delivery, Lifecycle, Retire, History), saved as versions. A reason is optional unless the change needs a new approval.	Change a filter’s settings
Activity	The filter’s timeline: polls, runs, verdicts, approvals, versions. Links to Filtered events.	Watch a running filter
Gold set	The examples that decide whether the filter may start.	Review the gold set
Verdict check	Shown only when the check is on: verdicts the decision model disputes.	Answer the verdict check

Three screens are reached from a filter rather than being tabs: the threshold screen (Threshold promotion, or Grouping approval for Shape delivery; see Approve a threshold), Connect the agent (see Connect a filter to its agent), and Filtered events, linked from Activity.

Administration

Admins reach Administration from the gear icon. Anyone else who opens it is told “Administration requires the admin role.” Its pages are Kindo connection, Users, Filter recipes, Decision model, Notifications and Audit log, each covered under Administration in these docs, starting with The Kindo connection.

What each role sees and does

Role	Can
Reviewer	Read everything about filters, label gold-set examples, answer the verdict check.
Operator	Everything a reviewer can, plus create and change filters, approve gold sets and thresholds, start, stop, hold and retire filters.
Admin	Everything an operator can, plus Administration.

The gold-set and threshold approval forms are shown to reviewers too, but the server refuses a reviewer’s approval: approvals need an operator or admin. See Users and roles.