Flow Analyzer — roles, workspaces, and Jira (SaaS direction)

This page is the human-facing companion to the multi-tenant backlog in §12 of tasks/tasks-FlowAnalyzer-PRD.md. It explains who does what, how shared Jira works, how the workspace selector relates to data in SaaS mode, and where to read about credentials and security. Deployments that have not turned on organization mode may still behave like a single-tenant demo (empty / seed / operator-controlled live); those differences are called out below.

Quick links: Marketing home (product overview and sign-in) · Product tour (screenshots of key screens, including Start here, Reporting gap, Improvement actions, Priority matrix, and Results report) · Glossary (dwell, cycle time, lead time, and other flow terms — Slovník in Slovak UI) · Main app (Start here — the Brief — is your home after you sign in)

Administrator guides

Focused manuals for setup roles (English):

In-app help

After you sign in, open Help & guide in the top header (question-mark icon). The sheet shows product orientation for everyone, organization-administrator topics when your role allows, member notes when applicable, a Flow metrics glossary section with a link to the full [Glossary](/glossary) page and quick FAQ (including dwell), and a Sources & hosting area with separate expandable sections for Jira Cloud, Jira Data Center, ClickUp, Asana, Linear, Trello, and general hosting guidance. It complements the manuals above; use it when you are already inside the app.

For definitions of dwell, cycle time, lead time, WIP, and related labels, see the [Flow Analyzer glossary](./flow-analyzer-glossary.md) (public page at /glossary, titled Slovník when the UI is in Slovak).

What's new: the megaphone button in the top header opens the latest product news (release bullets). Dismiss it to hide the highlight until the next publish. For the full history, open View change log in that panel or go to [Change log](/flow-analyzer/changelog).

Compliance hub for buyers and compliance officers

Who this is for: security / compliance officers (CISO office), procurement sponsors, and enterprise IT admins evaluating Flow Analyzer for regulated delivery governance in financial services, insurance, or government.

What problem it solves: You need industry-shaped answers for audit trail, DSAR, retention, and on-prem reference architecture — mapped to controls that already shipped — without false HIPAA or SOC 2 Type II certification claims.

Where to find it: Open the public [Compliance](/compliance) hub from the marketing navigation or footer. Choose an industry tab, review the four control summary cards, and use Download playbook for the markdown appendix your security questionnaire can cite. The hub also links the Customer DPIA appendix (workforce roster / identity modes) without duplicating that document. From About, honest certification badges (including HIPAA — not applicable) link back here; the Enterprise row on Pricing links here as well. Organization admins also see a Compliance resources panel under Organization and workspaces.

