# Release notes 0.1.183

> 1 November 2026: 0.1.182 brought the option-5 content and the "scifi" look; this release brings its page layout to the pages operators use every day.

_Release notes · Updated 2026-11-01 · Describes release 0.1.183_

## 0.1.183 — 1 November 2026 {#0-1-183-1-november-2026}

### The option-5 page frames {#the-option-5-page-frames}

0.1.182 brought the option-5 content and the "scifi" look; this release brings its page layout to the pages operators use every day.

- **App shell.** The top bar runs the full width (workspace switcher, search, estate graph, clock, theme, account). The sidebar is 240 px with a collapse rail; every group says what it is for, the settings groups fold into one **Settings** group at the bottom, and Compliance lists Posture, Findings (Vulnerabilities, Patching, Backup, All) and Audit & coverage. The Human gate card sits in the sidebar under the menu. Each page opens with a breadcrumb, its title and one line on what it is for, with the read connections it uses as chips at the top right ("+N sources" opens the rest). The floating chat button is gone; Chat stays in the sidebar.
- **Dashboard.** One row of KPI tiles (unresolved incidents, needs attention, MTTA, MTTR, alert noise reduced, auto-handled events), then the Human gate card with the first decisions and their Open buttons, the opened-vs-resolved chart, and two folds: **Alerts → incidents · per month** and **Pillar health**. Needs you groups its cards by kind with a "+N more" fold on each.
- **Incidents and findings.** The list is one card with a **Filters** button (cloud, triage, service) and a "Hide test records (N)" chip; the grouping strip starts folded. The record page puts **What happened** and **What you need to do** side by side above the **Where it stands** step bar, then the blast radius, a short Timeline and folded sections. A finding shows its **exposure path** and a **Combined risk** call-out (the "recurring", "reopened" and "problem proposed" chips now live there), and its decision card **Decide: fix it or accept the risk**.
- **Service dependencies.** The graph and the table sit side by side from 1280 px; the legend names each line style (declared solid, traced dashed, discovered dotted, observed thin grey).
- **Changes and runbooks.** The Changes list has two tabs, **Requests through the platform** and **Seen outside the platform** (outside changes grouped into cards). A change page opens on its top card with the result headline, the step bar and one primary; the **Change request document** is folded, and a completed change offers **Download change request (.md)**. An outside change suspected by an incident offers **Open the incident it is suspected of causing**; its Before state starts folded. Runbook cards show who certified them and, when one was taken off pre-approval, what took it off.
- **Compliance.** Posture shows the total score with patching and backup bars beside a score per standard with its own trend line. The findings lists rank their report cards, move Score and trend and Scanner sync under Diagnostics, and count P1 / P2 findings in a tile.
- **Settings pages.** Guardrails opens on four numbered cards (1 Approvals & change classes, 2 Maintenance windows as a calendar, 3 Automatic fixes, 4 Cost), followed by Change safety and Triage & agents; every switch shows an On/Off badge and the longer rule sets are folded. Alert intake shows a card for the intake rules ("Alerts that match no service go to triage · On") and a short webhook address per source (copy still copies the full URL). Data sources are grouped Read / Read & write / Write only. AI models carries a Residency check column. Dates on Changes and Artifacts are one compact line with the full stamp on hover.

### API additions {#api-additions}

- `GET /api/aiops/{tid}/findings/{id}/exposure` returns a finding's exposure path and combined risk from what the platform already holds: the finding's context signals, the harvested estate inventory (world-open ingress rules and attachments, only with `datasources.view`) and other open findings on the same resource. Nothing missing is filled in.
- The incident list takes `test=true|false`; the summary returns `test_count` and `by_priority`.
- Change rows and the change detail carry `suspected_by` (up to five incidents that name the change as a suspect, `incidents.view`).


## Next steps

- Next: [Release notes 0.1.182](/help/release-notes-0-1-182.md)
- [All What's new pages](/help/what-s-new/llms.txt)
- [Documentation home](/help/)