How to use it: Pick your industry → download the playbook → follow evidence links (FR-COMP ids, retention / audit runbook sections, ROPA, subprocessors). For on-prem topology and the enterprise procurement pack story, use the hub CTAs (contact sales until the procurement pack from issue #128 is published). HIPAA appears only as not applicable.

Home page, sign-in, and registration

Who this is for: anyone opening Flow Analyzer in the browser for the first time, or returning after a break.

What you see first

When your organization uses signed-in access (multi-tenant mode on the server), the [marketing home](/) is a short product overview: what FlowAnalyzer does (Jira-backed flow analytics, the Brief, findings, improvement actions and priorities, results reports, and optional evaluation notes), who it is for, sample screenshots of main screens, and buttons to Sign in or Create organization. For a full walkthrough before you sign up, open the [product tour](/product-tour).

• If you already have an account, choose Sign in, enter your email and password. If your organization already has at least one workspace, you land in the [main app](/flow-analyzer); otherwise you are sent to [Organization and workspaces](/org-settings) to create one (demo seed is optional and added only when you choose it).
• If your deployment allows self-serve signup, choose Create organization. You will be asked for a display name, organization name, email, and a strong password. You can optionally leave a purchase order or customer reference for invoice matching (you can also add or change it later under Organization and workspaces → Organization). You must accept the Terms of Service and Privacy Policy; the form explains that your organization is the data controller for workforce and work-tracker data you upload. After the organization is created, sign in with the same email and password. No workspace is created for you automatically—open [Organization and workspaces](/org-settings) to add a workspace: optional demo (seed) for exploration, or a live Jira-backed workspace after you connect Jira.

Assist — Optional billing reference at register and Organization (#196)

Who it is for: Organization administrators creating a self-serve SaaS tenant (especially invoice-only B2B), and platform operators who match invoices to CRM / AP records.

Why it exists: Freemium signup should stay unblocked, but procurement often needs a PO or CRM customer id on invoices. Capturing that optional reference at register — or on first Organization visit when it is still blank — avoids a support ticket later.

What problem it solves: On Create organization, you can leave an optional Purchase order or customer reference. Skipping it still creates your organization with an empty reference and continues to sign-in as before. If you skipped it, Organization and workspaces → Organization shows a dismissible reminder that explains why to add the reference and jumps to the existing field; dismiss hides the reminder in this browser without blocking save. The same value appears on platform admin organization details.

Where in the UI: Public Create organization (/register) optional field; Organization and workspaces → Organization (field + empty callout for org admins); platform admin Organizations → [org] → Overview billing reference.

When “Create organization” is not shown

Some teams run Flow Analyzer without self-serve registration (for example internal pilots). The [marketing home](/) then explains that your administrator must enable organization mode or invite you. Use the Sign in link if you already received credentials, or ask your admin for access.

Signing out

Use Sign out or Logout (wording may vary slightly by screen) when you are done on a shared computer. After sign-out, opening the [main app](/flow-analyzer) will send you back to Sign in until you authenticate again (or open the [marketing home](/) to read the overview).

Jira embed panels (simplified view)

If you open Flow Analyzer inside Jira as a small panel or iframe, you may see a trimmed view (for example an initiative-focused screen) without going through the [marketing home](/). That path exists so Jira can embed the tool conveniently; the full product (sidebar, configuration, organization settings, and so on) is still reached from the normal browser URL your admin shares—open [Marketing home](/) or [Main app](/flow-analyzer) and Sign in there.

Operators configuring hosts, environment flags, and public routes can cross-check Local development and the Operator runbook.

Atlassian Marketplace install and pairing (coming later)

Who this is for: Jira Cloud or Data Center admins who want Flow Analyzer inside Jira from the Atlassian Marketplace, and org admins who will pair the Jira site to your Flow Analyzer company.

Status today: Marketplace Forge listing and one-click pairing are planned but deferred (programme §18.8 / #137). Until that ships, use the manual Jira embed above or open the full app in the browser.

What it will solve: Jira-native teams discover Flow Analyzer in Marketplace, install a free app, and see compact issue findings without leaving Jira — with a governed pairing code so credentials never live in Jira.

How pairing will work (when live):

1. In Flow Analyzer, an org admin opens Organization and workspaces → Integrations → Atlassian and generates a one-time pairing code (valid about 15 minutes).
2. In Jira, a site admin opens Apps → Flow Analyzer → Configure, enters the code, and confirms the site is paired.
3. Map Jira projects to Flow Analyzer workspaces on the same admin page.
4. On an issue, the Flow Analyzer panel shows recent findings (or a short “still analyzing” wait) and an Open full diagnosis link into the signed-in product. Freemium orgs see a capped teaser; full catalogue needs the Coach plan or higher.

Empty states you will see (exact wording): “Not paired yet”, “Project not mapped”, and “No data yet” — each with a short next step, never a technical error dump.

Data Center: after the Cloud path and on-prem enterprise floor are ready, a separate DC Marketplace listing will embed the same compact summary via a signed URL to your on-prem Flow Analyzer.

Display language (English and Slovak)

Who this is for: anyone who prefers Slovak UI copy or wants to switch back to English.

Where to find it: use the Language control in the top app header (next to Notes, Improvement actions, and your account menu) after you sign in. The same control also appears in the sidebar footer when the sidebar is expanded. On the [marketing home](/) and other public pages, it appears in the top navigation.

What it does: choose English or Slovenčina. The app remembers your choice in the browser and reloads labels, buttons, and help text on the current page. You do not need to sign out or change organization settings.

What is translated: navigation, dashboards, configuration screens, error messages that the app understands, and most in-product help. Public marketing pages (/, /features, /pricing, /about, /product-tour, and related legal/marketing chrome) also follow your language for headlines, capability titles, persona role lines, and section copy. Core analysis screens — Discipline, Findings, Landscape, Initiative PM, and Sankey (resource flow) — are included in Slovak coverage for tabs, columns, view labels, triage/export chrome, Flow Story markers, and related shared labels (standard acronyms such as DoD, SP, BV, RAG, and CFD stay in English; portfolio grouping uses Tribe / tribes in Slovak copy (English loanword, same as English UI)). Organization and workspaces (/org-settings) chrome — connection and workspace controls, import wizard field labels, SCIM, license plan titles, and integration table labels — is included in Slovak coverage (product and brand names such as Jira Cloud, GitHub, Slack, and Webhook URL stay in English). Configuration section labels and SectionGuidance follow Slovak when you choose Slovenčina (workflow terms and brand tokens such as SLA / Scrum / SAFe stay as documented in the localization reference). Rule names and finding text follow the same language layer as analysis output (Slovak catalogue is generated for the rule engine). On the Rules catalogue detail panel, the Príklady v praxi section shows three curated Slovak coaching situations for each rule (concrete Jira / delivery stories, not generic formula stubs). The JQL Query Builder (opened from Organization and workspaces when editing a workspace JQL scope, or from the Jira connection wizard) also follows your language for dialog title, Simple / Advanced / Import tabs, Cancel / Apply, visual-builder labels, syntax-help headings, import empty states, and query preview — Jira field names, operators, and example snippets stay in Jira’s English vocabulary.

What stays English on marketing pages (intentional): product and competitor names (for example FlowAnalyzer, Jira Cloud, ClickUp, ActionableAgile / Nave), contact emails, cookie and tracker identifiers, browser labels, numeric or timing proof stats, plan/status tokens such as Enterprise and Roadmap, the role title Scrum Master, and punctuation-only leaves. Shared product terms such as Truth Gap and Initiative PM use the same Slovak wording as in the signed-in app (Medzera v reportovaní, PM iniciatívy). Portfolio vocabulary on marketing pages uses Tribe / tribes where Slovak copy is translated (English loanword). See Web UI localization for the full marketing allowlist.

Programme note (Slovak completeness): Flow Analyzer is finishing remaining English-identical Slovak message values and hardcoded chrome through a tracked programme (epic #14). Surfaces already shipped in that programme include org-settings chrome, configuration guidance, keyboard shortcuts help, workspace switcher / admin sidebar, and related bug fixes. Further analysis, workspaces-landing, and marketing copy land via child updates; product names stay English per the allowlist in the localization reference.

What is not changed: your Jira issue text, workspace data, and credentials stay exactly as stored in Jira or your organization. Switching language only affects how Flow Analyzer presents the product around that data.

If the control is missing, your deployment may be on an older build; ask your administrator to upgrade. Operators: see Web UI localization.

Who you are in the product (v1)

v1 role model: every person in a company is an organization administrator (org_admin). There is no separate “analyst” seat with reduced powers yet.

People and invitations

Who this is for: anyone adding teammates to the same organization.

Where to find it: open [Organization and workspaces](/org-settings) and scroll to People & invitations.

What you can do there: see Members already in the company, Pending invitations, and how many seats are in use. Enter an email and choose Send invitation. The app shows a one-time token once on your screen—copy it and share it through a channel you trust (the app does not email the token for you unless operators add separate email delivery). The person you invited should create an account or sign in with that exact email, then open [Accept invitation](/accept-invite), paste the token, and confirm. If the token expires, use Resend on the pending row to get a new one. Revoke cancels a pending invite so the old token no longer works.

Why it matters: seats are enforced when someone accepts an invite; pending rows do not consume a seat until then. Separately, copy and support should not promise “private” Jira tokens per person — see Shared Jira.

Shared Jira within your organization

When your org connects Atlassian Jira Cloud or Jira Data Center, the connection is stored once under the company. All members of that company can use workspaces that point at that connection.

• No duplicate credentials per user — access is “member of company that owns the connection,” not a personal PAT copy.
• Onboarding: anyone who can sign in to the org should understand that adding or rotating Jira credentials affects everyone.
• Leaving the company: removing membership removes access to all workspaces and connections for that org in one step.

Full policy: Org-wide Jira sharing. Data shape: SaaS data model.

Workspace selector and your data

The sidebar workspace selector (below the FlowAnalyzer title) chooses the active workspace for your session. That tells the app which snapshot and config to load for dashboards, findings, exports, and analysis runs.

Workspaces catalog: open Workspaces from the sidebar (directly under Home) or choose Workspaces at the bottom of the workspace selector dropdown. This opens [Workspaces](/flow-analyzer/workspaces)—a catalog of every workspace in your organization, grouped by type (live Jira, live ClickUp, live Asana, live Linear, live Trello, demo, import). Use search and filters to find a workspace, open it as your active session, or use the settings icon on a card for details, archive, delete, and import. Add new workspaces from the placeholder card in each group.

Organization settings: for source connections (Jira, ClickUp, Asana, Linear, and Trello), people and invitations, and the full workspaces table, open [Organization and workspaces](/org-settings) (linked from the Workspaces page footer hint and from org administration flows). The License & billing panel shows your plan tier, usage against freemium caps, and Stripe checkout when enabled. Locked sidebar items and in-app Upgrade prompts explain which tier unlocks each capability. You may be prompted for a short product satisfaction survey after key milestones; use Support APIs from in-app flows to message platform operators when your deployment enables them.

When you hit a freemium cap or open a Coach-only screen on Freemium, use the upgrade sheet or Organization settings → License & billing to start checkout or contact sales.

Assist — Coach engagements (audit lifecycle)

Who: external consultants and delivery auditors on a Coach plan (especially a 28-day engagement pass).

Why: each client audit used to feel like a generic workspace. Engagements add a lifecycle (setup → analysis → readout → hand-off → archived), multi-client switching without re-running Focus Wizard from scratch, white-label HTML export branding, and an enterprise hand-off invite for the client admin.

Where: open Workspaces — the Client engagements hub sits above the catalog. Use New engagement to create a shell (name, client label, analysis window), then complete the G7 delivery-audit Focus Wizard. The workspace switcher shows engagement status badges; on an active engagement workspace the lifecycle stepper, Advance control, and days remaining appear under the switcher. Configure logo / firm name / disclaimer under Organization settings → Organization → Report branding. Start Enterprise hand-off from the hub when the engagement is in readout or hand-off; the consultant workspace becomes read-only (analysis and config writes are blocked) and the client receives a register invite with a clear Enterprise next step.

Archive pack: when readout or hand-off is done, create an immutable stamped HTML/JSON pack from the hub or lifecycle chrome so the client deliverable cannot drift after later re-runs — see Assist — Consultant engagement archive pack.

Assist — Consultant engagement archive pack

Who: external consultants and delivery auditors on a Coach plan with findings report export (especially after a client readout or hand-off).

Why: after the audit meeting, re-running analysis or changing branding used to change what you could reprint. An archive pack freezes stamped HTML and JSON for that engagement so the client packet stays durable and auditable.

Where: open Workspaces → Client engagements. On rows in readout, hand-off, or archived (legacy without a pack), choose Create archive pack…, confirm the dialog, then use Download pack / Download HTML / Download JSON. On an active engagement workspace, the lifecycle chrome shows the same Archive pack card when status is readout, hand-off, or archived.

How it works: create builds the entitled findings export once, stamps engagement id, archive time, analysis run / snapshot identifiers, and a content hash, stores an immutable workspace artifact, advances status to Archived (if needed), and keeps the workspace read-only. Creating again does not overwrite the pack. Freemium orgs without Coach export stay on the usual upgrade gate.

Assist — Integrity-adjusted P50/P85 on Initiative PM (#148)

Who: Initiative sponsors, PMO, and tribe leads who plan from P50/P85 finish dates.

Why: Reported throughput can include completions flagged by forensics (Truth Gap). Planning on that velocity alone can understate finish risk.

What it solves: On Initiative PM, when the Truth Gap is material (about 10% or more of reported throughput flagged) and forecast history exists, P50 and P85 cards show Reported and Adjusted (estimate) columns side by side. Adjusted dates use the same Monte Carlo engine on completions with forensically implicated items removed. A short banner links to Truth Gap. Throughput can show both reported and adjusted stories/week. When the gap is small, you still see the familiar single reported forecast — no layout change.

Where: Initiative PM forecast strip; matching P85 shift line on Brief risk when the same threshold is met; optional bullet on the HTML executive summary.

How to read it: Treat adjusted dates as estimates (K-D2). A flagged closure may still be real work — use Truth Gap for the forensic detail, not person-level blame.

Freemium onboarding — haunted seed diagnostic

Who: New freemium organizations evaluating Flow Analyzer without a consultant in the room (tribe leads and Scrum Masters).

Why: Empty org settings delay the aha moment. The haunted seed path lands you on named findings in minutes.

What it solves: You see a real delivery diagnosis on safe demo data before connecting Jira.

How: After first sign-in with no workspaces, Organization settings shows a recommended card — See a real delivery diagnosis — safe demo data. One click creates a Demo workspace (seed connector, volume caps exempt, demo watermark). Analysis boots automatically so Start here (Brief) can show top findings with rule citations (RULEID: RULETITLE). Focus Wizard opens on first /flow-analyzer visit — prefer Ship faster and Trust our metrics; skip to Advanced if you want the full catalogue view without Guided filters. On freemium, Brief shows a Truth Gap teaser (gap % + one evidence row + upgrade to Coach); the full Truth Gap workbook unlocks on Coach.

Where: Organization and workspaces (empty org) → Open diagnostic workspace → Brief / Start here.

Organization switcher (12.21): if you belong to more than one company, sign-in asks you to choose your organization before you enter the app; your active organization is always shown in the account menu on your avatar (switch there anytime). Switching org reloads the workspace list for that company so you never mix tenants.

When SaaS mode is on and you are signed in, demo vs live follows the workspace you select. The older in-app Switch data source cookie control is not available in that mode so tenant data cannot be mixed with a browser-wide override.

If you open or script raw API URLs (for example bookmarking `/api/export?…` or calling `/api/analysis/jobs` from curl with your browser session cookies), append `&workspaceId=<id>` for the same workspace the header selector shows; the server rejects mismatched or missing ids so data never crosses workspaces. In-app pages add this for you. Automation without a browser session uses the headless bearer contract in headless-analyze-api.md.

When SaaS is off, operators may still use environment variables plus optional cookie source switching; see Operator runbook.

Freshness for live Jira (webhooks and backup poll)

For live workspaces, your deployment can receive push updates from Jira using a webhook (HTTPS URL scoped to the workspace, plus a signing secret Jira includes on each delivery). You can store that secret per Jira connection when you add or edit the connection in Organization settings, or rely on a single secret configured on the server by your operators. When webhooks are configured correctly, issue changes can reach Flow Analyzer quickly.

Your operators also run a scheduled check (at least about once an hour) as a safety net if a webhook delivery fails or is misconfigured. That job is invisible in the product UI in early slices; it shows up in operator logs and job history like other background work. On Organization settings, the Jira connections table shows Last webhook so you can confirm Jira is reaching the app.

Details for setup: Jira webhooks and data freshness and Operator runbook.

Jira Data Center note: webhooks are most reliable when Flow Analyzer runs on-prem beside your Jira server. If you use hosted Flow Analyzer and Jira sits on a private network, expect scheduled polling as the primary freshness path unless your network team exposes Jira to Flow Analyzer's egress IPs.

Connect Jira Data Center (live workspaces)

Who this is for: analysts and org admins whose organization runs self-hosted Jira (Data Center 9.12+ recommended; 8.14+ supported in best-effort mode).

Why: You get the same Brief, findings, configuration wizard, and rule catalogue as Jira Cloud customers — without migrating to Atlassian Cloud.

Where to find it:

1. [Organization and workspaces](/org-settings) → Source connections → Add connection → Jira Data Center.
2. Create a `jira_live` workspace from [Workspaces](/flow-analyzer/workspaces) and link the DC connection (same workspace type as Cloud-backed Jira).
3. Set project scope or JQL, then open Configuration and Configure from source for issue types and workflow mapping.

What you enter:

• Base URL — the full URL your team uses in the browser, including a context path when Jira is not at the site root (for example https://jira.internal.company/jira).
• Personal Access Token (recommended) — created in Jira for a service account; no password leaves your control path when you use a PAT.
• Basic auth — available with a clear discouraged warning; use only when PATs are not an option.

When validation fails: if Flow Analyzer cannot reach your server, the error explains reachability options (run Flow Analyzer on-prem on your LAN, expose Jira to Flow Analyzer egress IPs for SaaS, or a private link arranged with your vendor). This is expected for firewalled Jira — it is not a bug in your PAT. Your platform administrator handles network and TLS; you handle the connection form. Org admins can also open Organization and workspaces → Enterprise readiness for the full DC + SSO + topology checklist, and share the enterprise procurement pack with security.

Shared credentials: like Cloud, one DC connection per organization is shared by every member who can open workspaces that use it.

Connect ClickUp (live workspaces)

Who this is for: delivery leads and org admins who run delivery in ClickUp and want the same flow-health analysis, findings, and Resource Sankey views as Jira-backed workspaces—without exporting CSVs or building ad hoc reports.

Why: ClickUp holds tasks, status history, time entries, and sprint-style lists. Flow Analyzer normalizes that data into the shared rule engine so you can spot bottlenecks, allocation risk, and discipline gaps in one place.

Where to find it:

1. Organization settings (/org-settings) → Source connections → add a ClickUp connection (OAuth or personal API token).
2. Connect ClickUp wizard (/flow-analyzer/connect-clickup) — pick the connection, choose Team → Space → Folder → List scope, confirm status categories, confirm which lists are sprint iterations, preview rule coverage, then create a `clickup_live` workspace.

How it works:

• Scope: you select lists in the hierarchy tree; only tasks in those lists are ingested.
• Status mapping: ClickUp status types (open, custom, done, closed) are auto-mapped to todo / in progress / done; adjust per list in the wizard if needed.
• Sprints: lists whose folder name looks like a sprint or that have start/due dates are candidates; only lists you confirm in the wizard count as iterations for sprint-dependent rules.
• Freshness: ClickUp webhooks mark changed tasks dirty; the app re-fetches task data via the API (webhook bodies are not trusted as the snapshot). A scheduled poll runs as a safety net (same operator cron as Jira live workspaces).
• After connect: open the new workspace from Workspaces, run analysis from the dashboard, and open Resource Sankey when time entries are present.

Shared credentials: like Jira, a ClickUp connection is stored once per organization and shared by all members who can access workspaces using that connection.

Connect Asana (live workspaces)

Who this is for: delivery leads and org admins who run delivery in Asana and want the same flow-health analysis, findings, and coaching views as Jira- or ClickUp-backed workspaces.

Why: Asana holds tasks, section moves, dependencies, and optional custom fields. Flow Analyzer derives status history and normalizes tasks into the shared rule engine.

Where to find it:

1. Organization settings (/org-settings) → Source connections → add an Asana connection (OAuth or personal access token).
2. Connect Asana wizard (/flow-analyzer/connect-asana) — pick the connection, select projects, choose section or enum-field status mode, map section categories, preview rule coverage, then create an `asana_live` workspace.

How it works:

• Scope: only tasks in projects you select are ingested.
• Status mode: board sections (default) derive transitions from column moves; status custom field mode uses a designated enum field (map options in workspace configuration after connect).
• Freshness: Asana webhooks mark changed tasks dirty; the app re-fetches via the API after handshake and signature verification.
• After connect: open the workspace from Workspaces, run analysis, and review findings like any live source.

Shared credentials: one Asana connection per organization, shared by all members with access to workspaces that use it.

Connect Linear (live workspaces)

Who this is for: delivery leads and org admins who run delivery in Linear and want the same flow-health analysis, findings, and coaching views as Jira-, ClickUp-, or Asana-backed workspaces.

Why: Linear tracks issues, workflow states, and state transitions. Flow Analyzer derives status history from issue history and normalizes issues into the shared rule engine.

Where to find it:

1. Organization settings (/org-settings) → Source connections → add a Linear connection (OAuth or personal API key).
2. Connect Linear wizard (/flow-analyzer/connect-linear) — pick the connection, select teams and optional projects, map workflow states to analysis categories, preview rule coverage, then create a `linear_live` workspace.

How it works:

• Scope: issues in the teams (and projects, if narrowed) you select are ingested.
• Status mode: workflow states map to to-do / in-progress / done categories; transitions come from Linear issue history.
• Freshness: Linear webhooks mark changed issues dirty; the app re-fetches via the GraphQL API after signature verification. A scheduled poll runs as a safety net (same operator cron as Jira/ClickUp live workspaces).
• After connect: open the workspace from Workspaces, run analysis, and review findings like any live source.

Shared credentials: one Linear connection per organization, shared by all members with access to workspaces that use it.

Connect Trello (live workspaces)

Who this is for: delivery leads and org admins who coordinate work on Trello boards and want flow-health analysis on cards and list moves.

Why: Trello tracks cards on boards and lists. Flow Analyzer treats each list as a workflow column and derives status history from card actions (especially moves between lists).

Where to find it:

1. Organization settings (/org-settings) → Source connections → add a Trello connection (API token).
2. Connect Trello wizard (/flow-analyzer/connect-trello) — pick the connection, select boards, map lists to to-do / in-progress / done categories, preview rule coverage, then create a `trello_live` workspace.

How it works:

• Scope: only cards on boards you select are ingested.
• Status: list name and your category map drive workflow status; moving a card between lists creates transition history.
• Freshness: Trello webhooks notify the app when cards change; ingest re-fetches affected cards. A scheduled poll runs as a safety net (same operator cron as Jira/ClickUp).
• Operator note: your platform admin must set `TRELLO_API_KEY` on the deployment before connections can validate.

Connect ScrumDesk Start (live workspaces)

Who this is for: delivery leads and org admins who run delivery in ScrumDesk Start (cloud) and want flow-health analysis on backlog items.

Why: ScrumDesk exposes backlog items, workflow steps, native status history, worklogs, and sprint metadata over the cloud REST API. Flow Analyzer maps workflow steps to analysis categories and ingests project-scoped backlog items.

Where to find it:

1. Organization settings (/org-settings) → Source connections → add a ScrumDesk connection (integration or personal API token).
2. Connect ScrumDesk wizard (/flow-analyzer/connect-scrumdesk) — pick the connection, select projects, map workflow steps to to-do / in-progress / done categories, preview rule coverage, then create a `scrumdesk_live` workspace.

How it works:

• Scope: only backlog items in projects you select are ingested.
• Status: workflow step and your category map drive workflow status; native history_changes supply transition history.
• Freshness: a scheduled poll (same operator cron as other live connectors) is the primary freshness path until outbound webhooks are available from ScrumDesk cloud.
• Note: this connector targets ScrumDesk Start cloud only (api.scrumdesk.com), not the legacy Windows OData API. Request integration tokens from support@scrumdesk.com when needed.

Results report and scheduled delivery

• One-off download: open Results report from the sidebar Overview section for JSON (dashboard + charts) or Markdown (summary and sample findings), scoped to the active workspace when SaaS is on. The HTML report includes an executive summary, Reporting gap (when applicable), Flow focus items (ranked work items with the highest cycle/lead-time impact), Priority matrix (Eisenhower quadrants for findings with linked Jira issues — same ranking as the Priority matrix screen), key metrics, charts (including control chart with rolling average and UCL/LCL), a Hierarchy table, and a Recommendations section with this week’s constraint focus and all ceremony pack types (tribe sync, retro, PI prep, leadership briefing)—the same content as Recommendations in the sidebar. In Hierarchy, Flow quality is the same 0–100 Flow quality index (Index kvality toku) as issue detail; Problem rank is the worst-first order of that score among rows with delivery problems. Default sort is hierarchy order — the legend under the table says so. JSON export includes the same priority matrix items when findings have linked issues. On the HTML preview toolbar, use Share to send the formatted HTML report to a single email address (requires SMTP on the deployment — same settings as scheduled report email).
• Scheduled summaries: on the same Results report page, add and manage schedules (webhook or email) for the active workspace. Each schedule uses Markdown or JSON for the optional signed full export link in the message (PDF is not offered for schedules until PDF export exists in the product). Set Digest mode to Weekly delta (import compare) when you want a short Slack or email summary of what changed between the two newest import snapshots instead of the full dashboard summary. On Enterprise, choose Integrity-only executive digest for a PMO trust readout (portfolio trust index and tribe MI/OL lines) without the usual dashboard KPI block. Pick a timezone so daily/weekly/monthly runs follow local calendar boundaries (not a fixed hour count). Use Refresh to reload the list (for example after a cron run). Webhook runs post a short HTTPS message (Slack-compatible). Email schedules send a plain-text summary when the deployment has SMTP configured (see Automated report delivery); recipients are comma-separated addresses. Operators still enable the secured cron runner (same doc, runbook). Test send on a schedule row checks the webhook or email destination once without updating last run. Send code delivers a short-lived verification code only to that destination; enter it next to the row and choose Confirm so the Ownership column shows verified. If your operators enable strict mode for automated delivery, scheduled runs wait until ownership is verified for each schedule. You can type any valid IANA zone; the field suggests common regions.
• Scheduled summaries: on the same Results report page, add and manage schedules (webhook or email) for the active workspace. Each schedule uses Markdown or JSON for the optional signed full export link in the message (PDF is not offered for schedules until PDF export exists in the product). Set Digest mode to Weekly delta (import compare) when you want a short Slack or email summary of what changed between the two newest import snapshots instead of the full dashboard summary. Set Digest mode to Ceremony ritual (pack excerpt) and pick a Ritual template (Weekly constraint, PI planning prep, or Quarterly integrity review) when you want recurring ceremony bullets with a deep link to the in-app pack — not the standard dashboard KPI block. Pick a timezone so daily/weekly/monthly runs follow local calendar boundaries (not a fixed hour count). Use Refresh to reload the list (for example after a cron run). Webhook runs post a short HTTPS message (Slack-compatible). Email schedules send a plain-text summary when the deployment has SMTP configured (see Automated report delivery); recipients are comma-separated addresses. Operators still enable the cron; Enterprise plans include scheduled digests (Coach keeps manual export only).

secured cron runner (same doc, runbook). Test send on a schedule row checks the webhook or email destination once without updating last run. Send code delivers a short-lived verification code only to that destination; enter it next to the row and choose Confirm so the Ownership column shows verified. If your operators enable strict mode for automated delivery, scheduled runs wait until ownership is verified for each schedule. You can type any valid IANA zone; the field suggests common regions.

• Scheduled summaries: on the same Results report page, add and manage schedules (webhook or email) for the active workspace. Each schedule uses Markdown or JSON for the optional signed full export link in the message (PDF is not offered for schedules until PDF export exists in the product). Set Digest mode to Weekly delta (import compare) when you want a short Slack or email summary of what changed between the two newest import snapshots instead of the full dashboard summary. Set Digest mode to Ceremony ritual (pack excerpt) and pick a Ritual template (Weekly constraint, PI planning prep, or Quarterly integrity review) when you want recurring ceremony bullets with a deep link to the in-app pack — not the standard dashboard KPI block. Pick a timezone so daily/weekly/monthly runs follow local calendar boundaries (not a fixed hour count). Use Refresh to reload the list (for example after a cron run). Webhook runs post a short HTTPS message (Slack-compatible). Email schedules send a plain-text summary when the deployment has SMTP configured (see Automated report delivery); recipients are comma-separated addresses. Operators still enable the secured cron runner (same doc, runbook). Enterprise plans include scheduled digests including ceremony rituals (Coach keeps manual export and in-app packs only). Test send on a schedule row checks the webhook or email destination once without updating last run. Send code delivers a short-lived verification code only to that destination; enter it next to the row and choose Confirm so the Ownership column shows verified. If your operators enable strict mode for automated delivery, scheduled runs wait until ownership is verified for each schedule. You can type any valid IANA zone; the field suggests common regions.

Resource Sankey and investigation export

Open Resource Sankey from the sidebar (/flow-analyzer/resources) to see how people connect to epics and components in the active workspace, with precious resource scores and bottleneck hints on the chart.

• Findings: when the workspace has a roster (config.org) and a snapshot, ORG- org-capacity rules run with the rest of analysis and appear on Findings (over-allocation, undeclared sharing, squad/PI overcommit, hours vs FTE, discovered or inactive people, and related signals). Field mapping uses workspace config (team field, PI field, story points)—not a single customer’s custom field ids.
• Investigation panel: below the chart on Resource Sankey, browse Issues, People, and Flows tabs (sortable tables). Click an issue key to open the issue detail panel. Download CSV is on the same panel when you need a spreadsheet export.
• Discipline investigation: on the same screen, below the resource investigation panel, review Gate bypass, Coverage, Epic DoD, PI delivery, Operational buckets, Multi-project, and Lean waste tabs. Each tab opens with a short explanation of what it checks: Gate bypass lists issues that jumped statuses while skipping mandatory workflow stages; Coverage shows covered-by requirement links and flags gaps when a requirement is Done but covering work is still open; Epic DoD is a heatmap of checklist completion per epic by DoD stage; PI delivery compares committed versus delivered story points by Program Increment; Operational buckets lists catch-all operational trackers with child heap and growth metrics; Multi-project groups portfolio checks when a parent initiative spans delivery projects—cross-project gate bypass by parent and delivery project, cross-project blocker aging and blocker chain integrity (including late links), parent–child coherence when a parent initiative regresses while delivery children stay active, DoD evidence gaps for checked checklist items without supporting body text, PI label stack on active parents, description versus decomposition gaps, clone continuation pairs, clone PI rollover without scope change, and remote link churn without integrated content updates; Lean waste groups snapshot signals into coaching lenses (waiting, task switching, partially done work, extra processes, motion, extra features, defects) with related rule ids and sample issue keys, and lets you narrow samples to parent initiatives or delivery work. Matching issue keys are outlined on the Sankey chart (stage skips, coverage gaps, weak DoD stages, and multi-project portfolio risk). The same investigation panel is also available under Discipline → Investigation and as a collapsible section on Findings.

Seed-demo workspaces may show the chart layout without RA findings until the snapshot includes worklog history (live Jira or a Jira export import with worklog data).

Org structure (roster, FTE, sharing)

Open Org structure under Advanced analytics → Portfolio (/flow-analyzer/org-structure).

• Who it is for: delivery auditors, tribe leads, and consultants who need to see who belongs where, how capacity is allocated, and who is genuinely shared versus only incidentally assigned across teams.
• Why it exists: roster and FTE already live in workspace configuration, but without a dedicated auditor screen they stay hidden. This screen turns that roster into a chart, tree, and filterable table grounded in your imported or live snapshot—never invented demo people.
• What you see: Tribe → Squad → people as an org chart (default) or expandable tree; a people table (name, employment, role, FTE, primary squad, account, sharing, active); auditor filter chips (Shared only, Outside primary team, Overloaded, Underloaded, Discovered only, and more) that stay in sync with the chart and can be shared via the page URL. Hover a chip for what it includes — several chips combine (a person must match all of them). Import from snapshot when the roster is empty (one-shot structure bootstrap). Sync from Jira Teams refreshes squad membership from Atlassian Teams (or Tempo when configured): review adds / removes / moves / conflicts, resolve multi-team people by picking a primary squad, then apply — FTE, sharing, roles, and employment on existing people stay the same unless you include a soft-remove. Optional scheduled sync only fetches a pending draft onto the status strip; it never auto-applies.
• Person side sheet: edit role, employment (internal, vendor, contractor, intern, or other), FTE allocations, sharing scope (squad / tribe / organization), and active flag; review tasks, flow metrics (WIP, cycle/lead time), and linked findings/patterns. Inactive people remain visible (faded) but drop out of capacity totals. Removing a person, squad, or tribe asks for confirmation first.
• Privacy & workforce data: On first visit, org admins choose how people are shown — real names, generated codes, or structure only (tribes/squads/FTE without importing legal names). Storing real names requires an org-admin authority acknowledgment (not per-employee consent). Your organization remains the data controller for roster and workforce data; Flow Analyzer is the processor under your contract. Inform affected staff per your own employment and privacy policies. See Privacy Policy and the operator GDPR workforce plan.
• Example: An architect shows as dedicated to one squad but most active work sits in another tribe—use Outside primary team (not shared) to surface the mismatch and decide whether to formalize sharing or rebalance assignments. Matching ORG- findings also appear on Findings after a rules run.
• Squad sprint capacity: set Sprint capacity (SP) on each squad row. This feeds DV-12 overcommit checks, the Initiative PM → Takt vs delivery rate roster capacity band, and DV-16 staleness when velocity shifts without a roster refresh.
• Epic tribe field (live Jira): configure under Organization and workspaces → workspace details → Jira project → organization units so live ingest stamps _flowAnalyzerEpicMeta.tribe on Epic issues — required for tribe run filters and cross-tribe comparison outside seed mode. See org capacity product doc.
• Capacity change history: each roster save is versioned in workspace configuration. Analysis runs diff squad SP and FTE allocations between saves to drive CFD-10 and DV-16 — you do not need to bump effective_from alone when you change capacity figures.
• Capacity truth panel: when the roster and snapshot both exist, Org structure shows a tribe-level table comparing committed FTE (roster) with actual worklog hours over a 14-day window, observed load %, gap FTE, shared-people count, and a precious-at-risk count joined from Resource Sankey / RA-10 signals — process-level evidence for PMO readouts, not individual performance scores. Open Resource flow (Sankey) from each tribe row (or Org capacity truth from the Sankey toolbar) when justifying hiring or redistribution to sponsors.

Dashboard — Cross-tribe comparison and root cause hypotheses

Open Dashboard (/flow-analyzer/dashboard) when the snapshot contains two or more tribes.

• Who it is for: executives, tribe leads, and PMO comparing delivery health across value streams on one screen (FR-10).
• Cross-tribe table: sortable columns for open issues, WIP vs limit, average cycle time, and critical findings. When Org structure roster is configured, additional columns show configured FTE, observed load %, shared people, and suggested FTE Δ (allocation advisor preview). On Org structure → People, use Apply allocation advisor to write selected FTE / sharing-scope changes to the roster (with confirmation).
• Root cause hypotheses (FR-11): when at least two findings correlate, a block groups them by shared issue, shared rule family, or shared roster person (shared_person for ORG / RA findings on the same person). Each group links to Findings or Root cause causal loop map for deeper exploration.
• Ceremony packs: leadership and PI prep exports include cross-tribe org-capacity bullets when roster data exists.
• Multi-initiative workspaces: when the snapshot lists two or more initiatives and you are not narrowing the portfolio read scope to one tribe/team/sprint slice, the cross-tribe table rolls up open WIP, cycle time, and critical findings across all initiatives. Org-capacity columns (FTE, observed load, shared people, suggested FTE Δ) still come from the workspace roster once — not summed per initiative.

Product reference: `cross-tribe-and-root-cause-fr-10-fr-11.md`, `org-capacity-and-shared-resources.md`.

Map

Open Map from the sidebar (/flow-analyzer/landscape) to see how backlog and findings are distributed across hierarchy, tribes, assignees, components, and rule dimensions.

• Who it is for: tribe leads, Scrum Masters, and delivery managers who want a fast visual read on where scope and rule pressure concentrate before a refinement or portfolio review.
• Views: choose a Backlog layout (initiative hierarchy, tribes, assignees, components, issue types, PI) or a Findings / hybrid layout after a rules run.
• Controls: filter by tribe when your snapshot carries tribal labels; set tile size to issue count, story points, or finding weight; set color to status, severity, rule family, and other attributes.
• Interaction: click a group tile to drill down (breadcrumbs show where you are); click a leaf tile to open the issue detail panel. The side legend and breakdown table summarize the selected level.

Findings views show a clear empty state when no rules run exists yet for the workspace.

Simulation board (findings-grounded what-if)

Open Simulation board at `/flow-analyzer/simulation` (deep link from Findings or root-cause workflows with ?initiativeId=).

From the initiative dashboard: PMO viewers, Scrum Masters, and coaches who already trust the P50 and P85 dates can start a what-if without hunting the sidebar — on Coach+ workspaces, each of those forecast cards shows Model improvement, which opens Simulation for the selected initiative (levers empty so you choose). The dashboard dates stay the canonical Monte Carlo forecast; Simulation remains an illustrative counterfactual and does not replace the strip.

• Who it is for: Scrum Masters and tribe leads running retro or refinement who want to test “what if we fix WD-01 / WIP / quality escapes?” before changing process.
• Prerequisites: a persisted workspace snapshot with stage residence and weekly throughput samples, plus active findings that unlock levers (for example WD-01: Missing acceptance criteria → DoR AC coverage slider with base derived from missing_ac_issue_count / open_issue_count).
• Levers: up to three sliders generated from findings — not free-form constants. Disabled levers show an explicit reason when snapshot data is insufficient (no fabricated numbers).
• Live simulate: drag a slider and metrics recompute within ~200 ms (debounced); in-flight runs cancel. Reset all levers returns bases and the scenario column matches baseline.
• Metrics panel: sortable table with Baseline vs Scenario for cycle time P50/P85, throughput, waiting share, WIP, suppressed finding count, and optional scenario finish weeks when open scope and throughput history exist. Dashboard forecast (canonical P50/P85) is labeled separately — scenario output is an illustrative counterfactual and does not overwrite the initiative dashboard strip.
• Out of scope: no write-back to Jira, ClickUp, or other trackers; no replacement of the main Monte Carlo forecast engine.

Assist — Simulation levers (expanded catalogue)

Who it is for: Agile coaches (PER-P2), Scrum Masters (PER-P4), and PMO sponsors (PER-P9) who open Findings for RA / CFD / capacity signals and want a quantified what-if — not only WD-01 or tribe WIP.

Why it exists: Simulation used to feel empty outside AC coverage and tribe WIP. The expanded catalogue maps person WIP, FTE shifts, sharing scope, roster activation, and stage-policy bottlenecks so workshops can quantify the same findings they already trust.

What problem it solves: From Findings, mapped rules show Simulate fix (deep-links Simulation with that lever focused). Unmapped families (text quality, governance, estimation, and similar) show a Coaching only badge — never a silent empty action. On Simulation, up to three eligible levers appear; missing roster or waiting-split data disables a lever with an explicit reason (no invented baselines).

Where in the UI: Findings list → Simulate fix / Coaching only → `/flow-analyzer/simulation`. Lever kinds include person WIP, FTE reallocation (within max shift), sharing scope, roster activation, and stage policy (queue removal or parallel with a handoff cost).

How it works: Prefer org-configured baselines (person_wip_limit, FTE allocations, tribe WIP) when present; otherwise refuse with a reason. Slide ≤3 levers; compare Baseline vs Scenario. Apply to org structure and Track as experiment remain separate actions.

Product reference: `findings-grounded-what-if-simulation.md` §4.2 · `flow-optimizer-scenarios.md`.

Assist — Forecast band verify (predicted vs actual P50/P85)

For whom: Scrum Masters (PER-P4), agile coaches (PER-P2), and PMO sponsors (PER-P9) who tracked a Simulation experiment.

Why: After verify, leadership needs to know whether the dashboard Monte Carlo landed inside the committed prediction band — not only whether rule hit counts moved.

Where: /flow-analyzer/actions — Done cards show a Forecast verify row; Action detail → Verification shows the band chart and verdict (Inside band / Missed band / Forecast pending).

How: Track as experiment in Simulation (#166) → wait for the verify window → open Actions. When throughput history is thin, the verdict stays Forecast pending with an explicit reason (no invented green band). If OL-04: False Improvement Pattern (or CC-05) fired on the verify window, Forecast verify is annotated so an “inside band” result is never unqualified green.

Assist — Simulation experiments (Track as experiment)

Who it is for: Scrum Masters, agile coaches, and PMO sponsors who want a falsifiable forecast experiment after exploring levers on the Simulation board.

Why it exists: Simulation shows baseline vs scenario P50/P85, but workshops often stop at “interesting what-if.” Tracking stores a committed prediction snapshot so the team can later verify whether delivery moved toward the predicted band.

Where in the UI: Open Simulation (/flow-analyzer/simulation), adjust at least one eligible lever, wait for simulate to succeed, then click Track as experiment. After confirm, open the new card under Improvement actions and review Predicted outcome.

How it works: Confirm creates one Improvement action with the scenario as hypothesisId, suppressed finding refs, playbook-derived steps, baseline run id, and a structured prediction (cycle/throughput/finish weeks when present, lever values). Cancel writes nothing. Confirm does not enqueue analysis and does not apply organization config. Scenario results remain illustrative — they do not replace the dashboard Monte Carlo strip. Later band verify is a separate step (#168).

Flow improvement loop (compare, triage, coaching)

Use these when you are analyzing a delivery portfolio (especially after a Jira export import) and need to turn findings into sustained change:

Findings — noise reduction (dismiss with reason, confidence, narrative groups)

Assist — Durable finding triage and improvement actions on SaaS (#197)

Who it is for: Coaches and Scrum Masters who triage Findings and track Improvement actions on hosted SaaS.

Why it exists: On multi-instance or restart-prone hosts, file-only triage could drift or disappear between runs. SaaS now keeps triage (and action extras such as experiment predictions) in the same durable tenant database pattern as Evaluation notes.

What problem it solves: When you dismiss or acknowledge a finding, or create an improvement action, those choices stay with your workspace across app restarts. There is no new screen — use Findings triage controls and the Actions hub as today.

Where in the UI: Findings (triage / dismiss) · Improvement actions (header) · Brief noise filters that respect triage.

Who it is for: Analysts and coaches triaging a large findings list who need to hide known-noise findings without losing the audit trail, and want a quick read on which findings are most trustworthy.

Why it exists: Not every finding needs action — some are accepted risk, data-quality artifacts, or duplicates of another rule hit. Marking them Won't fix without a reason makes it hard to tell "reviewed and dismissed" from "never looked at." A single confidence signal (severity, evidence completeness, and stability across analysis runs — never people's names) also helps you decide what to act on first.

What it solves and how:

• Dismiss with reason — on a finding's triage controls, use Dismiss to open a dialog and pick a reason (not applicable, accepted risk, data quality, already resolved, duplicate, or other) plus an optional note (up to 280 characters). This sets status to Won't fix with an auditable reason instead of a bare status change.
• Confidence pill — each finding shows a High / Medium / Low confidence pill; hover for the contributing factors (severity, how much evidence is recorded, and whether the finding is stable across runs).
• Show suppressed / Regressed filters — dismissed (Won't fix) findings are hidden by default so the list stays focused on open work. Use Show suppressed in the Findings toolbar to bring them back, or Show regressed only to see findings that were dismissed or resolved before but reappeared with materially different evidence (shown with a Regressed badge and a link to compare snapshots).
• Related findings — findings that share the same rule and issue are collapsed into one card with a +N related badge; expand to see the grouped items without duplicating triage controls on each one.
• Narrative groups — switch the Findings List / Narrative groups tab to see findings clustered into short, correlated stories (same issue, same person, or the same rule family firing at high severity), each citing the rules involved and linking to the filtered list or the root-cause map. The Brief screen's Root-cause narrative card shows the top 1–3 groups for a quick read.
• Suppression audit — expand Suppression audit at the bottom of the Findings page for a sortable table of active dismissals and snoozed rules, each with Undo to bring the finding or rule back into the active queue.
• Exports — Markdown and JSON exports omit dismissed findings by default; check Include suppressed findings to append them as a separate section instead of mixing them into the main report.

Where in the UI: Findings (/flow-analyzer/findings) — toolbar filters, the finding row's Dismiss button, and the Suppression audit panel. Brief (/flow-analyzer) — Root-cause narrative card.

Assist — Findings FR-02 scope filters (tribe, team, label, issue type)

Who it is for: Scrum Masters, agile coaches, and PMO reviewers who triage Findings and then re-run analysis for the same slice of work.

Why: You should be able to narrow Findings by the same tribe, team, label, and issue type dimensions you use on Run analysis, then open Run with those values already filled — so the list you review matches the scope of the next run.

What problem it solves: Previously, Findings mostly filtered by search, severity, and rule family. Tribe could quietly ride the URL into Run analysis while team, labels, and issue types stayed empty, so coaches sometimes analyzed a wider set than the list implied.

How it works:

• On Findings, the filter bar includes Tribe, Team, Label, and Issue type (comma-separated labels match any label; all four dimensions combine with AND).
• Click Apply to update the URL so you can refresh or share the filtered view. Active filter chips clear one dimension at a time.
• Portfolio header tribe/team (when set) still narrows the workspace first; Findings FR-02 filters refine the list further and drive Run prefill.
• When no FR-02 page filters are set, the list behaves as before (portfolio read scope + severity/family/search). Run analysis scope fields start empty unless tribe/team are already in the URL from the portfolio header.
• Opening Run analysis from Findings pre-fills tribe, team, labels, and issue types from the current Findings filters.

Where in the UI: Findings (/flow-analyzer/findings) — second filter row, active chips, and the Run analysis sheet.

Assist — Findings list virtualization and bulk triage

Who it is for: Scrum Masters, agile coaches, and consultants who triage large Findings lists in workshops or audit readouts.

Why: After a large seed or live run, hundreds of findings can make the list laggy and force one-row-at-a-time dismissals. You need a responsive list and a way to clear noise, package a selection into an improvement action, or export only what you selected.

What problem it solves: The list tab used to mount every finding row in the DOM and offered no multi-select path, so noise control stayed slow at scale.

How it works:

• On Findings → List, large filtered catalogues use a virtualized window so only nearby rows stay in the DOM while you scroll.
• Checkboxes select rows. The sticky bulk bar shows the selection count. Dismiss…, Link to improvement action…, and Export selection stay disabled until at least one row is selected.
• Select all matching filters selects up to 500 matching rows and tells you clearly when the selection was capped — narrow filters if you need a different slice.
• Dismiss… opens a confirmation dialog with a shared reason and optional note. Confirmed rows become Won't fix with that reason (same behaviour as single-row dismiss). Suppressed rows stay hidden unless you turn on Show suppressed.
• Selecting a collapsed primary also includes its related siblings when you dismiss.
• Link to improvement action… creates a new open action from the selection or adds the finding refs to an existing open action, then offers a deep link to Actions.
• Export selection downloads Markdown, JSON, or CSV with only the selected findings (id, rule, severity, issue keys, triage) — not the full initiative report.
• Narrative groups stays as before; use the list tab when you need scale triage.

Where in the UI: Findings (/flow-analyzer/findings) — List tab, sticky bulk bar above the findings list.

Assist — AI Agents (Writing Quality, Type & Work Definition, Label Hygiene, Dependency / Flow Risk, Optimization Proposals, Root Cause Synthesis, Constraint & Bottleneck, Predictor, Flow Recovery Facilitator, Planning System Integrity)

Assist — AI Agents (Writing Quality, Type & Work Definition, Dependency / Flow Risk, Resource Constraint, Optimization Proposals, Root Cause Synthesis, Predictor, Flow Recovery Facilitator, Planning System Integrity)

Who it is for: Scrum Masters, coaches, consultants, and RTEs who want advisory coaching from the current workspace snapshot — not a second copy of Findings or VSM.

Why it exists: Rule ids such as TM-05 (meeting tracked as Story), WD-01 (missing acceptance criteria), VS-08 (long blocker chain), FL-01 (WIP overload), and BH-01 (ageing backlog) signal hygiene and waste patterns that are easy to miss in a long findings list. Type & Work Definition explains TM/WD gaps per issue. Dependency / Flow Risk turns VS/FI hits into a ceremony readout. Resource Constraint explains precious people and expert bottlenecks from Resource Sankey scores and RA findings. Optimization Proposals turns FL/WD/BH hits into a refinement workshop agenda grouped by theme. Root Cause Synthesis clusters FL/WD/TM/MI hits into 3–5 retro themes with A3 / 5-Whys why-chains, cited rule ids, optional reinforcing/balancing causal loops, and one experiment each — for copy into retro notes, not to replace the deterministic Retrospective pack. Predictor explains the deterministic P50/P85 labels already shown on the dashboard forecast strip plus VL/BC/SG predictability risks — it never recalculates Monte Carlo finish dates. Flow Recovery Facilitator turns the deterministic 4-week flow recovery plan into a weekly check-in script while copying WIP/Done targets and triage keys exactly from that playbook. Planning System Integrity answers whether the planning loop is healthy / strained / broken from scope KPIs (pctSpDone, scopeAdded, throughput) and BC/SG/VL findings — so teams fix overcommitment and scope churn before blaming delivery. It never invents SP or sprint dates and does not recalculate forecasts (that remains Predictor’s job).

Assist — AI Agents (Writing Quality, Type & Work Definition, Dependency / Flow Risk, Optimization Proposals, WIP & Pull Policy Coach, Root Cause Synthesis, Predictor, Flow Recovery Facilitator, Planning System Integrity)

Who it is for: Scrum Masters, coaches, consultants, and RTEs who want advisory coaching from the current workspace snapshot — not a second copy of Findings or VSM.

How it works: Enable AI assist for the workspace (same gate as before — no silent bypass). Agent cards are grouped into Issue & backlog quality, Initiative metrics & charts, and Workshop & ceremony so you can pick the right specialist faster. Select an agent card and run it for selected issues (or the initiative for Dependency / Flow Risk, Optimization Proposals, Root Cause Synthesis, Case Study Writer, Executive Flow Report, and Predictor). On Select issues, use Filter to search or narrow by type, tribe, team, status, and Problem type (broken rule ids that appear on issues in the list), and Group by to cluster the table (you can select a whole group at once). Columns include Problem rank, Flow quality index (same 0–100 score as issue detail), and Findings count for each Jira item. Rules-only mode always works when no language-model provider is configured. If a language-model provider is configured and you opt into AI narrative, prose may be polished and labeled AI-generated; citations stay grounded in dashboard fields and tool findings. Copy suggestions manually — Flow Analyzer never writes back to Jira, ClickUp, or Asana, never auto-changes issue types, never auto-persists improvement actions, never auto-closes findings, never raises, clears, or edits flags or dependency links, and never recalculates forecast dates for Predictor.

Model this fix → Simulation (#173): After Root Cause Synthesis, Optimization Proposals, and other agents that cite mapped finding refs (for example WD-01: Missing acceptance criteria → DoR AC coverage, or FL-01: WIP limit exceeded → tribe WIP), the follow-up toolbar shows Model this fix on Coach+ workspaces with Simulation entitlement. It opens Simulation with the matching lever pre-focused — same deep-link path as Findings. Predictor also shows Model this fix with forecast context when P50/P85 labels are present; when only VL/BC-style refs apply, Simulation opens without a pre-focused lever so you choose levers on the board. The button is hidden on freemium or when simulationBoard is not entitled. Create action still prefills title and readout only — no auto-create. Scenario results remain illustrative and do not replace the dashboard Monte Carlo forecast.

Assist — Case Study Writer (retro facilitation narrative)

Who it is for: Scrum Masters and Agile coaches preparing a retrospective or change workshop.

What problem it solves: Raw finding counts trigger blame. Case Study Writer turns correlated flow signals into a third-person story the team can recognize without seeing real names or internal keys — plus Socratic mirror questions so loops are discovered, not declared.

Where in the UI: AI Agents → Workshop & ceremony → Case Study Writer → Write case study (initiative scope; no issue selection required).

How it works: The agent builds two blocks: team Markdown (privacy-scanned before display) and coach annex (real issue keys, finding deep links, and rule citations — for your eyes only). Copy team Markdown into retro prep; keep the coach annex private. Optional AI polish follows the same consent gate as other agents. Pilot on Demo (seed) initiative SEED-INIT-ENRL before live workspaces.

Assist — Executive Flow Report (C-suite advisory HTML)

Who it is for: Program sponsors, RTEs, and consultants preparing a board or tribe leadership review — not coaches who need issue-level rewrites.

What problem it solves: Leadership asks for “one pack” with decision brief, KPI strip, cost of inaction, scenario comparison, and OKR hooks. Executive Flow Report merges the same BriefModel and snapshot metrics you already trust on Brief into a self-contained HTML file (17 slides) you can email or present offline — without inventing P85, flow health, or scenario deltas.

Where in the UI: AI Agents → Workshop & ceremony → Executive Flow Report → Build executive report (initiative scope; no issue selection required).

How it works:

1. Enable AI assist for the workspace (same gate as other agents).
2. Run Build executive report for the active initiative. The agent builds a deterministic pack from Brief + snapshot, runs an internal quality check, then renders HTML.
3. Preview in the results panel (document mode by default). Rehearse board slides by adding `?mode=presentation` or `?slide=N` (1-based) to the hub URL — for example /flow-analyzer/agents?agentId=executive-flow-report&mode=presentation&slide=3.
4. Download HTML — the file includes inline CSS, presentation chrome, and keyboard navigation (←/→, Space, Home, End). Works offline after download.
5. Copy run link (optional) — reopens the same preview for about one hour via ?runId=… on the Agents hub.

Document vs presentation mode:

Toggle modes inside the downloaded HTML toolbar, or open with ?mode=presentation.

Scenario simulation (Exhibits 4–5): When findings-grounded what-if levers are available, scenario A/B/C and recommended scenario B detail populate from the simulation engine. When not available, those exhibits show explicit simulation unavailable copy — not fabricated numbers.

Optional export: Power users can also fetch GET /api/export?format=executive-html&initiativeId=… (same authentication as initiative HTML export). The hub download remains the primary path.

Advisory only — numbers stay grounded in your workspace analysis; Flow Analyzer never writes board decisions or roadmap dates back to Jira, ClickUp, or Asana.

SK — Executive Flow Report: AI agenti → Workshop & ceremony → Executive Flow Report → Vytvoriť executive report. Náhľad v režime dokumentu; na skúšku slides pridajte do URL hubu `?mode=presentation` alebo `?slide=N`. Stiahnuté HTML funguje offline; režim prezentácie prepínate v paneli v HTML.

Assist — Truth Gap Auditor (reported vs forensic assurance)

Who it is for: Delivery auditors, PMO leads, and consultants who need a copyable ceremony narrative explaining reported vs forensic throughput gaps — without hand-stitching Truth Gap, Findings, and Brief notes.

What problem it solves: The Truth Gap workbook shows gap % and integrity rows, but client readouts still need assurance language with cited MI / OL / BC / PR evidence. Truth Gap Auditor turns the same Truth Gap model into four blocks: Reported picture, Forensic picture, Gap drivers, and Audit talking points.

Where in the UI: AI Agents → Integrity & trust → Truth Gap Auditor → Run Truth Gap Auditor (initiative scope; no issue selection required). Deep links open Truth Gap, Brief, and Findings filtered to MI | OL | BC | PR.

How it works:

1. Enable AI assist for the workspace (optional — rules-only mode works without an LLM).
2. Run the agent for the active initiative. Counts and gap % match the Truth Gap workbook verbatim — the agent does not recalculate forensics.
3. Money / days-lost lines appear only when the Truth Gap money estimate is present; otherwise omitted with no invented numbers.
4. Copy the readout or use section Copy block buttons for audit ceremonies. Rule citations use RULEID: RULETITLE in prose.

Distinct from: Planning System Integrity (BC/SG/VL planning health), Portfolio Integrity Narrator (multi-tribe assurance), Metric Credibility Coach (score trustworthiness), and the Truth Gap workbook screen itself (forensic drill-down and executive extensions).

SK — Truth Gap Auditor: AI agenti → Integrita a dôvera → Auditor medzery v reportovaní → Spustiť audítora Truth Gap. Štyri bloky: Reportovaný obraz, Forenzný obraz, Hnacie sily medzery, Body na audit. Peniaze/dni straty len pri dodanom odhade Truth Gap.

Assist — Brief Trust panel (outcome vs rule signals)

Who it is for: PMO leads and metric-integrity owners (PER-P9), agile coaches (PER-P2), and Scrum Masters (PER-P1) who open Start here (Brief) for a weekly truth check and need to see when GREEN / high Flow health hides a delivery crisis.

Why it exists: Flow health, Brief RAG, and discipline scores measure rule-signal density (types of findings). Outcome KPIs — BV/week, % BV delivered, cycle time, PI delivery, WIP — measure delivery volume and pace. Without a bridge on Brief, executives can celebrate a green headline while throughput and cycle time collapse.

What problem it solves: An always-on Trust panel on Brief places Outcome (delivery) beside Proxy (rule signals) with plain-language why they differ. Tones are Aligned, Caution, or Do not trust headline alone (crisis) when outcomes look weak while proxy or RAG looks strong. When Focus Wizard goals are set, the bridge names those goals and their primary outcomes, and reminds you that goals do not recalculate Flow health overall. When goals are cleared, the objective outcome-vs-proxy explanation still appears — crisis is never hidden.

Where in the UI: Start here (/flow-analyzer) — after Your goals (when present), before the Brief answer cards. Deep links open Dashboard KPIs, Flow health strata, Discipline dual scores, and optional Metric Credibility Coach. Weekly / Brief digests include a Trust one-liner when tone is caution or crisis.

How to use it:

1. Open Brief for the active initiative (same snapshot as the Dashboard KPI strip).
2. Read the outcome column first when the badge is Caution or crisis — then compare proxy scores.
3. Use the deep links if you need strata detail or a ceremony-length coach readout.

Distinct from Metric Credibility Coach (#245): Trust panel is ambient on every Brief load (cite-only KPIs, no agent run). Metric Credibility Coach is an on-demand Agents hub ceremony with config-gap-first blocks and copyable sections. Use the panel for the weekly glance; open the coach when you need a facilitated narrative.

SK — Panel dôvery na Brief: Start here — po Vašich cieľoch, pred kartami Brief. Stĺpce Výsledok (dodávka) vs Proxy (signály pravidiel); tóny Zladené / Opatrne / Nespoliehajte sa na headline samotné. Ciele neprepočítavajú Flow health overall. Odlišné od Kouča dôveryhodnosti metrík (#245) — panel je vždy na Brief; kouč je na požiadanie v AI agentoch.

Assist — Snapshot staleness banner (re-run analysis)

Who it is for: PMO and metric-integrity owners (PER-P9), agile coaches (PER-P2), and Scrum Masters (PER-P1) who open Start here (Brief), Dashboard, or Findings and need to know when the workspace snapshot is older than a trust window. Organization admins (PER-P6) also see the last succeeded job id for support triage.

Why it exists: SaaS Brief and Dashboard numbers only refresh after an analysis job finishes. Without a shell-level warning, week-old KPIs still look “live,” which drives “why is this wrong?” tickets. The banner is ambient honesty — it does not replace page-local freshness lines or the Trust panel on Brief.

What problem it solves: When the last succeeded analysis is older than the deployment threshold (default 7 days), a non-blocking banner appears above the main content with data as of (absolute date and relative age) and a Re-run analysis button. That button opens the same Run analysis sheet you already use on Findings or Dashboard (date window and optional scope) so you can queue a refresh without hunting for the panel.

Where in the UI: Any analytics screen under the Flow Analyzer shell with an active workspace — for example Start here (/flow-analyzer), Dashboard, and Findings. The banner sits below the header chrome. While a workspace job is running, the job progress banner takes priority and the staleness banner stays hidden. If there is no succeeded analysis or no reliable timestamp, the banner stays hidden (the app never invents an as-of date).

How to use it:

1. Open Brief, Dashboard, or Findings for the active workspace.
2. If the snapshot may be stale, read data as of, then choose Re-run analysis.
3. Set the date window (and optional scope) in the sheet and queue the run.
4. Organization admins can open Organization and workspaces from the job id link for triage; members see as-of and the CTA only.

SK — Banner zastarania snímky: Na Brief / Dashboard / Findings sa pri staršej úspešnej analýze (predvolene > 7 dní) zobrazí banner Snímka môže byť zastaraná s Údaje k … a tlačidlom Spustiť analýzu znova (rovnaký sheet ako Run analysis). Počas bežiacej workspace úlohy sa banner skryje. Admini vidia odkaz na id úlohy.

Assist — Live Jira issue links in workspace snapshots

Who it is for: Scrum Masters and RTEs (PER-P1 / PER-P4), agile coaches (PER-P2), and PMO / metric-integrity owners (PER-P9) who review Findings, VSM, or Issue detail on a live Jira workspace and expect blocker / relates links to match Jira.

Why it exists: Demo (seed) workspaces already carried issue links into the delivery graph and FI-09: Flag Without Blocker Link. Live SaaS ingest now persists the same structural links so coaches are not blind on production Jira workspaces.

What problem it solves: After a successful analysis or webhook/poll refresh, in-scope Jira issue links (type, direction, linked keys) land in the workspace snapshot. Nested titles and descriptions on linked issues are not stored. Links to issues outside the analysis scope are dropped (no invented remote nodes). Incremental updates that omit link fields keep the previous links for that issue.

Where in the UI: Issue detail (links section), VSM (/flow-analyzer/vsm) for non-hierarchy link edges, and Findings for FI-09: Flag Without Blocker Link when an issue is flagged without a Blocks / is-blocked-by link. Seed demo behaviour is unchanged.

How to use it:

1. Use a live Jira workspace and run analysis (or wait for webhook/poll) so a fresh snapshot exists.
2. Open an issue that has Blocks or Relates links in Jira — confirm the same structural links appear in Issue detail.
3. Open VSM — confirm dependency edges for in-scope endpoints.
4. For a flagged issue without a blocker link, confirm FI-09 on Findings; after adding a Blocks link in Jira and re-ingesting, confirm FI-09 clears for that key.

SK — Odkazy na Jira issue v živej snímke: Pri live Jira workspaci sa štrukturálne issuelinks (typ, smer, kľúče) uložia do snímky a použijú vo VSM / Issue detail / FI-09. Narratívne texty na vnorených odkazoch sa neukladajú; odkazy mimo scope sa zahodia.

Assist — Metric Credibility Coach (when to trust headline scores)

Who it is for: Agile coaches, PMO leads, and metric-integrity owners who need a ceremony-ready answer to “can I trust this 78/100 or GREEN RAG?” without opening Brief, Dashboard, Discipline, and Configuration separately.

What problem it solves: Metric credibility programme (#83) aligned Brief, Dashboard, and discipline dual scores, but coaches still hand-explain when green headlines hide missing BV mapping, empty active statuses, or proxy vs outcome divergence. Metric Credibility Coach turns those surfaces into four blocks: Config gaps first, Headline trust verdicts, Proxy vs outcome, and Fix-first actions.

Where in the UI: AI Agents → Integrity & trust → Metric Credibility Coach → Run (initiative scope; no issue picker). Deep links open Configuration, Brief, Dashboard, and Discipline.

How it works:

1. Enable AI assist for the workspace (optional — rules-only mode works without an LLM).
2. Run the agent for the active initiative. Flow health, RAG, % SP / % BV, and dual scores match dashboard / Brief / Discipline inputs verbatim — the agent does not recalculate formulas.
3. Config gaps from workspace integrity signals appear before team-blame language. Verdicts cite MC-## principles (e.g. MC-02, MC-05, MC-08) — never invented industry benchmark percentages.
4. Copy the readout or use section Copy block buttons for ceremonies.

Distinct from: Brief Trust panel (#184 — always-on outcome vs proxy on Start here), Truth Gap Auditor (reported vs forensic throughput), Portfolio Integrity Narrator (multi-tribe assurance), Planning System Integrity (BC/SG/VL planning health), and metric credibility banners / goals strip on Brief and Dashboard (#83 UI).

SK — Kouč dôveryhodnosti metrík: AI agenti → Integrita a dôvera → Kouč dôveryhodnosti metrík → Spustiť. Štyri bloky: Najprv medzery v konfigurácii, Verdikty dôveryhodnosti headline metrík, Proxy vs výsledok, Najprv opravy. Verdikty citujú princípy MC-## — bez vymyslených benchmarkov. Odlišné od panelu dôvery na Brief (#184).

Assist — Code vs Tracker Correlation (commits vs Done alignment)

Who it is for: Initiative PMs and tech leads who need a ceremony-ready narrative of where code signals and tracker Done/state diverge — without manually stitching Initiative PM Code vs tracker, Findings · DC/FS, and Integrations.

What problem it solves: Delivery correlation (#140) and DC/FS rules ship the evidence, but release/postmortem readouts still need grouped mismatch themes, sample issue keys, and audit questions. Code vs Tracker Correlation turns persisted findings and flow-signal coverage into five blocks: Signal coverage, Delivery without commits, Commits without Done, Stale branches, and Audit questions.

Where in the UI: AI Agents → Integrity & trust → Code vs Tracker Correlation → Run (initiative scope; no issue picker). Deep links open Initiative PM · Code vs tracker, Findings · DC|FS, and Findings · code evidence.

How it works:

1. Workspace must have flow signals (GitHub App / git ingest) and an allowlisted repository — otherwise the agent shows an honest capability-gated empty state with an Integrations CTA (no fabricated themes).
2. Run the agent for the active initiative. Theme rows cite DC-## / FS-## rules with sample issue keys from the snapshot only — never invented repos, PR ids, or ages.
3. Audit questions come from the DC coaching playbook facilitation set (process-level language).
4. Copy the readout or use section Copy block buttons for release/postmortem ceremonies.

Distinct from: Truth Gap Auditor (reported vs forensic throughput), Portfolio Integrity Narrator (multi-tribe assurance), Planning System Integrity (BC/SG/VL planning health), Metric Credibility Coach (headline score trust), and the Initiative PM Code vs tracker band itself (#140 workbook drill-down).

SK — Korelácia kódu a trackera: AI agenti → Integrita a dôvera → Korelácia kódu a trackera → Spustiť. Motívy: Dodávka bez commitov, Commity bez Done, Zastaralé branche, Otázky na audit. Pri absencii flow signálov úprimný skip — žiadne vymyslené korelácie.

Assist — Improvement Verification Coach (verify briefing for leadership)

Who it is for: Scrum Masters and coaches (PER-P4) who logged improvement actions; PMO (PER-P9) as a secondary consumer for board paste.

Why it exists: Actions verify UI (#126) shows badges and stats on cards, but leadership still wants effect size, window sufficiency, confidence, and FR-15 false-improvement guardrails in one copyable paragraph.

What problem it solves: Four blocks — Before / after windows, Effect size, Sufficiency & confidence, Board paragraph — plus an explicit False-improvement flag when OL-04: False Improvement Pattern or CC-05 evidence applies. Effect % is copied verbatim from verificationStats when present; otherwise pending copy with no invented percentages.

Where in the UI: AI Agents → Workshop & ceremony → Improvement Verification Coach → Run (initiative scope). Deep links: Improvement actions, Compare (≥2 snapshots), Findings · OL|CC when flagged.

Distinct from: Improvement actions (#126), Snapshot Delta Narrator (#235), Truth Gap Auditor (#233).

SK — Kouč overenia zlepšení: AI agenti → Workshop a ceremonie → Kouč overenia zlepšení → Spustiť. Štyri bloky + príznak falošného zlepšenia; žiadne vymyslené %.

Assist — Portfolio Integrity Narrator (monthly portfolio assurance)

Who it is for: PMO portfolio managers (PER-P9) preparing monthly or QBR assurance packs; external consultants (PER-P8) who need portfolio-grain integrity language without reopening Portfolio, Findings, and Brief per tribe.

Why it exists: The Portfolio Integrity cockpit (#131) shows trust index, tribe rollup, and MI/OL counts, but Agents hub lacked a ceremony card for copyable monthly assurance narrative.

What problem it solves: Three blocks — Executive assurance summary, Tribes at risk (worsening trust trend only), and Top integrity findings (G6 families, capped) — grounded on PortfolioIntegrityCockpitModel only. Trust scores and gap % are copied verbatim; no cross-company benchmarks.

Where in the UI: AI Agents → Integrity & trust → Portfolio Integrity Narrator → Run (workspace portfolio grain; no issue selection). Deep links: Portfolio Integrity tab, Findings (integrity families), Brief for at-risk tribes.

Distinct from: Truth Gap Auditor (#233, single-initiative reported vs forensic), Planning System Integrity (#55), Metric Credibility Coach (#245), Cross-tribe Comparison Narrator (#244), and the Integrity cockpit screen itself.

SK — Rozprávač integrity portfólia: AI agenti → Integrita a dôvera → Rozprávač integrity portfólia → Spustiť. Tri bloky; trust index a tribe riadky z Integrity cockpitu doslovne.

Assist — Snapshot Delta Narrator (weekly what-changed briefing)

Who it is for: Scrum Masters (PER-P4) preparing weekly standups; coaches (PER-P2); PMO when Enterprise digests are unavailable mid-week.

Why it exists: Compare and Brief share SnapshotDiffModel (#145), but Agents hub lacked a ceremony card for copyable weekly paste.

What problem it solves: Headline counts, Narrative lines (byte-identical to Compare for the same pair), Worsened / improved rule families, and Triage overlay notes when triage data exists.

Where in the UI: AI Agents → Initiative metrics → Snapshot Delta Narrator → Run. Deep links: Compare imports; Weekly delta schedules when scheduledDigests is entitled.

Distinct from: Compare imports UI (#145), Improvement Verification Coach (#234), Truth Gap Auditor (#233).

SK — Rozprávač delty snímok: AI agenti → Metriky iniciatívy → Rozprávač delty snímok → Spustiť. Naratívne riadky zodpovedajú Compare pre rovnaký pár.

Assist — Cross-tribe Comparison Narrator (fair peer learning briefing)

Who it is for: PMO (PER-P9) and coaches (PER-P2) who need fair internal peer-learning language for QBR packs without reading the FR-10 table as a league board.

Why it exists: The Dashboard cross-tribe table (FR-10) shows relative ranks, but Agents hub lacked a ceremony narrative that turns the same rows into strengths, gaps, and learning pairs.

What problem it solves: Three blocks — Tribe ranking context (portfolio or initiative grain labeled explicitly), Notable outliers (peer rank plus absolute thresholds), and Suggested peer learning pairs (process-level tribes only, capped). Metrics match the FR-10 loader verbatim; no winner/loser or cross-company language.

Where in the UI: AI Agents → Initiative metrics → Cross-tribe Comparison Narrator → Run (no issue selection). Deep links: Dashboard, Compare imports, Portfolio.

Distinct from: Portfolio Integrity Narrator (#238, trust/MI·OL assurance), Snapshot Delta Narrator (#235), Resource Constraint (#58), and the raw FR-10 table.

SK — Rozprávač porovnania naprieč tribes: AI agenti → Metriky iniciatívy → Rozprávač porovnania naprieč tribes → Spustiť. Tri bloky; interné peer učenie, nie ligová tabuľka.

Assist — Sprint Diagnostic Coach (current sprint health briefing)

Who it is for: Scrum Masters (PER-P4) and RTEs (PER-P3) who need a paste-ready mid-sprint or standup health script without stitching Brief, burn charts, and Findings · BC by hand.

Why it exists: The sprint diagnostic page (#129) shows strengths → blocker → fix, but Agents hub lacked a ceremony card that returns that story as a copyable review script with an explicit health band.

What problem it solves: Three blocks — Sprint health band (On track / Watch / Intervene — never Healthy / Strained / Broken), Top signals, and Review script — grounded on sprint-diagnostic DTOs and BC findings only. Metrics are copied verbatim; burn and scope churn are never recalculated.

Where in the UI: AI Agents → Initiative metrics → Sprint Diagnostic Coach → Run (initiative scope; sprint window from header). Deep links: Sprint diagnostic, Findings · BC.

Distinct from: Planning System Integrity (#55) audits planning-system trust; Sprint diagnostic page (#129) is the full interactive diagnostic workbook.

SK — Kouč diagnostiky sprintu: AI agenti → Metriky iniciatívy → Kouč diagnostiky sprintu → Spustiť. Tri bloky + deep link na Diagnostiku sprintu a Nálezy · BC.

Assist — Discipline Investigation Coach (investigation plan briefing)

Who it is for: Scrum Masters and agile coaches (PER-P4 / PER-P2) who need a copyable investigation plan from Discipline gate bypass, blocker chains, DoD evidence, and PI commitment — without hand-picking keys across Investigation tabs.

Why it exists: The Discipline workbook (#G8) already surfaces investigation tables, but Agents hub lacked a ceremony card that turns that evidence into Top violation themes, Sample keys by tab, and Recommended squad agreements.

What problem it solves: Three blocks grounded on the Discipline investigation API payload only — gate bypass, blocker-chain integrity, DoD evidence / epic DoD, PI commitment (secondary tabs when non-empty). Sample keys are capped subsets of payload keys; FL-07: Mandatory Workflow Stage Skipped and DG / FI families cite catalogue titles in prose. Never recomputes bypass, DoD, or PI math.

Where in the UI: AI Agents → Issue & backlog quality → Discipline Investigation Coach → Run (initiative scope; honors portfolio tribe/team header). Deep links: Discipline Investigation tabs, Findings · FL | DG | FI.

Distinct from: Team Rules & Agreements (durable charter), Critical Path Steward (#232, path-filtered discipline), Dependency / Flow Risk (#41), and the Discipline workbook itself (tables, not ceremony narrative).

SK — Kouč disciplinárneho vyšetrovania: AI agenti → Kvalita issue a backlogu → Kouč disciplinárneho vyšetrovania → Spustiť. Tri bloky + deep link na Discipline a Nálezy · FL | DG | FI.

Assist — PI Planning Facilitator (PI workshop agenda)

Who it is for: RTEs (PER-P3) and agile coaches facilitating PI planning who need a timed workshop agenda from forecast anchors, constraint focus, pi_prep ceremony pack, and VS cross-tribe dependency risks.

Why it exists: Ceremony packs pi_prep and ritual pi_planning (#134) deliver bullets, but Agents hub lacked a PI-horizon facilitator script with Forecast anchors, Timed agenda, Risks, Preparation checklist, and Facilitator script.

What problem it solves: Composes buildCeremonyPack({ packType: 'pi_prep' }), constraint focus, Predictor P50/P85 labels, and VS findings into a copyable PI workshop readout. P50/P85 and scope labels copy verbatim from dashboard; VS risks cite RULEID: RULETITLE in prose. Never invents forecast dates, SP, or issue keys.

Where in the UI: AI Agents → Workshop & ceremony → PI Planning Facilitator → Run (initiative scope). Deep links: Ceremony packs (PI prep view), Constraint focus, Findings · VS | FI, VSM.

Distinct from: Optimization Proposals (#40, refinement FL/WD/BH), Planning System Integrity (#55, healthy/strained/broken audit), and raw ceremony pack bullets without timed facilitator script.

SK — Facilitátor PI plánovania: AI agenti → Workshop a ceremonie → Facilitátor PI plánovania → Spustiť. Päť blokov + deep link na Ceremony packs PI prep, Constraint focus, Nálezy VS, VSM.

Assist — Backlog readiness workflow

Who it is for: Scrum Masters, product owners, and tribe leads who need one initiative-level readout when WD-01: Missing acceptance criteria fires across many Story/Feature items — not a manual merge of Findings, Flow health, and spreadsheet counts.

Why it exists: Definition quality on the Brief and Dashboard Flow health radar penalizes WD/TM/ES rule families, but the score alone does not give a refinement plan, project grouping, or ceremony hooks. The Backlog Readiness agent turns the persisted snapshot into a copyable portfolio readout plus deep links.

What problem it solves: You see % missing AC (against ac_required_types, default Story/Feature), epidemic thresholds (≥ 5 items or ≥ 20% of scoped AC-required types), top Jira project prefixes, TQ-06: Missing acceptance criteria (text quality) / TQ-07: Invalid AC format counts (preferred from persisted findings in the latest analysis; advisory Writing Quality scan only when those findings are absent), a refinement plan, and links to filter the issue picker (brokenRule=WD-01) and Findings (WD-01 / TQ family). Backlog structure mini-histograms (age, story points, priority) appear beside the agent when an initiative is selected.

Where in the UI:

Recommended workflow (advisory — you run each step):

1. Backlog Readiness agent — portfolio readout + epidemic flag + refinement plan.
2. Issue picker — filter Problem type WD-01 (or use agent deep link) → select keys for batch work.
3. Requirements Template — batch AC drafts for selected issues (copy/paste; no write-back).
4. Optimization Proposals — refinement workshop agenda (epidemic block when thresholds met).
5. Root Cause Synthesis — retro theme missing_ac_epidemic when epidemic thresholds met.

Flow Analyzer never writes AC back to Jira, ClickUp, or other trackers.

Assist — AC writing culture workflow

Who it is for: Product owners, business analysts, and Scrum Masters who already have acceptance criteria on Story/Feature items and want to understand how this population thinks in AC — not whether bullets follow Given/When/Then.

Why it exists: Backlog Readiness and WD-01: Missing acceptance criteria measure gaps and epidemic missing AC. Writing Quality coaches single issues. AC Writing Culture adds a corpus-level semantic map: outcome vs task-list “done”, testability habits, edge-case depth, user voice, silent assumptions, and heuristic fit with written standards — with quoted lines for workshops.

What problem it solves: You get tag distributions for the initiative, slices by Jira project prefix, contrast lines for coaching, and up to twenty representative quotes suitable for map-reduce readouts or small LLM synthesis. On very large initiatives, analysis uses stratified sampling (cap 250 Story/Feature items with AC, round-robin by project) and states how many items were in scope vs analyzed. No tracker write-back.

When every scoped Story/Feature item has empty AC text in the snapshot (the same population WD-01: Missing acceptance criteria flags in Findings), the agent does not show blank tag charts. The readout explains that semantic culture analysis needs existing AC text, cites WD-01 / TQ-06 counts when available, lists top projects from the WD-01 signal, and points you to Backlog Readiness and Findings before you re-run AC Writing Culture after AC exists.

Where in the UI:

Findings (deterministic portfolio rules): After analysis, Findings also surfaces extended writing antipatterns as TQ-20 (wiki link only), TQ-21 (screenshot/attachment stub), TQ-22 (AC as Definition of Done), TQ-23 (communication diary / email dump), TQ-24 (duplicate summary in initiative scope), TQ-25 (AC state benefits not verifiable conditions), TQ-26 (AC reference external template or documentation only), TQ-27 (AC meeting notes or validity rules), and TQ-28 (AC system capability not user behavior). Use these for measurable % and issue keys; use AC Writing Culture for workshop quotes and habit tags. TM-10 still flags duplicate summaries among sibling stories under the same parent.

Recommended workflow (advisory):

1. Findings — filter TQ-11–TQ-28 (and WD-01 / TQ-06) for portfolio counts and deep links.
2. AC Writing Culture — portfolio semantic tags + evidence quotes.
3. Backlog Readiness — missing-AC % and refinement plan when definition quality is weak.
4. Writing Quality — per-issue ScrumDesk-style suggestions on exemplar keys.
5. Requirements Template — batch drafts where outcome language is absent.

Flow Analyzer never writes AC back to Jira, ClickUp, or other trackers.

Assist — Workspace configuration coach

Who it is for: Organization administrators and Scrum Masters setting up a new or partially configured workspace — especially when Configure from source feels overwhelming.

Why it exists: Workspace Configuration has many knobs (workflow, DoD gates, tribe mapping, acceptance-criteria fields). The Workspace config coach skill in AI Chat interviews you one question at a time with quick-answer chips, then proposes a human-readable summary before any write.

What problem it solves: You pick a delivery methodology (Scrum, SAFe, Kanban, hybrid, or help-me-choose), answer focused questions grounded in your connector catalog, review affected config.* sections, and — if you are an organization administrator — apply validated changes in one confirm step. Non-admins can finish the interview and open Configuration or copy the recommendation for an admin.

Where in the UI: Floating AI Chat (bottom-right) → skill Workspace config coach → answer chips on each assistant turn (Type my own answer is always last). After the summary, tap Apply to workspace (admins only) and confirm in the dialog. You can also open Configuration any time to verify or fine-tune.

How it works: The coach reads your current workspace envelope, live source catalog (issue types, statuses, fields when connected), and configuration-related findings (for example WD-01: Missing acceptance criteria, ORG-01, FL-). It does not* invent catalog values. Applying runs the same validation as the Configuration screen; nothing is saved without your explicit confirmation.

Example: You connect a Jira portfolio workspace with Epic/Feature hierarchy and PI-style statuses → choose Help me choose → coach recommends SAFe → you confirm → follow-up questions include SAFe DoD funnel stages and optional tribe field mapping → review summary → apply as org admin → reload Configuration to see updated stage order and fields.

Example: Initiative scope has 12 Story items without AC (24% of AC-required types) → Backlog Readiness headlines epidemic, groups AKVI (5) and BENE (4), lists TQ-06 / TQ-07 counts from persisted findings when present, and links to Findings · WD-01. You filter the picker, run Requirements Template on six keys, then copy the OP section 0 block into refinement notes.

SK — workflow pripravenosti backlogu:

Príklad (SK): 12 Story bez AC (24 %) → agent označí epidémiu, zoskupí projekty AKVI / BENE, odporučí filter WD-01 a batch Requirements Template; OP blok 0 a RC téma missing_ac_epidemic pri rovnakých prahoch.

TQ-06 / TQ-07 vs WD-01: WD-01: Missing acceptance criteria fires when the AC field is empty on AC-required types (workflow/DoR evidence). TQ-06: Missing acceptance criteria (text quality) (empty AC text) and TQ-07: Invalid AC format (unstructured AC) are engine findings for Definition quality and Findings with distinguishable evidence (signal_source: text_quality_ac). Both WD-01 and TQ-06 may fire on the same empty-AC set. Backlog Readiness prefers persisted TQ-06/TQ-07 findings from the latest analysis and falls back to an advisory text-quality scan only when those findings are absent.

Assist — Holiday calendar for cycle time

Who it is for: Scrum Masters (PER-P1), agile coaches (PER-P2), and PMO / metric-integrity owners (PER-P9) who need cycle time, lead time, and time-in-status to skip real non-working days — not only Saturdays and Sundays.

Why it exists: Teams often pause during national holidays. Without a holiday calendar in the working time zone, control charts and initiative metrics look slower than the team actually worked. The engine already supported holiday dates; Configuration now makes that calendar easy to maintain.

What problem it solves: Under Configuration → Workflow → Cycle time metrics, turn on Exclude weekend days, set a Working time zone (for example Europe/Bratislava), and maintain a Holiday calendar list of full non-working days. You can add or remove dates, dedupe and sort, paste a list, or Import from calendar (.ics file or calendar URL). Import previews events and lets you merge or replace — replace and clear-all ask for confirmation first. When weekends are off, zone and holiday controls stay hidden and metrics use full wall-clock duration. Run analysis shows a short honesty line with the zone and holiday count from the saved workspace config (this run does not override the calendar).

Where in the UI: Configuration → Workflow → Cycle time metrics. Optional honesty strip on the Run analysis sheet (Findings, Dashboard, and related CTAs).

How to use it:

1. Open Configuration → Workflow and enable Exclude weekend days.
2. Set Working time zone to the zone your team uses for weekends and holidays.
3. Add holiday dates, or choose Import from calendar, preview, then Merge or Replace.
4. Save configuration, then re-run analysis so new cycle-time numbers use the calendar.
5. Spot-check control chart or initiative metrics for issues that spanned a holiday.

SK — Kalendár sviatkov pre cycle time: V Konfigurácia → Workflow → Metriky cyklického času zapnite vylúčenie víkendov, nastavte Pracovnú časovú zónu a spravujte Kalendár sviatkov (pridať / odstrániť / import .ics). Pri vypnutých víkendoch ostanú ovládacie prvky skryté a metriky používajú plný kalendárny čas. Sheet Spustiť analýzu ukáže krátky riadok so zónou a počtom sviatkov.

Assist — Backlog structure panel (Backlog Readiness)

Who it is for: Product owners, tribe leads, and Scrum Masters who need a quick shape-of-backlog readout before refinement — not only per-issue WD-01 coaching from the Backlog Readiness agent.

What problem it solves: A long findings list can hide whether the backlog is fresh or stale, estimated or unestimated, and priority-skewed. The structure panel shows three mini-histograms from the persisted workspace snapshot so you judge backlog health at a glance.

Where in the UI: AI Agents → Issue & backlog quality → Backlog Readiness → scope column (right). The panel appears only for this agent when an initiative is selected. It does not show for other agents.

How it works: Counts come from open issues whose status is in workflow.initial_statuses (the same open-backlog filter as IA-01: Age Distribution — Backlog Aging Profile). Three histograms:

Data loads from the backlog-structure API using the active workspace persisted snapshot. If no snapshot exists, the panel shows a localized load error — no invented bar heights. Loading state appears while fetching.

SK — Štruktúra backlogu (Backlog Readiness): V AI agentoch → Kvalita issues a backlogu → Backlog Readiness (len pri zvolenej iniciatíve) v stĺpci rozsahu uvidíte tri mini-histogramy z perzistentnej snímky workspace:

• Vek — počty issues v rovnakých vekových intervaloch ako IA-01: Rozloženie veku — profil starnutia backlogu (0–30d … 365+d). Dlhý chvost v 181+d zodpovedá signálom zastaraného backlogu v Nálezoch.
• Story pointy — rozloženie odhadov (neodhadnuté, 1 SP, 2–3 SP, …) — dopĺňa SP súčty v IA-01, nie nové pravidlo.
• Priorita — počty podľa priority v trackeri — kontext pre poradie refinmentu.

Bez perzistentnej snímky panel zobrazí chybu načítania, nie vymyslené výšky stĺpcov.

Assist — Estimation & Sizing Coach (#239)

Who it is for: Scrum Masters and POs who run sizing workshops from ES-family findings (missing estimates, SP inconsistency) without hand-stitching Findings.

Why it exists: Backlog Readiness and Requirements Template cover AC refinement; this agent owns sizing hygiene — ES summary, project/tribe groups, copyable workshop agenda, and BV mapping honesty.

Where in the UI: AI Agents → Issue & backlog quality → Estimation & Sizing Coach → Run (initiative default; optional issue picker narrows the batch).

Workflow: Run with empty selection → review ES summary and groups → Copy agenda → open Findings · ES or Issue picker · ES → after sizing, pair with Backlog Readiness → Requirements Template for AC. TM findings appear as callouts only (route to Type & Work Definition). Advisory only — never writes SP to the tracker.

SK: AI agenti → Kvalita issues a backlogu → Coach odhadov a veľkosti → spustiť pre iniciatívu → skopírovať agendu → Nálezy · ES → po sizingi Backlog Readiness → Requirements Template pre AC.

Assist — Practice Adoption Coach (#242)

Who it is for: New Scrum Masters who want a prioritized “consider starting…” plan on the Agents hub — not only Brief or AI Chat.

Why it exists: Uses the same evaluatePracticeAdoptionNudges catalogue as Brief Practice suggestions (≤3 practices, evidence chips, config deep links, linkedPracticeId for Track handoff). Distinct from Workspace Configuration Proposals (concrete config value drafts).

Where in the UI: AI Agents → Issue & backlog quality → Practice Adoption Coach → Run (workspace scope; no issue picker). Respects Brief snoozes.

SK: AI agenti → Kouč adopcie praktík → rovnaký katalóg ako Brief · Návrhy praktík; poradné — bez auto-Apply konfigurácie.

Assist — Focus Wizard Guide (#247)

Who it is for: First-run users who want a coached path through Focus Wizard profiles without facing the full rule catalogue on day one.

Why it exists: Lightweight interview (G1 shorten delivery, G6 metric integrity, G4 find constraints) → recommended profile + exactly three next steps (Focus Wizard confirm, highlighted screens, shipped hub agents). Never auto-applies the focus profile.

Where in the UI: AI Agents → Issue & backlog quality → Focus Wizard Guide → pick goal → Run. Confirm profile in Focus Wizard or Profile → My focus.

SK: Sprievodca Focus Wizardom — vyberte G1/G6/G4 → tri ďalšie kroky → potvrdenie profilu len vo Focus Wizard; agent neaplikuje profil sám.

Assist — Initiative Graph Navigator (#243)

Who it is for: RTEs, flow coaches, and workshop facilitators who need a cited walkthrough of the initiative value stream map — critical path, top risk nodes, and dependency hotspots — without manually clicking every node.

Why it exists: computeInitiativeGraph already exposes topology, cycle warnings, and risk scores. This agent turns that bundle into a facilitation narrative with deep links into Value stream map overlays (criticalPath, blockedOnly, selected node). Distinct from Dependency / Flow Risk (findings ceremony) and Critical Path Steward (protect/discipline/oversight on the path).

Where in the UI: AI Agents → Workshop & ceremony → Initiative Graph Navigator → Run (initiative scope). Copy ceremony sections; follow deep links to VSM with the right filters pre-applied.

SK: AI agenti → Workshop a ceremonie → Navigátor grafu iniciatívy → spustiť pre iniciatívu → skopírovať walkthrough → Mapa value streamu s overlay parametrami.

Assist — Stakeholder Status Writer (#246)

Who it is for: Initiative PMs and RTEs who need a concise weekly stakeholder update — wins, risks, and asks — grounded in Brief and top findings, not a full executive report.

Why it exists: Brief already summarizes flow health and recommendations; Findings hold rule-backed evidence. This agent composes a copy-ready status in Markdown and plain text for email or chat. Distinct from Flow Analysis (general health coaching) and Executive Flow Report (orchestrator programme #261).

Where in the UI: AI Agents → Workshop & ceremony → Stakeholder Status Writer → Run (initiative scope). Use Copy Markdown or Copy plain text on the run view.

SK: AI agenti → Workshop a ceremonie → Autor statusu pre stakeholderov → týždenný status (výhry, riziká, požiadavky) → kopírovať Markdown alebo plain text.

Assist — Critical Path Steward (#232)

Who it is for: RTEs and constraint coaches who must protect people and teams on the initiative critical path — not just see the path on VSM.

Why it exists: Joins critical path node ids from the initiative graph with Sankey precious people, path-filtered Discipline signals, and VS/FI/DV findings into three blocks: Protect, Discipline, and Oversight watchlist. Deep links open VSM, Resources Sankey, Discipline, Findings, and Constraint focus with the right filters. Complements Discipline Investigation Coach and Initiative Graph Navigator; distinct from Resource Constraint (initiative-wide precious) and Constraint & Bottleneck (TOC pack).

Where in the UI: AI Agents → Initiative metrics & charts → Critical Path Steward → Run (initiative scope). Follow section deep links or copy the stewardship readout.

SK: AI agenti → Metriky iniciatívy a grafy → Správca kritickej cesty → tri bloky Chrániť / Disciplína / Dozor → odkazy na mapu, Sankey, Disciplínu a Nálezy.

Assist — Code vs tracker correlation (Initiative PM)

Who it is for: Enterprise PMO and release-engineering leads who need to know whether pre-release Jira stages and correlated git activity tell the same story.

Why it exists: Pipeline findings alone cannot say whether code actually moved. Code vs tracker joins pre-release stage aging with GitHub (or Jira development information) pull request and merge signals so you can spot release-pipeline blockage with code evidence — without developer scorecards or a separate DORA dashboard.

Where to find it: Open Initiative PM, select an issue, scroll below Flow Story. The Code vs tracker band shows mismatch class (code stalled / tracker stalled / aligned / insufficient signals), stage age, last merge age, signal coverage, and links into Findings filtered to PL- and DC-. On a finding for PL-01 or DC-*, expand the row to see the Code evidence** panel (PR refs, merge age, signal source).

Empty state: If the workspace has no flow signals, the band explains how to connect GitHub under Organization settings → Integrations (or enable Jira development information). It does not invent PR timestamps. Azure Repos correlation is marked as planned until that connector path ships.

Plans: Full correlation is an Enterprise surface; Coach orgs see an upgrade prompt instead of fabricated metrics.

Assist — AI Chat (floating conversation)

Who it is for: Scrum Masters, coaches, and RTEs who want a quick conversational explanation of findings or flow health without opening a specialist agent card.

Why it exists: Batch agents are excellent for Writing Quality rewrites or ceremony agendas; day-to-day questions (“why is DEMO-104 flagged?”, “what changed this week?”) fit a floating chat better.

What problem it solves: You stay on Findings, Discipline, or any authenticated screen, open the AI bubble, and ask in natural language. Slash commands (/findings, /cfd, /forecast, /brief, /repeat) and quick prompts seed useful context from the workspace snapshot. Repeat on an assistant reply (or /repeat) re-asks the previous question against the current workspace. Copy puts the message on the clipboard. Optional MCP tools can pull findings, dashboard, or flow story evidence. Threads are saved per workspace so you can resume later. In the left History column, use ⋯ on a thread to rename, archive (hide from the default list; expand Show archived to restore), or delete permanently. Double-click a title to rename inline.

Where in the UI: AI Chat is the first item under Analyze in the main sidebar when your organization has a configured LLM provider — open it for a full-page layout with conversation history on the left and the active thread on the right. The floating AI button (bottom-right) remains on other Flow Analyzer screens for quick access. Organization LLM settings remain under Organization settings → AI Agents. Chat reuses the same enable AI assist consent as Agents.

How it works: Organization AI Agents must be on and a provider configured. Enable AI assist for the workspace, then send a message. Answers stream as markdown (headings, lists, links, tables, optional ``mermaid / `fa-chart / ``svg blocks, and HTTPS images), are labeled AI-generated, and never write back to trackers. Turn MCP off in the chat toolbar when you want conversation-only replies without tool lookups. Use the toolbar skill selector for Flow coach (general flow health) or Backlog readiness (WD-01 / missing-AC coaching — recommends Agents or Findings, never auto-runs agents).

Assist — AI Chat grounded Brief, map, and CFD (#109)

Who it is for: Scrum Masters, RTEs, and flow coaches who ask about Brief constraint focus, root cause map loops, CFD stability, forecasts, or acceptance-criteria quality in the floating AI Chat.

Why it exists: Chat used to prefetch a full dashboard dump and expose multiple tool schemas. That made answers noisy and did not scale as more screens shipped.

What problem it solves: With MCP on, chat uses a single `read_workspace` tool (plus an optional skill-gated scenario helper). Prefetch is a compact workspace digest. Slash /brief, /cfd, and /forecast load those views — the same numbers as the Brief / CFD / forecast screens — not a raw dashboard paste. Ask about map loops or “review AC on ISSUE-1” and answers stay snapshot-grounded. When the assistant suggests deeper causal work, tap Open Agents · Root Cause Synthesis to open the Agents hub with initiative scope — chat never silently runs agents.

Where in the UI: Same floating AI chat as above. Skills include Flow coach, Backlog readiness, CFD interpreter, Workspace config coach, and Practice adoption coach.

Assist — AI Chat focused views Phase 1 (#187)

Who it is for: Scrum Masters, RTEs, and coaches who ask about Brief, the causal map, CFD, control charts, or delivery forecast in the floating chat.

Why it exists: After consolidating to one read tool, coaches still needed focused slices — not a truncated dashboard dump — so Assist cites the same constraint, loops, stage totals, cycle-time outliers, and P50/P85 as the screens.

What problem it solves: Chat can look up Brief, root cause map (loops / regions / coach-authored labels — not canvas positions), CFD, control chart, and forecast detail when needed. Flow coach prefetches a bounded Brief on top of the always-on digest; CFD interpreter prefetches CFD. When forecast data is missing, Assist refuses invented finish dates. Empty snapshots fail closed — no invented issue keys, stage totals, or map loops.

Where in the UI: Same floating AI chat. No new panels — use slash /brief, /cfd, /forecast, or skill chips.

Assist — AI Chat page-context prefetch (#188)

Who it is for: Scrum Masters, RTEs, and coaches who open Assist while already looking at Brief, Findings, the root-cause map, or VSM.

Why it exists: Slash commands and skills still work, but when you are already staring at a coaching screen you should not have to type /brief or re-explain “based on this screen” for the first answer.

What problem it solves: Opening floating AI Chat from Brief, Findings, or the causal map auto-grounds the first message in that screen’s summary (same builders as the UI — not invented metrics). A small Context · … chip in the chat header shows which screen is active; you can dismiss it for the rest of the session. Later messages keep the conversation going without re-fetching that page view. On VSM, the chip still appears and the usual workspace digest runs — Assist does not invent hierarchy metrics until a dedicated VSM view ships.

Where in the UI: Floating AI button on Brief, Findings, root-cause map, or VSM. Look for Context · Brief / Findings / Map / VSM in the chat header when the panel opens.

Assist — Agent bridge cards (#189)

Who it is for: Scrum Masters, Agile coaches, and flow coaches who ask floating AI Chat workshop questions (“why are we slow?”, “what should we discuss in refinement?”, “is the backlog ready?”).

Why it exists: Those questions belong with specialist Agents hub runners (Root Cause Synthesis, Optimization Proposals, Backlog Readiness). Assist should hand you off safely — never auto-run an agent and never put hub runners into chat tools.

What problem it solves: When your question (or the Backlog readiness skill) matches a workshop intent, the assistant reply includes a bridge card with Run … and Open Agents hub. With Backlog readiness, you may see cards for Backlog Readiness and AC Writing Culture (missing-AC portfolio vs semantic habits when AC text exists). Questions about writing culture, lived AC, or how teams phrase acceptance criteria can surface the AC Writing Culture bridge alone. Run opens a confirm dialog (and the Assist consent dialog first if AI assist is off). Only after you Confirm does Assist call the same Agents run API as the hub. Open Agents hub and Cancel never start a run. If a recent run for that workspace, agent, and initiative is still cached, you also see a last-run card with a short advisory summary plus View last run / Run again / Open hub — Assist does not invent scores when nothing is cached.

Where in the UI: Floating AI Chat. Bridge cards appear under the assistant message for matching intents. Full readouts stay on AI Agents (/flow-analyzer/agents with the agent and initiative preselected).

Assist — Practice suggestions (#209)

Who it is for: Scrum Masters, RTEs, and delivery leads who open Start here (Brief) or the Dashboard and want coach-like “consider starting…” advice when Jira looks clean but setup gaps leave rules silent.

Why it exists: Findings fire when tracker evidence shows pain. Teams that never configured WIP limits, acceptance criteria fields, or SLA maps often see silence — or only skipped-rule observability — not a clear next practice to adopt.

What problem it solves: Flow Analyzer evaluates a product catalogue of practices from your workspace configuration and rule coverage. The Brief shows up to three Practice suggestions with evidence chips (config path, skipped-rule counts) and a link into configuration. You can Track as improvement action (creates an experiment on Improvement actions linked to the practice) or Remind me for 7 or 30 days so the same nudge does not nag every visit. The Dashboard shows the same themes with View in Brief. AI Chat skill Practice adoption coach answers “what should we start?” from those prefetched nudges only — it refuses invented ceremonies.

Where in the UI: Brief (Start here) strip above the answer cards; Dashboard card near Flow health; optional Getting Started hints in the sidebar; Improvement actions for tracked experiments; AI Chat skill chip Practice adoption coach.

Assist — Getting Started programme completion (#194)

Who it is for: Org admins and Scrum Masters setting up a new SaaS workspace, plus coaches walking a client through day one.

Why it exists: Registering an organization is not enough — you still need a workspace, data (Jira or seed), configuration, a first analysis, and a place to track improvements. Without a durable checklist, people stall in empty Brief or lose progress after refresh.

What problem it solves: The sidebar Getting Started programme walks you through six honest steps with deep links that open real screens: create workspace, connect Jira or seed, map acceptance criteria, run first analysis, review practice suggestions on Brief, and open the Actions hub. Manual check-offs survive refresh for your user and workspace. After register, zero workspaces land on Organization and workspaces; with a workspace you land on Brief with Getting Started expanded for that guided activation. When every step is done, the block collapses and you can dismiss or show it again.

Where in the UI: Flow Analyzer sidebar Getting Started (with workspace controls); first login after register via Login → Org settings or Brief; Actions hub under Improvement actions.

Assist — Practice adoption coach (#214)

Who it is for: Scrum Masters and Agile coaches who want a conversational answer to “what should we start doing?” without inventing rituals.

Why it exists: Brief and Dashboard already surface practice suggestions; AI Chat is where coaches discuss next steps in natural language, and outbound webhooks wake Slack/n8n when a new high-severity gap appears.

What problem it solves: Select Practice adoption coach in floating AI Chat. Replies use prefetched practice nudges (or Brief) and cite evidence chips. The assistant may mention Configuration deep links and Brief Track as improvement action, but never applies config or creates actions for you. Under Organization settings → Integrations → Outbound webhooks, subscribe to Practice adoption gap for allow-listed signed deliveries (no issue bodies).

Where in the UI: Floating AI chat → skill Practice adoption coach / Kouč adopcie praktík; Org settings → Integrations → Outbound webhooks.

Assist — Org capacity coach (#278)

Who it is for: PMO leads and tribe coaches on Org structure who need sponsor-ready capacity narrative (configured FTE, observed load, shared people, suggested FTE Δ) without juggling Dashboard FR-10 columns in a second tab.

Why it exists: The org_structure read view already projects tribe capacity from the same snapshot as the UI, but generic Flow coach answers lack tribe-level capacity rows.

What problem it solves: On Advanced analytics → Org structure, open floating AI Chat (Context · Org structure when page context is active). Select skill Org capacity coach / Kouč kapacity org. Replies cite prefetched org_structure data only — tribe configured FTE, observed load %, suggested Δ, shared people counts, and overloaded spotlight people. When the roster is empty, the assistant explains emptyReason and points to Org structure configuration without inventing FTE. Deep-link guidance mentions Overview (capacity) on Org structure and the Dashboard cross-tribe / FR-10 table. Role gaps, bus factor, and hiring narrative belong to the sibling HR overview coach skill (not this chip).

Where in the UI: /flow-analyzer/org-structure?chatContext=org_structure → AI Chat skill selector (Org capacity coach). On Org structure, the skill is suggested (ordered first) but not auto-selected if you already chose another skill.

Assist — Outbound webhook Analysis failed (#162)

Who it is for: Ops engineers and org admins who already wire outbound webhooks to Slack, n8n, or PagerDuty and need on-call alerts when analysis or ingest jobs fail — without polling job status.

Why it exists: Success events (analysis.completed) and connection health were already on the bus; job failures stayed silent unless someone watched Organization settings or the jobs API.

What problem it solves: Under Organization settings → Integrations → Outbound event webhooks, subscribe to Analysis failed (SK: Analýza zlyhala). When a tenant analysis or ingest job reaches terminal failed, Flow Analyzer posts a signed allow-listed payload (job_id, error_code, job_type, optional initiative id) — never passwords, stack traces, or issue bodies.

Where in the UI: Organization and workspaces → Integrations → Outbound event webhooks → event multi-select Analysis failed.

Assist — AI Agents (Writing Quality, Type & Work Definition, Label Hygiene, Dependency / Flow Risk, Optimization Proposals, Root Cause Synthesis, Constraint & Bottleneck, Predictor, Flow Recovery Facilitator, Planning System Integrity)

Who it is for: Scrum Masters, coaches, consultants, and RTEs who want advisory coaching from the current workspace snapshot — not a second copy of Findings or VSM.

Why it exists: Rule ids such as TM-05 (meeting tracked as Story), WD-01 (missing acceptance criteria), VS-08 (long blocker chain), FL-01 (WIP overload), and BH-01 (ageing backlog) signal hygiene and waste patterns that are easy to miss in a long findings list. Type & Work Definition explains TM/WD gaps per issue. Label Hygiene audits the whole snapshot's labels for near-duplicates, stale PI_* tags, taxonomy orphans, and cross-links DV-08 / PL-09 / PL-12 / MI-18 — so PMO and consultants stop exporting label lists to spreadsheets. Dependency / Flow Risk turns VS/FI hits into a ceremony readout. Optimization Proposals turns FL/WD/BH hits into a refinement workshop agenda grouped by theme. Root Cause Synthesis clusters FL/WD/TM/MI hits into 3–5 retro themes with A3 / 5-Whys why-chains, cited rule ids, optional reinforcing/balancing causal loops, and one experiment each — for copy into retro notes, not to replace the deterministic Retrospective pack. Constraint & Bottleneck answers "what is the constraint?" with TOC exploit / subordinate / elevate actions grounded in the weekly constraint pack, findings, and interventions — distinct from the optional executive-summary narrator on the pack itself and from Flow Analysis general health. Predictor explains the deterministic P50/P85 labels already shown on the dashboard forecast strip plus VL/BC/SG predictability risks — it never recalculates Monte Carlo finish dates. Flow Recovery Facilitator turns the deterministic 4-week flow recovery plan into a weekly check-in script while copying WIP/Done targets and triage keys exactly from that playbook. Planning System Integrity answers whether the planning loop is healthy / strained / broken from scope KPIs (pctSpDone, scopeAdded, throughput) and BC/SG/VL findings — so teams fix overcommitment and scope churn before blaming delivery. It never invents SP or sprint dates and does not recalculate forecasts (that remains Predictor's job).

What problem it solves: You can coach refinement on one issue at a time with cited rule ids from the snapshot (never invented defects), clean label debt with a catalog and duplicate clusters grounded in real issue keys, walk an RTE sync with VS/FI sample keys, facilitate backlog/refinement with prioritized FL/WD/BH themes and copyable agenda blocks, run a weekly TOC where-to-focus session from the constraint pack, run a tribe recovery check-in from the same numbers the dashboard already shows, or run a PI-prep integrity audit with ceremony fixes — then manually create improvement actions if you choose.

How it works: Enable AI assist for the workspace (same gate as before — no silent bypass). Agent cards are grouped into Issue & backlog quality, Initiative metrics & charts, and Workshop & ceremony so you can pick the right specialist faster. Select an agent card and run it for selected issues (or the initiative for Label Hygiene, Dependency / Flow Risk, Optimization Proposals, Root Cause Synthesis, Constraint & Bottleneck, Predictor, Flow Recovery Facilitator, and Planning System Integrity). On Select issues, use Filter to search or narrow by type, tribe, team, status, and Problem type (broken rule ids that appear on issues in the list), and Group by to cluster the table (you can select a whole group at once). Columns include Problem rank, Flow quality index (same 0–100 score as issue detail), and Findings count for each Jira item. Rules-only mode always works when no language-model provider is configured. If a language-model provider is configured and you opt into AI narrative, prose may be polished and labeled AI-generated; citations stay grounded in dashboard fields and tool findings. Copy suggestions manually — Flow Analyzer never writes back to Jira, ClickUp, or Asana, never auto-changes issue types, never create/merge/delete tracker labels, never auto-persists improvement actions, never auto-closes findings, never raises, clears, or edits flags or dependency links, never invents SP/sprint dates for Planning System Integrity, never recalculates forecast dates for Predictor, and never regenerates recovery targets for the Facilitator.

How it works: Enable AI assist for the workspace (same gate as before — no silent bypass). Agent cards are grouped into Issue & backlog quality, Initiative metrics & charts, and Workshop & ceremony so you can pick the right specialist faster. Select an agent card and run it for selected issues (or the initiative for Dependency / Flow Risk, Resource Constraint, Optimization Proposals, Root Cause Synthesis, Predictor, Flow Recovery Facilitator, and Planning System Integrity). On Select issues, use Filter to search or narrow by type, tribe, team, status, and Problem type (broken rule ids that appear on issues in the list), and Group by to cluster the table (you can select a whole group at once). Columns include Problem rank, Flow quality index (same 0–100 score as issue detail), and Findings count for each Jira item. Rules-only mode always works when no language-model provider is configured. If a language-model provider is configured and you opt into AI narrative, prose may be polished and labeled AI-generated; citations stay grounded in dashboard fields and tool findings. Copy suggestions manually — Flow Analyzer never writes back to Jira, ClickUp, or Asana, never auto-changes issue types, never auto-persists improvement actions, never auto-closes findings, never raises, clears, or edits flags or dependency links, never invents SP/sprint dates for Planning System Integrity, never recalculates forecast dates for Predictor, and never regenerates recovery targets for the Facilitator.

How it works: Enable AI assist for the workspace (same gate as before — no silent bypass). Agent cards are grouped into Issue & backlog quality, Initiative metrics & charts, and Workshop & ceremony so you can pick the right specialist faster. Select an agent card and run it for selected issues (or the initiative for Dependency / Flow Risk, Optimization Proposals, Root Cause Synthesis, Constraint & Bottleneck, Predictor, Flow Recovery Facilitator, and Planning System Integrity). On Select issues, use Filter to search or narrow by type, tribe, team, status, and Problem type (broken rule ids that appear on issues in the list), and Group by to cluster the table (you can select a whole group at once). Columns include Problem rank, Flow quality index (same 0–100 score as issue detail), and Findings count for each Jira item. Rules-only mode always works when no language-model provider is configured. If a language-model provider is configured and you opt into AI narrative, prose may be polished and labeled AI-generated; citations stay grounded in dashboard fields and tool findings. Copy suggestions manually — Flow Analyzer never writes back to Jira, ClickUp, or Asana, never auto-changes issue types, never auto-persists improvement actions, never auto-closes findings, never raises, clears, or edits flags or dependency links, never invents SP/sprint dates for Planning System Integrity, never recalculates forecast dates for Predictor, and never regenerates recovery targets for the Facilitator.

Assist — AI Chat (floating conversation)

Who it is for: Scrum Masters, coaches, and RTEs who want a quick conversational explanation of findings or flow health without opening a specialist agent card.

Why it exists: Batch agents are excellent for Writing Quality rewrites or ceremony agendas; day-to-day questions (“why is DEMO-104 flagged?”, “what changed this week?”) fit a floating chat better.

What problem it solves: You stay on Findings, Discipline, or any authenticated screen, open the AI bubble, and ask in natural language. Slash commands (/findings, /cfd, /forecast, /brief, /repeat) and quick prompts seed useful context from the workspace snapshot. Repeat on an assistant reply (or /repeat) re-asks the previous question against the current workspace. Copy puts the message on the clipboard. Optional MCP tools can pull findings, dashboard, or flow story evidence. Threads are saved so you can resume later.

Where in the UI: Floating AI button (bottom-right) on Flow Analyzer when you have an active workspace. Organization LLM settings remain under Organization settings → AI Agents. Chat reuses the same enable AI assist consent as Agents.

How it works: Organization AI Agents must be on and a provider configured. Enable AI assist for the workspace, then send a message. Answers stream as markdown, are labeled AI-generated, and never write back to trackers. Turn MCP off in the chat toolbar when you want conversation-only replies without tool lookups. Use the toolbar skill selector for Flow coach (general flow health) or Backlog readiness (WD-01 / missing-AC coaching — recommends Agents or Findings, never auto-runs agents).

Chat skills: Use the toolbar skill selector to choose coaching focus:

• Flow coach (default) — general findings, cycle time, CFD, and flow-health explanations.
• Backlog readiness — WD-01 missing-AC portfolio signals (% without AC, top projects), refinement workflow (Backlog Readiness agent → WD-01 issue filter → Requirements Template → Optimization Proposals / Root Cause epidemic theme), and TQ-06: Missing acceptance criteria (text quality) / TQ-07: Invalid AC format engine findings (Backlog Readiness prefers persisted counts; advisory Writing Quality scan only when TQ findings are absent). Chat recommends AI Agents or Findings but never auto-runs agents or writes AC back to Jira/ClickUp. With an empty snapshot, chat refuses invented issue rows and points you to seed or live setup.

Zručnosti chatu (SK): V paneli nástrojov vyberte zameranie koučingu:

• Kouč toku (predvolené) — všeobecné vysvetlenia nálezov, cycle time, CFD a zdravia toku.
• Pripravenosť backlogu — portfóliový signál WD-01 (chýbajúce AC, top projekty), workflow refinmentu (agent Backlog Readiness → filter WD-01 → Requirements Template → Optimization Proposals / Root Cause epidémia) a engine nálezy TQ-06 / TQ-07 (preferované uložené počty; poradný scan Writing Quality len keď TQ nálezy chýbajú). Chat odporučí AI agentov alebo Nálezy, nikdy nespúšťa agentov automaticky ani nezapisuje AC do Jira/ClickUp. Pri prázdnej snímke nevymýšľa riadky issues — odporučí seed alebo live dáta.

TQ-06 / TQ-07 vs WD-01 vs Backlog Readiness agent

EN: Use WD-01 for workflow/DoR gates (“field empty on required types”). Use TQ-06 when you care about text-quality portfolio views that align with Writing Quality. Use TQ-07 when AC exists but is prose-only. The Backlog Readiness agent does not replace Findings — it summarizes and links to them.

SK: WD-01 slúži na workflow/DoR brány (prázdne pole na povinných typoch). TQ-06 pri portfóliovom pohľade na kvalitu textu AC. TQ-07 keď AC existuje, no nie je štruktúrované. Agent Backlog Readiness nezastupuje Nálezy — sumarizuje ich a odkazuje na ne; počty TQ preferuje z uložených nálezov.

Where in the UI: Sidebar Assist → AI Agents. Initiative PM dashboard Finish oldest first — Coach pull policy. Discipline and Ceremony packs → Tribe sync may deep-link the same coach. Initiative PM dashboard — Facilitate this week on the 4-week flow recovery plan panel. Ceremony packs → 4-week flow recovery deep-links the Facilitator. Initiative PM dashboard and portfolio Dashboard — Explain forecast beside the forecast strip and Audit planning integrity near the scope KPIs. Ceremony packs → PI planning prep can deep-link Planning System Integrity. Issue Detail Analyze with agent… preselects Type & Work Definition when the issue has TM/WD findings.

Where in the UI: Sidebar Assist → AI Agents. Initiative PM dashboard — Facilitate this week on the 4-week flow recovery plan panel. Ceremony packs → 4-week flow recovery deep-links the Facilitator. Initiative PM dashboard and portfolio Dashboard — Explain forecast beside the forecast strip and Audit planning integrity near the scope KPIs. Ceremony packs → PI planning prep can deep-link Planning System Integrity. Ceremony packs → This week's constraint — Where to focus (TOC) opens Constraint & Bottleneck for the same initiative (Generate executive summary remains the pack narrator). Issue Detail Analyze with agent… preselects Type & Work Definition when the issue has TM/WD findings.

Example (Type & Work Definition): DEMO-210 has TM-05 → the readout explains why a meeting should not be a Story, suggests Task wording, and links the TM playbook facilitation cue. DEMO-55 with no TM/WD hits shows a healthy-hygiene note without invented defects.

Example (Label Hygiene): The initiative snapshot has team-platform, Team-Platform, and stale PI_2025_Q4 on open DEMO-104. The report lists a distinct catalog with usage counts, a duplicate cluster with match reason case_variant + separator_variant, stale PI rows, and cross-links DV-08 / PL-09 when those findings cite the same keys. Copy the report or open Findings / Discipline — tracker labels are unchanged.

Example (Dependency / Flow Risk): Initiative SEED-PI-1 has VS-08 on SEED-104 → SEED-91. The readout cites VS-08 and those keys, offers Open in VSM, and Findings · VS-08. If there are no VS/FI findings, you see a clean-posture note and still get a VSM link.

Example (WIP & Pull Policy Coach): Finish oldest first shows SEED-104 and SEED-201 as weekly targets; Platform tribe is 8/5 (over). The coach headlines “finish SEED-104, SEED-201 first” and says Do not start new work, citing Platform over limit and FL-01. Tribe WIP numbers match the dashboard bars exactly. When AI assist is off or the language model is unset, rules-only copy still works; the Finish oldest first table itself never changes.

Example (Constraint & Bottleneck): Ceremony packs show Review as this week's constraint with CA-01. From AI Agents (or Where to focus (TOC) on the pack), the coach returns one headline constraint, evidence citing CA-01, and exploit / subordinate / elevate actions from the pack experiments — without inventing finding ids or changing WIP limits.

Example (Optimization Proposals): The same initiative has FL-01 on DEMO-104, WD-06 on DEMO-77, and BH-01 on DEMO-12. The workshop agenda lists three themed blocks (WIP/load, definition, backlog health) with those rule ids and keys. Copy a block or open Improvement actions to create an experiment manually. If only FL findings exist, WD and BH themes are omitted with an explicit scope note — no invented waste patterns.

WD-01 epidemic priority (Optimization Proposals): When WD-01: Missing acceptance criteria affects at least five scoped Story/Feature items (or at least 20% of AC-required types in scope), the agenda adds a section 0 epidemic block (definition-quality-epidemic) before numbered FL/WD/BH themes — DoR gate and batch refinement first, then the usual family blocks (still numbered 1, 2, 3…). Below those thresholds, or when WD-01 is absent, no epidemic section appears and the readout does not invent counts or issue keys.

SK (Optimization Proposals — epidémia WD-01): Pri aspoň piatich položkách bez AC (alebo ≥ 20 % scoped typov s povinnými AC) agenda začína blokom 0. Epidémia chýbajúcich kritérií akceptácie pred číslovanými témami FL/WD/BH; pod prahom alebo bez nálezu WD-01 sa epidémia nezobrazí.

Example (Backlog Readiness): Open Assist → AI Agents, select Backlog Readiness under Issue & backlog quality, and run with no issues selected (initiative scope). The readout shows how many Story/Feature items lack acceptance criteria, the % of scoped AC-required types, an epidemic flag when at least five items or 20% are affected, top project prefixes with sample keys (e.g. AKVI, BENE), a copyable refinement plan, and TQ-06 / TQ-07 text-quality counts (from persisted findings when the analysis produced them). Use Findings · WD-01 or Findings · TQ to open the matching family filter, or Issue picker · WD-01 to filter the hub table by WD-01: Missing acceptance criteria. Select a cluster → run Requirements Template for batch AC drafts. Pair with Optimization Proposals or Root Cause Synthesis when the epidemic theme appears. Copy-only — Flow Analyzer never writes AC back to Jira, ClickUp, or Asana.

SK (Backlog Readiness — batch AC): V Assist → AI agenti vyberte Pripravenosť backlogu v kategórii Kvalita issues a backlogu a spustite bez výberu položiek. Readout ukáže počet položiek bez AC, percento zo scoped typov s povinnými AC, príznak epidémie (≥ 5 alebo ≥ 20 %), top projekty s ukážkovými kľúčmi, kopírovateľný plán refinementu a počty TQ-06 / TQ-07 (z uložených nálezov, keď ich analýza vytvorila). Odkaz Nálezy · WD-01 alebo Nálezy · TQ otvorí filter rodiny; Výber položiek · WD-01 prefiltuje tabuľku podľa WD-01: Chýbajúce kritériá akceptácie. Vyberte cluster → Requirements Template na batch návrhy AC. Pri epidémii použite Optimization Proposals alebo Root Cause Synthesis. Len kopírovanie — AC sa nezapisujú do trackera.

Example (Root Cause Synthesis): The initiative has FL-07 on twelve in-progress items plus correlated WD-01 / TM-09 on DEMO-77. The agent shows 3–5 retro themes with numbered why-chains, cited FL-07 (never invented rule ids), affected issue counts bounded by the sample keys, and one experiment per theme. Copy retro Markdown for the ceremony. From Ceremony packs → Retrospective, use Synthesize root causes to open the same agent without replacing the deterministic pack.

WD-01 epidemic priority (Root Cause Synthesis): At the same epidemic thresholds, a `wd01:epidemic` theme (missing_ac_epidemic) is injected before pattern-derived themes. It cites only WD-01, includes reinforcing/balancing causal loops, a DoR-gate experiment, and playbook likely-cause text. When WD+TM correlation also supports quality_crisis, both themes may appear with distinct themeId / patternKind. Below threshold or without WD-01, no epidemic theme is added.

SK (Root Cause Synthesis — epidémia WD-01): Pri rovnakých prahoch sa téma `wd01:epidemic` (missing_ac_epidemic) vloží pred vzormi z korelácie; v retro Markdown uvidíte WD-01: Chýbajúce kritériá akceptácie, experiment s DoR bránou a slučky R:/B: v slovenčine. Téma quality_crisis môže súčasne zostať, ak korelácia WD+TM stačí.

Assist — Ceremony ritual templates (Enterprise scheduled delivery)

• Who it is for: Agile coaches and RTEs who already use ceremony packs before stand-ups, PI planning, or quarterly integrity reviews.
• Why it exists: Packs were high value but easy to forget to export before each ritual. Ritual templates turn the same analysis into a recurring operating rhythm.
• Where to find it: Sidebar Recommendations (/flow-analyzer/ceremony-packs). Three Ritual template cards sit above the coaching-session picker: Weekly constraint, PI planning prep, and Quarterly integrity review.
• How to use it: Open pack jumps to the matching in-app session (constraint focus or PI prep). Schedule ritual (Enterprise with scheduled digests) opens the report-schedule form pre-filled with digest mode Ceremony ritual, the matching ritual template, and a suggested cadence (weekly for constraint; monthly for PI / quarterly integrity). On Coach, Schedule ritual shows an honest Enterprise upgrade prompt — in-app packs and manual Markdown export still work.
• What arrives: Email / Slack / Teams get a short ceremony excerpt (title, up to eight bullets, deep link to the pack) grounded in the latest succeeded analysis run — not the standard dashboard KPI summary. Weekly constraint bullets match the in-app constraint focus for the same snapshot. Quarterly integrity includes a planning-integrity status line (healthy / strained / broken) or honest degraded copy when integrity cannot be assessed.
• Related: Manage all schedules from Results report → Schedule regular reports. Calendar OAuth is out of scope for v1.

Assist — Coaching packs

• Who it is for: Agile coaches and consultants who need one ritual Markdown artifact before a retro or leadership huddle — without stitching Brief, lean waste, Findings, and several Assist agents by hand.
• Why it exists: Ceremony packs already export session Markdown. Coaching packs compose the same evidence into a retro or leadership brief pack with deep links, optional one narrator pass, and the same gates as AI Agents.
• Where to find it: Sidebar Recommendations → Ceremony packs (/flow-analyzer/ceremony-packs). Choose Retro or Leadership brief, then Generate retro pack / Generate leadership brief pack. AI Chat offers a single Run retro pack / Run leadership brief pack bridge (skill Retro coach, or ask for a leadership brief from Flow coach). MCP clients use call_agent with agent_id: coaching-pack and template.
• How to use it: Leave One narrator pass off for rules-only Markdown (default). Turn it on only when AI-assist consent is granted — generate fails closed if consent is missing (never silently opts in). Copy Markdown from the preview. Use the chips to open Findings, constraint focus, or lean-waste Discipline. Scheduled digests are a separate Enterprise feature (see Coaching pack digests).
• Related: Pack evidence comes from the workspace snapshot (same path as Brief). There is no new card on the AI Agents hub — optional deep-link to Ceremony packs only.

Assist — Coaching pack digests (Enterprise scheduled delivery)

• Who it is for: Agile coaches and RTEs who already generate Coaching Packs in Ceremony packs and want the excerpt in email / Slack / Teams before the ritual.
• Why it exists: In-app Generate is high value but easy to forget to open before every retro or leadership huddle. Scheduled coaching packs push a short, rules-only excerpt on a cadence.
• Where to find it: Sidebar Recommendations (/flow-analyzer/ceremony-packs) — Coaching pack digests cards (Retro, Leadership brief, Tribe sync, Constraint focus) sit below the #134 ritual templates. You can also set digest mode Coaching pack (pack excerpt) under Results report → Schedule regular reports.
• How to use it: Schedule digest (Enterprise with scheduled digests) opens the report-schedule form pre-filled with digest mode Coaching pack, the matching pack template, and a suggested cadence (weekly for retro / tribe sync / constraint focus; monthly for leadership brief). You may override cadence to daily, weekly, or monthly. On Coach, Schedule digest shows an honest Enterprise upgrade prompt — in-app Generate on Ceremony packs still works.
• What arrives: Email / Slack / Teams get a Coaching pack header, up to eight grounded bullets, and a deep link to /flow-analyzer/ceremony-packs?view={template} — not the standard dashboard KPI summary. Cron never calls an LLM; full pack stays in-app.
• Related: Ceremony ritual schedules (#134) remain separate (different templates and header). Manage all schedules from Results report → Schedule regular reports.

Assist — Portfolio scope on scheduled digests

• Who it is for: PMO leads and agile coaches on Enterprise who schedule weekly digests for leadership channels and need tribe or squad slices — not an unlabeled whole-portfolio summary.
• Why it exists: Header portfolio filters already shape Brief and Dashboard. Scheduled email / Slack / Teams digests now store the same period / tribe / squad / sprint scope so Test send and cron match the slice you trust in-app.
• Where to find it: Results report → Scheduled reports. On New schedule, set Period, Tribe or squad, and Sprint, or choose Use current header scope. The table Scope column shows the saved slice (or Whole portfolio).
• How it works: Active tribe, squad, or sprint scope builds the standard digest from the same empty-scope-safe Brief/Dashboard path as the header. Those outbound messages include a Scope: line and a Brief link that keeps the matching filters (signed whole-portfolio export links are omitted while scope is active). Other digest modes keep their existing bodies without a Scope claim. Whole-portfolio schedules behave like before. Coach plans without scheduled digests still see the upgrade gate — scope does not bypass entitlement.
• Related: Global portfolio scope in the header; Automated report delivery.

Assist — Coaching packs: system-thinking bridge (#182)

Who it is for: Agile coaches and consultants who facilitate system-thinking retros and want lean waste, flow health, and root-cause patterns in one ritual pack — then track the experiment as an improvement action.

Why it exists: Even with a generated retro pack, coaches still flipped between Discipline lean waste, the Flow health radar, and Root Cause themes. Experiments in the pack did not hand off into Improvement actions, so the observe → diagnose → act loop stopped at the retro wall.

What problem it solves: Ceremony packs can generate a rules-only Retro coaching pack with a System thinking bridge (waste → health axes → pattern hints) for buckets that have evidence, plus up to three Recommended experiments from the same ranking as Brief. Create improvement action prefills title and linked rule ids; you Confirm in a dialog before anything is saved, then land on the Actions hub. Templates also include Tribe sync and Constraint focus (no AI required). Pack provenance keeps a baseline analysis run id for later verify compare.

Where in the UI: Recommendations → Ceremony packs — Coaching pack panel near the top. After Confirm, Improvement actions (/flow-analyzer/actions). Optional AI Chat read_workspace view coaching_pack_summary returns a compact grounded excerpt of bridge rows and top experiments.

Collaboration theater (/flow-analyzer/collaboration-theater)

• Who it is for: Agile coaches, Scrum Masters, and consultants facilitating live retros or cross-team reviews who need to replay who waited on whom using real ingested evidence — not a static slide deck.
• Why it exists: Ceremony packs export narrative Markdown, but a war-room retro often needs a step-by-step walk through handoffs, comments, blockers, and queue time between squads. Collaboration theater builds that replay from the workspace snapshot changelog and org roster.
• Where to find it: Sidebar Analysis outputs → Collaboration theater (/flow-analyzer/collaboration-theater). Requires the same Coach entitlement as ceremony packs.
• How to use it: Select an initiative, then use the playback rail to scrub Jira interaction steps (prev/next, keyboard arrows, or Replay). The war map highlights the active arc between teams; the Evidence sidebar shows “At this step” detail and a filterable event log. Scope down with the breadcrumb popover (epic / feature). Replay settings filter lanes (cross-team, in-team, stakeholders, shared) and adjust speed. KPI chips above the rail summarize lead time, teams/handoffs, and queue share — click a chip to focus the event log on steps up to now.
• View modes: Explore opens the Metrics tab while you scrub. Facilitate shows facilitator prompts on the war map. Workshop builds a rules-only presentation deck (Actions → Build presentation pack) with slide dots — the map jumps to each slide’s interaction. Present hides side panels and the map legend; the playback rail fades after a few seconds of idle until you move the mouse. Toggle Anonymize team names to replace squad labels with Team A/B/C for safer screen sharing.
• Bookmarks and export: Use bookmark chips (blocker moment, first handoff, longest wait) to jump to common retro talking points. Actions → Copy retro pack copies Markdown for Confluence or retro notes; Track as experiment opens Improvement actions for the current initiative.
• Related flows: Use the Open Retro ceremony pack link above the war map for Markdown talking points, or return to the Brief for weekly recommendations. From Ceremony packs → Retrospective, open Collaboration theater to replay the same initiative step by step.
• Coach marks: On first visit, a short four-step guide appears; dismiss it with Got it (stored in your browser).
• Empty state: If no interactions appear, connect Jira and run analysis so changelog history and org roster are available in the snapshot.
• Toolchain (Replay menu): Toggle Show toolchain in timeline to nest Git, Figma, CI/CD, and related connector signals under each Jira step. Use Scrub mode → All signals for flat stepping through every tool touch. Evidence filters: Jira only, Tools only, or both. Map orbit glyphs show toolchain activity at the current step.

A3 Thinking Document (/flow-analyzer/a3)

• Who it is for: Scrum Masters, Agile coaches, tribe leads, and external consultants who need a complete lean A3 worksheet for a retro, PI inspection, or leadership review — not only retro themes from Root Cause Synthesis.
• Why it exists: Root Cause Synthesis clusters 3–5 themes with why-chains, but PI and leadership forums expect the full seven-section A3 layout (background → current → target → root cause → countermeasures → plan → follow-up). The A3 document assembles that layout from Brief, findings, Root Cause Synthesis, and constraint-focus experiments in one persisted page.
• Where to find it: Sidebar Analysis outputs → A3 document (/flow-analyzer/a3). Also: Ceremony packs → Retrospective → Open A3 document, AI Agents → Root Cause Synthesis → Open full A3, and Brief → This week's one thing → Open A3 document.
• How to use it: Select the initiative, review the seven sections (derived analysis renders as formatted rich text — bold scores, bullet findings — not raw markdown), then Edit sections to workshop narrative in a TipTap editor (bold, italic, lists, headings) per section. Copy A3 Markdown still exports a coherent markdown document for Confluence or retro notes (complex HTML formatting may simplify on export). Refresh from analysis merges new derived content after a re-run; coach-authored rich-text overrides are preserved unless you opt in to overwrite per section. When analysis changes after your last refresh, a drift banner appears until you refresh or dismiss. Advisory only — Flow Analyzer never writes back to Jira, ClickUp, or Asana.
• Distinct from: Root Cause Synthesis (retro themes only), Case Study Writer (narrative genre), and Root Cause Map (causal loop canvas).

Root cause map (`/flow-analyzer/root-cause-map`): When you have at least two correlated findings, open Root cause causal loop map from the sidebar under AI Agents, Open causal loop map from the dashboard Root cause hypotheses tab, or View causal loop map after a Root Cause Synthesis run. The page renders an interactive diagram: findings, shared issues, correlation hypotheses, flow patterns, synthesis themes, and optional reinforcing/balancing loop variables.

• Diagnostic mode (default): evidence-linked graph with findings, issues, and loop variables — same trust model as before (#67).
• System dynamics (CLD) mode: facilitation canvas with frameless variables, region story cards, named loop badges (e.g. R1 · WIP spiral), +/− polarity on links, and optional ∥ delay marks when snapshot-backed dwell or blocked time exists (tooltip cites the median source — never invented days). When correlated findings support a classic pattern, an advisory archetype pill (e.g. Limits to Growth, Shifting the Burden) may appear below the loop badge — hover for rationale and cited rules; labels are heuristics, not certified system-dynamics analysis.
• Loop archetypes (advisory): In CLD mode, medium-confidence archetype pills appear under loop badges when Findings back the heuristic (WIP overflow + FL rules → Limits to Growth, quality-crisis balancing loops with WD/TM → Shifting the Burden, and similar). In Diagnostic mode, select a loop in the insight panel to read the archetype there — no canvas pill. Weak or unbacked signals show the loop name only.
• Edit map: add authored variables and causal links, drag layout, and save — persisted per workspace and initiative in Postgres (not browser localStorage).
• Drift: when analysis reruns, a banner appears until you Refresh from findings; authored workshop overlays are preserved.
• Toggle loop types and root-cause highlights in Diagnostic mode; click a node for cited rules and a link to related findings. Ranked root-cause candidates are advisory — the same trust model as synthesis text.

Example (Resource Constraint): Resource Sankey shows Adam K. at precious 0.88 (high) and Lucia P. at 0.76 (medium), with RA-01 and RA-10 in Findings. The briefing lists those scores and bands exactly, cites only those RA ids, and recommends protection actions without inventing people or recalculating RA-10.

Example (Predictor): Dashboard shows P50 14 Mar 2026 and P85 28 Mar 2026 with throughput 4.2 stories/week and VL-01 / BC-03 findings. Predictor copies those labels verbatim, explains spread and scope-added risk, and links Findings · VL/BC/SG. When no stories remain, it explains why no finish date applies instead of inventing one.

Example (Planning System Integrity): The same initiative shows scopeAdded +12 SP, 42.5% SP done, and BC-01 / SG-01 findings. The agent returns integrityAssessment: broken, cites those metrics and rule ids only, recommends refinement gate / commitment cap / mid-sprint scope policy, and deep-links Findings · BC and Findings · SG. Without AI assist consent the run fails closed; without an LLM provider you still get the rules-only assessment.

Example (Flow Recovery Facilitator): The dashboard 4-week plan shows WIP today 13 → target 4, Done target 6, and triage key SEED-104. Week 2 Facilitator cites those exact numbers, focuses on “Hold WIP limit — unblock category B,” lists control signals from the playbook, and escalate-if for zero Done by week 2 — without inventing keys or rewriting process-control severity.

Dashboard also shows a Flow health scorecard, Delivery diagnostic (system-level bottlenecks), Flow focus items (see below), and Top interventions queue so you know where to start.

Dashboard — Flow health and value over time

Open Dashboard (/flow-analyzer/dashboard) after Start here.

Assist — Findings trend chart on Dashboard and Brief (#253)

Who: PMO managers, Scrum Masters, and coaches who want to see whether finding hygiene is improving across analysis runs without exporting JSON.

Why: Comparing two run exports or scrubbing Compare tables is slow when you only need direction — are critical/high findings falling, and which rule families dominate?

What it solves: A Findings trend chart on Dashboard shows stacked finding counts per succeeded analysis run. Toggle Severity vs Family (top families plus Other). Click a run column to open Compare (what changed) when a prior snapshot pair exists, or Findings for that initiative. On Brief, a compact strip shows the same trend with View full trend on dashboard. When fewer than two completed runs exist, both surfaces show an honest empty state with Run analysis — the chart is never silently omitted.

Where: Dashboard (/flow-analyzer/dashboard) near the health-score trend; Brief (/flow-analyzer) scope/outcome area.

How to use it: Run analysis at least twice on the workspace. Open Dashboard, read the stacked series, switch Family when you want catalogue prefixes, then click the latest run to review what changed in Compare. Use the Brief strip before a ceremony to confirm direction, then jump to the full chart.

Assist — Work mix vs target on Dashboard and Brief (#260)

Who: Scrum Masters (PER-P4), tribe leads / coaches (PER-P2), and PMO (PER-P9) who need feature / bug / debt balance against plan during stand-up or Brief scan.

Why: Work-mix targets lived only in Configuration. Ceremony prep still required a Configuration tab-hop to see whether done work matched the planned capacity mix.

What it solves: Dashboard shows grouped actual vs target bars from done work in the active snapshot (scoped when portfolio filters apply). Categories that drift past the allowed threshold show a variance callout citing IT-04: Cross-Sprint Issue Type Composition Drift, with a Findings deep link when IT-04 findings exist (otherwise Configuration). Brief shows a compact strip with links to the Dashboard chart and Configuration work-mix section. If no targets are set, both surfaces show an honest empty state with Set work-mix targets — the panel is never silently omitted. Flow Analyzer does not invent mix series when snapshot data is missing.

Where: Dashboard (/flow-analyzer/dashboard → Work mix vs target panel / #work-mix) and Brief (/flow-analyzer → Work mix vs target strip). Edit targets only under Configuration → work type mix (#work-mix).

How to use it: Confirm targets in Configuration, open Brief for a 30-second scan, drill to Dashboard for the full chart and variance detail, then open Findings for IT-04 or adjust targets when drift is expected.

• Who it is for: Scrum Masters, tribe leads, product owners, and delivery managers who need to see whether the system is healthy — and whether outcomes (business value) are moving, not only how many stories finish.
• Why it exists: Story throughput answers “how many items per week?” Flow health Value delivery and the BV / week card answer “is value actually reaching Done?” Completing many small children while high-BV epics stay open is output without outcome.
• What problem it solves: A six-axis radar used to measure finding density for pace, stability, load, definition quality, dependencies, and discipline. It did not call out value-specific findings, and the KPI strip showed % BV delivered (a progress stock) without a rate. Teams could look “busy” on stories/week while BV stayed back-loaded or stuck.
• How it works:
• The Flow health radar has seven dimensions. Each starts at 100 and falls when matching findings fire (same severity penalties as the other axes). Definition quality (SK: Kvalita definície) counts WD/TM/ES families — when this axis is weak, open Assist → AI Agents → Backlog Readiness for a portfolio WD-01 readout (see Backlog readiness workflow). Value delivery (SK: Dodávka hodnoty) is penalized by BV-specific rules only: BC-08 (BV back-loaded), BC-09 (zero BV in the PI), BC-10 (BV vs count/SP inconsistency), PR-07, CO-05, IA-05, and EP-05 — not whole PR/CO/IA/EP/BC families. Pace burn-chart rules stay on Predictability; they are not double-counted. The axis is meaningful when a business-value field is mapped in configuration; if that field is missing, those rules skip and the score stays 100.
• % BV delivered remains the stock of epic business value that has reached Done (children completing does not count until the epic is Done).
• BV / week is the flow metric: business value of epics that reached Done in the last 8 weeks, divided by 8 — the same lookback as story throughput.
• Where in the UI: Dashboard KPI strip (story Throughput card, then BV / week, then % BV delivered) and the Flow health / Zdravie toku radar below the KPI cards. Expand a dimension for the calculation and View related findings.
• Example: A team finishes 4 stories/week, so throughput looks healthy. Two child stories under a high-BV epic are Done, but the epic is still Implementing — BV / week stays 0 and Value delivery may show BC-08 or IA-05. When that epic reaches Done (BV 40) in the 8-week window, BV / week becomes 5.0 (40 ÷ 8) and % BV delivered steps up. That is outcome, not item count.

Dashboard — Refinement health KPIs

Open Dashboard (/flow-analyzer/dashboard) and look for the Refinement health strip under the main KPI cards.

• Who it is for: Scrum Masters, product owners, and delivery managers who need three stable checklist numbers for refinement quality — not only scattered rule findings.
• Why it exists: Flow Analyzer already fires WD/CH/FL signals for rework, churn, and missing AC, but teams still had to infer the three consultant checklist KPIs by hand.
• What problem it solves: You can see (1) requirement rework rate, (2) decision latency (median and P85), and (3) sprint entry without acceptance criteria, each with sample size, analysis window, and evidence.
• How it works:
• Requirement rework rate = 100 × (items with a rework signal ÷ eligible delivery items). Default signals are per-issue status regression (FL-03), critical field churn (CH-10), and late or removed acceptance criteria (CH-06 / CH-19). Warning-band CH-10 does not inflate the rate; CH-05 / CH-07 stay off unless enabled in configuration. If nothing is eligible, the KPI shows an empty state — not 0%. Evidence is a sortable table of capped issue keys, signal summaries, and contributing rule ids with deep links to Findings. This KPI is not the Recommendations “quality crisis” rework wording.
• Decision latency uses configured request and decision markers (statuses, optional fields, or a comment-event proxy). Comment bodies are never read. Items with a request but no decision in the window count as open decisions and are not averaged as infinite. Missing marker config hides the KPI and links to Configuration → Workflow. Closed pairs show median and P85 in days; open rows appear separately in the sortable evidence table with request/decision dates and marker labels.
• Sprint entry without AC evaluates acceptance criteria at the first sprint-add timestamp via changelog replay (not only the current snapshot). Optional sprint-start grace hours default to 0 (related to CH-06 / CH-08 timing ideas but does not retune those rules). Drill-down shows a sortable per-sprint table and a capped evidence table (issue, sprint, add time, AC-at-add summary, optional WD-01 / CH-06 cross-links).
• Where in the UI: Dashboard → Refinement health strip; expand explanations on each card; open Findings or Configuration from the hints when needed.
• Example: Twenty eligible stories, four with FL-03 or CH-10 → rework rate 20%. Twelve closed decisions with median 2.0d and P85 5.5d, plus three open decisions listed separately. Eight sprint-adds, three without AC at add time → 37.5%, with Sprint 42 showing 2 of 5.

Sprint entry without acceptance criteria

• Who it is for: Scrum Masters and product owners who need a stable measure of Definition-of-Ready at sprint commitment — not only “missing AC now” (WD-01) or “empty at first active status” (CH-06).
• Configure: Map the acceptance criteria field under Configuration → Workflow. Types that require AC come from ac_required_types (default Story, Feature). Optional sprint-start grace hours (default 0) exclude very early sprint adds from the sample.
• Read the tile: Percentage = 100 × (issues with empty or below-minimum AC at first sprint-add ÷ issues added to sprint in the window). When nothing is eligible, the tile shows —, not 0%. When the AC field is not configured, the KPI is hidden with a link to Configuration.
• Evidence table: Sortable list of issue keys with sprint name, sprint-add timestamp, AC-at-add summary, and optional WD-01 / CH-06 finding links. Items still count when AC was filled after sprint add but before work started.

Decision latency (request → decision)

• Who it is for: Product owners and Scrum Masters who need a stable measure of how long items wait for a decision after a configured “request” signal.
• Configure: Configuration → Workflow → Decision latency markers — pick request statuses/fields and decision statuses/fields (or enable comment-event proxy). Both sides must be set or the KPI stays hidden with a link to Configuration.
• Read the tile: Median and P85 days over closed pairs only; open decisions (request without a later decision in the window) are counted separately and never averaged as infinite. When no closed pairs exist, the tile shows —, not 0d.
• Evidence table: Sortable list of issue keys with request date, decision date (or open), latency, and marker labels used. Comment bodies are never read.

How to read headline vs outcome metrics

> Metric credibility (2026-08): Phases F−1 through F3 shipped under epic #83. Brief, Dashboard, HTML/CSV export, and scheduled reports now share the same RAG, % SP done, % BV delivered, and rule-signal index for a given snapshot. Composite RAG weighs pace, BV delivery, and PI outcomes — Brief Where it burns is no longer SP-only GREEN. Flow health remains a rule-signal density scorecard (by design); compare it with outcome KPIs on the same screen. Full audit: audit-zladenie-metrik-a-vypoctov.md.

> Dôveryhodnosť metrik (2026-08, SK): Fázy F−1 až F3 sú dodané v rámci epic #83. Brief, Dashboard, HTML/CSV export a naplánované reporty zdieľajú rovnaké RAG, % hotových SP, % dodanej BV a index signálov pravidiel pre danú snímku. Kompozitné RAG zohľadňuje tempo, dodávku BV a PI — karta Kde horí už nie je len GREEN podľa SP. Flow health zostáva index signálov pravidiel (zámer); porovnajte ho s outcome KPI na tej istej obrazovke. Audit: audit-zladenie-metrik-a-vypoctov.md.

Who it is for: anyone using Start here or Dashboard for weekly syncs and sponsor readouts.

How to read the surfaces together:

Your Focus Wizard goals (G1–G8): in Guided mode they reorder Brief cards, filter findings, and boost goal-aligned recommendations — they do not change the Flow health overall number or composite RAG. Workspace default focus (F3) applies shared goal affinity on exports when configured.

Dashboard — Flow focus items

Open Dashboard (/flow-analyzer/dashboard) for a portfolio-wide read after Start here (the Brief).

Global portfolio scope (header filters)

When your workspace has more than one tribe or squad in the imported portfolio, use the portfolio scope controls in the app header (second row under the workspace name):

• Period: This quarter (default) or All time — narrows discipline-style metrics and several charts to the current quarter window vs full snapshot history.
• Sprint: All sprints (default), Current sprint, Previous sprint, or Last 2 sprints — narrows issue-level views to work assigned in those sprint windows when sprint history exists in the snapshot (Sprint field changelog).
• Tribe / squad: Whole portfolio (default), a single tribe, or one squad — filters findings, dashboards, maps, exports, and ceremony packs to issues in that slice.

How it works: scope is stored in the URL (period, sprint, tribe, team) so sidebar links keep the same filter as you move between Brief, Dashboard, Discipline, Findings, Truth gap, CFD, VSM, Initiative PM, Priority matrix, Improvement actions, Ceremony packs, Compare, Export, AI Agents, Resources, Landscape, Control chart, and related views. This is read scope (display filter on the persisted snapshot). It is separate from Run analysis ingest scope (FR-02), which controls what Jira issues are pulled on the next analysis job.

When sprint history is not configured in the workspace snapshot, the Sprint control stays disabled with a short hint — tribe/squad and period filters still work.

Period vs tribe/squad: This quarter (default) narrows discipline-style metrics, CFD window, agent run context, and — when you also pick a tribe or squad — further limits issue-level panels to work items with snapshot activity in the current calendar quarter. All time keeps full history on those metric views. Tribe/squad alone filters findings, Sankey, discipline investigation tabs, improvement actions (by linked findings), run trends, snapshot compare, and export samples to issues in that slice.

Improvement actions: when a tribe or squad filter is active, the kanban list is filtered on the server. Actions with no linked finding refs still appear so you can track squad-level experiments that are not tied to a single rule.

Compare: snapshot compare respects the same tribe/squad scope on finding deltas and issue counts.

Resources: Sankey and resource investigation honor tribe/squad scope on allocation and investigation APIs.

Control chart: the findings panel beside the chart refetches when portfolio scope changes.

Tips: leave tribe and team at all for portfolio-wide reviews; pick a tribe before a tribe sync or PI prep pack; use squad when you coach one delivery team. Org structure highlights the selected tribe in the roster chart without changing roster filters.

When a tribe or squad filter is active, the product separates three lenses so the numbers do not contradict each other:

• Rule-signal / flow quality (Brief risk card primary when filtered — flow health /100; Findings; Dashboard flow health) — hygiene and hierarchy-problem density for the selected slice. This is the headline on RIZIKO under a tribe/team filter, not a lone initiative-wide GREEN badge.
• Scoped delivery (Brief risk evidence line + HTML/Markdown executive summary) — pace, forecast, and blockers recomputed on that slice only, labeled as slice delivery (for example “BENE delivery pace: GREEN (96% SP done in slice)”).
• Initiative delivery (secondary Brief line + export secondary line; Dashboard RAG footnote) — whole-initiative pace and RAG unchanged; sponsors still see whether the full initiative is on track.

Many hierarchy “problem” rows in a squad view can coexist with a green scoped or initiative RAG — they measure process noise in the slice, not portfolio completion pace. HTML and Markdown Executive summary use the same dual-lens Brief model (process + scoped pace + initiative), so an export cannot show only an unlabeled initiative GREEN while Findings show many hierarchy problems.

If the filter matches no issues (or the slice has no delivery sample), Brief and export stay empty-scope safe: forecast stays unavailable, and the primary risk copy says there is no work in that scope — it does not present parent-initiative GREEN as “all clear.” Reset Tribe and Team to all for the classic initiative-wide risk card.

• Who it is for: Scrum Masters, tribe leads, and coaches who need one ranked list of which issues to unblock first—not only which rule families fired.
• Where it sits: below Delivery diagnostic and above Findings insights (top findings by rule and interventions).
• What it shows: up to fifteen work items sorted by a focus score that combines cycle time (CT), lead time (LT), dwell in the dominant workflow stage, rule signals (for example OL-01, CT-06/07, IA-05, blocked dependencies), downstream impact, and whether the issue is new since the last analysis.
• Columns: item (with parent feature/epic), tribe, CT, LT, dominant stage with dwell days, signal tags, and score. Click an issue key to open the issue detail panel.
• Context line: above the table, a short summary names the longest portfolio stage, this week’s constraint (when available), and the analysis scope and date.
• HTML report: the same ranked table appears in the Flow focus items section of the initiative HTML report (after executive summary and Reporting gap), so stakeholders see the same priorities without opening the app.
• How to use it: start with the top three rows in your next stand-up or refinement; cross-check Findings and Value stream map when you need rule evidence or dependency context. This view complements findings-by-rule—it does not replace the control chart or full findings list.

Dashboard — Finish oldest first

Open Dashboard (/flow-analyzer/dashboard) and scroll to Finish oldest first (below Flow focus items).

• Who it is for: Scrum Masters running a stop-starting, start-finishing week.
• Why it exists: Age in a workflow stage is the ranking; story-point size is the glanceable extra so you do not pull a 40-point item into a “finish three this week” goal by accident.
• What problem it solves: A raw 3 in the SP column is easy to miss next to dwell days. Colored planning-poker cards (the same Fibonacci values teams hold up: 0, ½, 1, 2, 3, 5, 8, 13, 20/21, 40, 100) make size pop without opening the issue.
• How it works: each estimate is a compact colored card in the SP column. Missing estimates stay as an em dash — no placeholder card. Colors reuse the product status/BV palette (green, teal, blue, purple, amber, orange, red) rather than a second invented rainbow.
• Where in the UI: Dashboard → Finish oldest first table → SP column. Pick a stage, then finish the top weekly-target rows before starting new work.

Did it work? — outcome verification

Improvement actions now close the loop by themselves. When you create an action, FlowAnalyzer records

the analysis run you are improving from (the baseline). When you move the action to Done, it

waits for the next completed analysis run and compares the rule hit counts behind the action's linked

findings between the two runs.

The verdict appears as a badge on the Done column and in the action's detail panel:

Verdicts are derived from the same rule engine that produced the findings, so an action's outcome is

evidence, not an opinion. Actions with no linked findings show no verdict — there is nothing to measure.

Navigation: Start here first

The sidebar is ranked in two tiers.

• Start here (the Brief) and Dashboard sit at the top, visually separated. Start here answers five

questions in about thirty seconds: how healthy you are, this week's one thing, what to do, what changed,

and where it burns. After Your goals (when set), the Trust panel compares delivery outcomes to

rule-signal scores so GREEN headlines cannot silently mask a delivery crisis. Above the card grid, Open sprint diagnostic jumps to a sprint-scoped strengths →

#1 blocker → fix screen for retro evidence (This sprint in the sidebar).

• Global portfolio filters in the header (Period, Sprint, Tribe, Team) scope analysis views that honor

the URL parameters. Brief, Dashboard, Discipline, Findings, and Truth gap narrow findings

(and related metrics where wired) to the selected tribe or team. Sidebar links and the Analytics hub keep

those filters in the URL as you move between screens.

• Analysis outputs (always visible) holds reporting gap, discipline, priority matrix, improvement

actions, ceremony packs, and the results report.

• Assist (always visible, below Analysis outputs) holds AI Agents.
• All analysis holds everything else — findings, control chart, value stream map, cumulative flow,

plus the portfolio views (Portfolio, Org structure, compare imports) and map views. It stays open

once you have used it, so returning users keep their depth. Open All analysis → Portfolio → Org structure

to edit tribes, squads, people, and FTE for the active workspace.

Breadcrumbs at the top of each screen show the path you took and let you step back up. Collapsing the

sidebar keeps group boundaries and shows each item's name on hover.

Sprint diagnostic (Maria mode)

Who it is for: Scrum Masters preparing standups and retros who need one sprint-scoped answer — not a KPI grid tour.

Why it exists: Stop synthesizing Brief, Dashboard, Findings, and VSM by hand. The screen shows measured strengths (when changelog dwell exists), one named blocker with RULEID: RULETITLE and issue-key evidence, and one primary fix with handoffs.

Where to find it: From Start here, use Open sprint diagnostic, or open This sprint in the sidebar (/flow-analyzer/sprint-diagnostic). The page defaults to Current sprint; change the header Sprint chip to recompute for previous / last 2 sprints (same portfolio scope as #91).

How to use it: Read strengths first, then the #1 blocker and fix. Create an improvement-action draft (not auto-saved), open the retro ceremony pack, copy Markdown for retro, or drill into Findings. Freemium orgs see the same partial-scan banner as the Brief.

Initiative PM — history playback

Open Initiative PM (/flow-analyzer/initiative/{initiativeId}) to review hierarchy, timeline bars, and bottom charts for one initiative.

• Who it is for: initiative owners and PMs who want to see how scope, status markers, and charts evolved from changelog history—not only the current snapshot.
• Play history: use Play history above the hierarchy tree. The shared playhead scrubs across the tree, SVG timeline (orange dashed line), and bottom charts.
• Controls: play/pause, speed (default 1 calendar day = 1 real second), step back/forward per changelog keyframe, date scrubber, and Jump to date.
• Charts: while playback is on, CFD / BV / scope replay from changelog buckets; static charts return when you stop playback. BV and scope show an orange playhead cursor.
• Note: inner bar fill (% time spent) does not replay worklogs in v1—the legend explains that values stay at the snapshot baseline.

Initiative PM — average time in workflow stage

Below the status workflow strip, Average time in workflow stage shows how long issues in this initiative typically stay in each Jira status column.

• Who it is for: RTEs, tribe leads, and coaches asking where work waits longest before you change WIP limits or swarm a stage.
• What it shows: a bar chart of average dwell hours per workflow status, ordered by your workspace workflow stage order when configured. Statuses outside the configured order appear in gray after the main flow.
• Data source: changelog-derived dwell from the workspace snapshot (same signal as rule FL-06). The chart appears only when status history exists; otherwise you see a short empty-state message.
• How to use it: compare the tallest bars across columns—often Review or Test—to the status strip WIP counts above. A tall bar plus high WIP usually marks the system constraint for that initiative.

Value stream map — measured cycle time

On Value stream map (/flow-analyzer/vsm), node badges show cycle time and age from your snapshot when changelog metrics exist for that issue.

• Who it is for: initiative owners tracing blockers who also need how long items have been open or in flow—not story-point estimates.
• When numbers are real: after live ingest or import with status history; values come from the same persisted timing used on Initiative PM.
• Fallback: if an issue has no dwell or cycle metrics, the map uses a lightweight estimate from story points and status so the layout still renders.

Value stream map — value stream layout (tribe × stage)

On Value stream map (/flow-analyzer/vsm), use the toolbar toggle Value stream (next to Hierarchy) to switch from the dependency graph to a tribe × workflow stage grid.

• Who it is for: RTEs and tribe leads who want a classic lean-style view of where work piles up by team and column—not only hierarchy blockers.
• Each cell shows: WIP count (corner), average dwell days in that status, a queue vs active split bar (non-active vs active_statuses from workflow config), a small throughput sparkline (items leaving the stage per week), and an amber bottleneck tint when recent inflow/outflow exceeds config.cfd.bottleneck_ratio.
• Drill-down: click a cell to open a drawer listing issue keys in that tribe and stage.
• Data source: persisted workspace snapshot (same changelog replay as FL-06 / CFD rules). The toggle stays disabled until snapshot dwell metrics exist.

Initiative PM — stage timing ladder

Below Average time in workflow stage, the Stage timing ladder shows wait vs active dwell along your configured workflow stages, plus P50 lead/cycle summaries and up to three sample story segment rows.

• Who it is for: coaches explaining where time is queue vs touch before changing WIP policies.
• Data source: aggregated timeInStatusSeconds from the workspace snapshot, classified using active_statuses.

Initiative PM — blocker and dependency network

On Initiative PM Overview (/flow-analyzer/initiative/{initiativeId}), below the flow timing charts, the Blocker and dependency network shows a compact graph of blocker and depends-on links among scoped issues — without opening the full value stream map for every stand-up.

• Who it is for: tribe leads (PER-P2), Scrum Masters (PER-P4), and initiative owners (PER-P9) who need VS / RA blocker chains visible during stand-up or ceremony prep.
• Why it exists: Full Value stream map is the canonical topology tool, but it is heavy for a daily drill. This lite panel answers “what blocks what in this initiative?” in one glance.
• What it shows: real issue keys from your workspace snapshot, edges taken from the same dependency / blocker links as the initiative graph (never invented). Nodes with VS- or RA- findings get a red ring; selecting a node lists citations as RULEID: RULETITLE with a deep link to Findings** (VS + RA families, filtered by issue key). The longest blocker chain in the capped subgraph is highlighted.
• Cap: at most 40 nodes (highest risk first). When more blocker-linked nodes exist, the panel shows how many are shown of the total and offers Open full VSM.
• Empty state: when there are no blocker or depends-on edges in the blocked-only scope, you see honest empty copy and the same VSM CTA — no fake nodes.
• Open full VSM: keeps the initiative scope, turns on blocked-only filtering, and focuses the selected node when one is selected.
• Data modes: empty, seed, and live snapshots only (PRD §4.6) — no mock graph series.

Initiative PM — takt vs delivery rate

When the initiative has PI commitment data (piHistory with committed story count), the Takt vs delivery rate panel compares committed demand (stories per week) with trailing throughput from the snapshot.

• Who it is for: RTEs checking whether delivery pace matches PI commitment without inventing demand numbers.
• Roster capacity band: when Org structure squads define Sprint capacity (SP), the same panel adds a flat roster sprint capacity line (weekly story points) alongside completed SP from the snapshot — even when PI commitment is absent. Purple = weekly done SP; dashed green = summed squad capacity (default 2-week sprint assumption).
• Empty state: when neither PI commitment nor squad SP capacity is configured, the panel explains what is missing; no fake takt line is shown.

CFD and control chart — live snapshot replay

Cumulative flow (/flow-analyzer/cfd) and Control chart (/flow-analyzer/chart) prefer changelog replay from your workspace snapshot when one exists, falling back to seed interpolation only when snapshot metrics are unavailable.

• Who it is for: flow coaches who need charts aligned with rule-engine CFD/CA signals, not demo curves alone.
• How it works: the initiative dashboard API enriches CFD series from persisted snapshot WIP-by-stage replay; the control chart page merges completed-issue cycle times from snapshot(s) across initiatives in scope.
• Process control metric (6 weeks): below the CFD chart, the Process control stat card checks the last six weeks for at least one week where Done rose week-over-week and Implementing WIP stayed below 8 (the same WIP-limit threshold used in batch-size coaching). Pass means process changes on this board can work; Miss means capacity or priorities outside the board are the more likely constraint. Use it after a WIP-limit or finish-first experiment to falsify whether the bottleneck is on-board workflow vs off-board demand.

Assist — Cycle time distribution histogram on Charts (#251)

Who: Agile coaches (PER-P2), Scrum Masters (PER-P4), and consultants (PER-P5) who explain tail latency and cycle-time variability in retros or client reviews.

Why: The Control chart shows points over time, but coaches still sketch histograms for P50/P85 tails and CT/CC stories. A distribution tab keeps that exhibit next to the scatter without leaving Charts.

What it solves: On Charts, open the Cycle time distribution tab to see completed-item cycle times in day buckets (3 / 5 / 7 day widths), with P50 / P85 / P95 text chips and dashed overlays on the bars (plus bar counts so encoding is not colour-only). When the snapshot has created→done lead fields, switch to Lead time; otherwise the lead control stays disabled with honest copy — Flow Analyzer never invents lead days from cycle time. Related CC- and CT- findings appear as RULEID: RULETITLE links into Findings. With fewer than five completed items, the tab shows insufficient-data copy and no fake bars**.

Where: Charts (/flow-analyzer/chart) → Cycle time distribution tab (same control-chart source as the Control chart tab when a persisted snapshot is preferred).

How to use it: Start on cycle time with the default 5-day buckets; change bucket width to re-bin the same issues; compare P85/P95 to outliers you already see on Control chart; open a cited CT/CC finding when the insight strip lists one.

Assist — Estimation calibration scatter on Charts and Discipline (#256)

Who: Agile coaches (PER-P2), Scrum Masters (PER-P4), and PMO readers (PER-P9) who run sizing retros and need estimate-vs-actual evidence instead of “we always underestimate” anecdotes.

Why: Estimation tables and ES-* findings exist, but coaches still sketch scatters offline. A Chart tab (and Discipline embed) keeps the workshop exhibit next to control-chart and cycle-time views.

What it solves: On Charts → Estimation calibration, completed issues with both estimate and actual appear as scatter points keyed to real issue keys on hover. With ≥10 points, under / calibrated / over bands render (fill + hatch + labels) using ratio thresholds 0.75–1.25; with fewer points, bands stay off and insufficient-data copy shows the count — no fake fills. Prefer same-unit pairing (hours vs logged hours when available); when units differ (for example story points vs cycle days), ratio bands may still appear as exploratory while the y=x diagonal stays hidden with an honest note. Related ES- findings cite `RULEID: RULETITLE` and deep-link Findings (family ES). Team distinction uses colour and shape. Empty / seed / live snapshots only — never mock series. The same panel appears in Discipline Investigation* estimation content under portfolio / team / tribe scope (#91).

Where: Charts (/flow-analyzer/chart) → Estimation calibration tab; also Discipline (/flow-analyzer/discipline) Investigation estimation section.

How to use it: Open the tab on TestWorkspace seed or a live snapshot; hover points for issue keys; when bands appear, discuss under/over clusters in the sizing retro; open cited ES findings; apply portfolio scope when comparing one tribe or team.

On the Initiative dashboard, the same check appears as a panel below Finish oldest first, with a link to the CFD screen.

4-week flow recovery plan appears on the dashboard (after process control), in ceremony export (flow_recovery_4w), and in Výsledná správa HTML — baseline from CFD, numeric targets, implementing triage with issue keys, weekly steps, and control signals. All numbers come from the workspace snapshot (no AI).

RTE decision checklist (VSM timing)

Who this is for: coaches and delivery leads reviewing the latest analysis for the active workspace.

On Findings (/flow-analyzer/findings), filter by severity, rule family, and search text. Use Operational defect funnel to focus on the Operational Issues (OI) family (including environment-related evidence when present). Expand Discipline investigation on the same page for gate bypass, requirement coverage, epic DoD, PI delivery, flags & blockers, operational bucket, multi-project portfolio, and Lean waste tables without switching screens.

On Discipline (/flow-analyzer/discipline), the score overview shows one circle per domain. When the dashboard has DV findings loaded, each domain uses DV severity only when that domain has active rules in Findings; domains without DV coverage show the timeline proxy in the circle with an amber note so a misleading 100 does not appear. The structural signal under each card (for example undecomposed features) always comes from the timeline proxy. The scorecard tabs (Assignment, Mandatory Fields, Planning, Continuous Update, Decomposition) use the reconstructed initiative tree from the workspace snapshot. Story and Bug issues linked directly under an Epic (not only Epic → Task → Story) are now included in that tree. When some scoped issues still fall outside the reconstructed shape (for example Sub-tasks), a Partial hierarchy coverage banner appears on the score overview and Investigation tab — open Findings for full issue-level coverage. Assignment lists stories in an active workflow status with no assignee (using workspace active statuses when configured); when assignees are missing from the feed, empty timelines are used as a stand-in. These cards are timeline proxies — a domain score of 100 means no gaps under that narrow definition, not that every Jira issue is assigned or that mandatory fields match DV-05/DV-06. Prefer Findings (DV family) and Investigation when coaching ownership and field completeness. See also How to read conflicting signals. Open the Investigation tab for gate bypass, coverage, epic DoD, PI delivery, Flags & blockers, Operational buckets, Multi-project, and Lean waste at full width. The Flags & blockers tab shows a calendar timeline of flagged intervals and open blocker links with age bands; select a row for FI findings cited as `RULEID: RULETITLE` and Findings deep-links. The Operational buckets tab lists catch-all tracker issues (for example Prevádzka or Operativa umbrellas) with an operational noise impact chart (open children / open child SP / injection window), optional OI-07 with/without cycle-time strip, open child counts, recent child injection, and monthly growth slope. The Multi-project tab surfaces cross-project gate bypass, blocker aging and blocker chain integrity, parent–child coherence, DoD evidence gaps, PI label stack, description-versus-decomposition gaps, clone continuations, clone PI rollover, and remote link churn when the snapshot spans multiple delivery projects under shared parent initiatives. The Lean waste tab helps coaches review behavioural waste patterns by waste type (related catalogue rules and sample keys) and optionally filter samples to parent initiatives or delivery-level work. Issue detail overlays include a Links section for clone, covered-by, and blocking links with status badges when the snapshot has issue links.

Assist — Blocker and flag aging timeline (#252)

Who it is for: Scrum Masters (PER-P4), Agile Coaches / RTEs (PER-P2), and PMO readers (PER-P9) who need to escalate stale flags and blockers before they silently age out of sprint attention.

Why it exists: Findings list FI-* flag-lifecycle rules, but duration is invisible — coaches rebuild timelines in spreadsheets for retros.

What problem it solves: A blocker and flag aging timeline on Discipline Investigation shows each flagged interval and open Blocks / is-blocked-by relationship on a calendar axis. Bars use age bands (0–7 / 8–14 / 15–30 / 30+) with colour and hatch so severity is not colour-only. Select a row to see FI findings cited as `RULEID: RULETITLE` with deep links into Findings (family FI, plus rule or issue filter). Missing flag-field mapping shows a configuration banner — no fabricated flag bars; open blocker-link rows may still appear. More than 50 intervals are capped with a Findings overflow link.

Where in the UI: Discipline (/flow-analyzer/discipline) → Investigation → Flags & blockers.

How to use it:

1. Open Discipline Investigation with the active workspace snapshot (seed or live).
2. Open Flags & blockers and scan the longest bars first (sorted by age).
3. Select a stale bar → review FI citations → open Findings to coach the issue.
4. Apply portfolio sprint / tribe scope when needed — the timeline uses the same scoped issue keys as other investigation filters.

SK — Časová os starnutia blokátorov a vlajok: Disciplína → Vyšetrovanie → Vlajky a blokátory. Pruhy = intervaly vlajok a otvorené blokujúce odkazy; legenda pásiem veku; výber riadku → citácie FI a odkazy do Nálezov.

Assist — Operational noise impact chart (#255)

Who it is for: Agile Coaches / tribe leads (PER-P2), PMO analysts (PER-P9), and consultants (PER-P5) who need to separate operational-tracker catch-alls from genuine delivery WIP before coaching on cycle time or metric integrity.

Why it exists: Discipline Investigation already computed operational bucket rows and OI signals, but coaches still missed them in a visual scan — the thin open-children bar did not expose metric toggles, OI-07 distortion, or catalogue citations.

What problem it solves: An operational noise impact chart on the Operational buckets tab shows horizontal bars for open children, open child story points, or children created in the injection window — always from the same snapshot rows as the table below. When OI-07 detects significant cycle-time distortion, a workspace impact strip shows with/without averages (omitted when below threshold — no fake zeros). Select a bucket to see related OI- rules cited as `RULEID: RULETITLE`* with Findings deep-links (families=OI, optional issue-key query). Empty snapshots show honest empty copy; explicit empty operational keywords show a Configuration banner without inventing buckets.

Where in the UI: Discipline (/flow-analyzer/discipline) → Investigation → Operational buckets.

How to use it:

1. Open Discipline Investigation with the active workspace snapshot (persisted SaaS preferred; seed or live also fine).
2. Open Operational buckets and scan the longest bars (default: open children).
3. Switch series to open child SP or created-in-window when the coaching question is about estimate load or injection rate.
4. If the OI-07 strip appears, treat metric charts elsewhere as potentially inflated by trackers.
5. Click a bar → review OI citations → open Findings filtered to the OI family (and that issue key when selected).
6. If keywords were cleared in Configuration, follow the banner to restore vocabulary for honest detection.

SK — Graf dopadu prevádzkového šumu: Disciplína → Vyšetrovanie → Prevádzkové buckety. Stĺpce = otvorené deti / SP / vkladanie; prepínač metrík; pás OI-07 pri významnom skreslení; výber bucketu → citácie OI a odkazy do Nálezov.

Assist — PI commitment reliability chart (#258)

Who it is for: RTEs / tribe leads (PER-P2), PMO managers (PER-P9), and consultants (PER-P5) who need committed versus delivered reliability per Program Increment without spreadsheet pivots.

Why it exists: Discipline Investigation already computed PI commitment rows, but RTEs still exported CSVs for PI Inspect & Adapt because the chart lacked reliability trend, metric toggles, and drill-down to snapshot issue keys.

What problem it solves: A PI commitment reliability chart on the PI delivery tab shows grouped bars for committed versus delivered story points (or issue counts) per PI label, with a delivery reliability % trend line when two or more PIs are present — always from the same piCommitment payload as the sortable table below. Click a PI column to see up to five snapshot issue keys, PR-04: Quarterly Planning Advisory (PI Level) context, and a Findings deep-link filtered to the PR family (with the first sample key when a PI is selected). Single-PI snapshots show bars and % only — no fake trend. Missing PI labels show honest empty copy and a Configuration planning link.

Where in the UI: Discipline (/flow-analyzer/discipline) → Investigation → PI delivery.

How to use it:

1. Open Discipline Investigation with the active workspace snapshot (persisted SaaS preferred; seed or live also fine).
2. Open PI delivery and compare committed versus delivered bars across PI labels.
3. When two or more PIs exist, read the orange reliability % line against the right axis.
4. Toggle Story points versus Issue counts when the coaching question is about throughput volume rather than estimate load.
5. Click a PI bar → review sample issue keys and reliability % → open planning Findings for the PR family.
6. If no PI series appears, follow the Configuration link to map the Program Increment field — never expect zeroed fake PIs.

SK — Graf spoľahlivosti PI záväzkov: Disciplína → Vyšetrovanie → PI doručovanie. Stĺpce zaviazané/doručené SP alebo issue; trend % pri ≥2 PI; výber PI → až 5 kľúčov + nálezy PR.

Assist — PI commitment reliability chart (#258)

Who it is for: RTEs / tribe leads (PER-P2), PMO managers (PER-P9), and consultants (PER-P5) who need committed versus delivered reliability per Program Increment without spreadsheet pivots.

Why it exists: Discipline Investigation already computed PI commitment rows, but RTEs still exported CSVs for PI Inspect & Adapt because the chart lacked reliability trend, metric toggles, and drill-down to snapshot issue keys.

What problem it solves: A PI commitment reliability chart on the PI delivery tab shows grouped bars for committed versus delivered story points (or issue counts) per PI label, with a delivery reliability % trend line when two or more PIs are present — always from the same piCommitment payload as the sortable table below. Click a PI column to see up to five snapshot issue keys, PR-04: Quarterly Planning Advisory (PI Level) context, and a Findings deep-link filtered to the PR family (with the first sample key when a PI is selected). Single-PI snapshots show bars and % only — no fake trend. Missing PI labels show honest empty copy and a Configuration planning link.

Where in the UI: Discipline (/flow-analyzer/discipline) → Investigation → PI delivery.

How to use it:

1. Open Discipline Investigation with the active workspace snapshot (persisted SaaS preferred; seed or live also fine).
2. Open PI delivery and compare committed versus delivered bars across PI labels.
3. When two or more PIs exist, read the orange reliability % line against the right axis.
4. Toggle Story points versus Issue counts when the coaching question is about throughput volume rather than estimate load.
5. Click a PI bar → review sample issue keys and reliability % → open planning Findings for the PR family.
6. If no PI series appears, follow the Configuration link to map the Program Increment field — never expect zeroed fake PIs.

SK — Graf spoľahlivosti PI záväzkov: Disciplína → Vyšetrovanie → PI doručovanie. Stĺpce zaviazané/doručené SP alebo issue; trend % pri ≥2 PI; výber PI → až 5 kľúčov + nálezy PR.

Excessive commenting (DV-30 / DV-31)

Who this is for: coaches and team leads who see people spending a lot of time writing Jira comments that do not move the work forward (goldplating or “cover yourself” notes).

What problem it solves: Some teams under-document (caught by DV-18 — no comments on long-running work). The opposite waste is also common: many comments on a ticket with little status or ownership progress. Flow Analyzer measures comment event counts and timestamps only — it never reads comment text.

How it helps:

• DV-30 — Excessive Comment Activity on Issue flags a delivery-level story/bug/task when comment volume is high relative to age and to delivery field changes (status, assignee, estimates, sprint, resolution). Issues with an active impediment flag use a higher threshold so legitimate blocker threads are less likely to fire.
• DV-31 — Excessive Comment Volume by Author flags a person who either owns a large share of all comments in the snapshot or leaves many comments across many issues.

Where to find it: open Findings or the Rules catalogue, filter by the Discipline family, and look for DV-30 / DV-31. Sample issue keys appear on findings so you can open the tickets in Jira and coach toward shorter decision notes or moving status instead of comment sprawl. On Lean waste (Extra processes), the same issue keys may appear as samples when those rules fire.

Continuous update cadence (Discipline timeline proxy)

Who this is for: Scrum Masters and coaches who want teams to update Jira throughout active work — not only in a Friday batch or only at the start/end of a ticket.

What problem it solves: A story can have some comments or field changes and still be a poor living document if updates arrive in long silent gaps, in a burst on many tickets at once, or only when the item is about to close.

How it helps: On Discipline, the Continuous Update domain score and tab now measure cadence, not only whether any status, field, or comment marker exists:

• Per story: longest gap between engagement markers, concentration at the start or end of active work, and irregular intervals between updates.
• Per team: batch patterns when many active issues are updated in the same short time window.

Rows in the Continuous Update tab explain the pattern (for example end-loaded updates or a long gap). When DV findings are available for this domain, the card may also show a findings-based score — use both when coaching.

Where to find it: /flow-analyzer/discipline → Continuous Update tab and the Priebežná aktualizácia domain card in the score overview. When DV findings are loaded, DV-32 (weak cadence per issue) and DV-33 (team batch update pattern) appear under the Discipline family in Findings.

Configuration: open Configuration → Discipline to tune continuous-update cadence thresholds (expected cadence days, gap warn and critical days, batch window and minimum issues, list score threshold, minimum active days, and pattern-detection knobs).

Jira export import workspaces

Some organizations use `jira_export` workspaces when live Jira API access is unavailable or when you want a one-time portfolio upload.

1. In Organization settings, open a workspace and set Type to `jira_export`, then Save workspace.
2. On the workspaces table, use Import data on that row (or Import Jira export… from Workspace details).
3. Choose the export format that matches the files:

• Jira printable export — printable HTML per issue, native history.txt (Name made changes), optional navigator CSV and RSS.
• Per-issue folder export — folders such as epics/KEY/, features/KEY/, initiatives/KEY/ with KEY.html, KEY_history.txt (JIRA HISTORY EXPORT table), and KEY_changelog.json.

1. Choose ZIP or Folder:

• ZIP (recommended for large exports): a single archive of your export tree. The server stores the ZIP and extracts it during the background import job — fastest upload path.
• Folder: select the extracted folder; the browser zips files first, then uploads one archive (slower for large trees).

1. After you start the import, a progress bar in the import panel and in the corner notification tracks upload and each processing step (queued, parsing files, running rules). When the job finishes, the workspace snapshot refreshes and rules run. Results use initiative scope `import-ws-{workspaceId}` for the whole portfolio.

Import and ingest scale limits

Who: Organization admins and operators configuring SaaS workspaces.

Why: Large Jira exports and live ingests run as background jobs. Caps keep uploads predictable and protect shared infrastructure.

What you see: If an export contains more issues than your deployment allows, the import job fails with a clear error in the import panel and job status — split the export or ask your operator to raise the cap.

Default limits (2026-08, NFR-02 M4 spike):

Operators tune caps with FLOW_ANALYZER_IMPORT_MAX_ISSUES (import) and FLOW_ANALYZER_TENANT_INGEST_MAX_ISSUES (live ingest). Flow Analyzer engineering has verified synthetic normalize up to 50 000 issues offline; supported SaaS tier remains 5000 issues per job until product and operations explicitly raise it. See `performance-nfr-scalability.md` for spike data.

On the first successful import of a SAFe-style printable export (for example POIT/ENRL issue keys or Dovera DoD custom fields), Flow Analyzer can automatically apply the SAFe portfolio Jira export preset when the workspace still has the factory default configuration. User-edited or previously saved presets are never overwritten. You can still apply or adjust the preset manually from Organization settings → workspace → SAFe portfolio Jira export preset.

What findings appear after import

Import workspaces run the same rule catalogue as live Jira and seed-demo workspaces. Signal builders on the saved snapshot feed cycle time, DoD checklists, acceptance criteria, worklogs, sprint scope, value-stream links, and chart series (control chart / CFD) into the analysis run.

In practice you should see a broad mix of families on a rich export (for example DoD DG, content history CH, discipline DV, pipeline PL, operational OI, and flow FL / SP), not only a handful of hygiene rows. Seed-demo workspaces share the same pipeline and produce a solid baseline of findings even without Jira.

Charts and side panels (control chart, CFD) use the same snapshot context, so engine findings stay aligned with what you see on the chart screens.

Re-importing creates a new snapshot row (merge mode) or clears prior data (replace mode). On the import workspace settings panel, use Import snapshot history to pick a past snapshot and save a bookmark label (for example Pre-coaching or Post-PI-2). Use Compare imports in the sidebar to prove what improved or regressed between two snapshots.

One narrative for what changed (Brief, Compare, digest)

After you have at least two analysis snapshots, Flow Analyzer tells the same “what changed” story everywhere:

• Brief home card What changed? — up to three narrative lines (regressions, improvements, and integrity findings when metric-integrity families MI/CH/TI/GOV/DQ appear or worsen), plus a link that opens Compare with that snapshot pair pre-selected.
• Compare imports — a short narrative header above the sortable tables uses the same lines and counts for the pair you select (not only the two newest).
• HTML / Markdown report — Executive summary What changed block matches the Brief delta lines for that pair.
• Enterprise weekly delta digest (scheduled email / Slack / Teams) — the same narrative lines when digestMode is weekly delta. Coach plans still see the in-app Brief narrative; automated digests require the Enterprise scheduled-digests entitlement.