Insights

An insight is a judgment about your system that is hard to check by hand: what has no fallback, what is a single point of failure, what is worth protecting. Most insights are written by a model running an analysis, so two runs can notice different things.

Dependencies is the other half: it shows what is connected, and the same boards always give the same result. An insight says what it means.

What an insight is

Most insights come from running an insight skill over a board's scope. Each run produces a batch of insights, each anchored to the nodes and edges it concerns. A batch only groups them: it has no title, report or narrative of its own.

Open an element to see its insights. For a batch from chat, the conversation carries the narrative; after a plugin push, each insight is read on its own. Insight Skills covers authoring skills.

The four signals

Every insight has a signal that says what kind of thing it is:

Strengths show what to protect when you refactor.

How an analysis starts

Start an analysis from chat in the portal, or from a plugin:

• /insights and /monitor in the code plugin, from a repo.
• /assess in the workspace plugin, from your AI host.
• /discover in either plugin. This graph-first pass files its insights under the Architecture Highlights skill and draws context boards beside them.

There is no Run button on the canvas. The plugins run inside your coding or AI session and don't need a connected model provider. Chat runs on trial credits or on a connected model provider.

Insights from Sentry

When a Sentry project is bound to an app board, new and regressed Sentry issues arrive as draft insights every hour. Each one sits on the app's node on the board above the app board, tagged sentry and linked to the issue. Automations covers which issues qualify and how their priority is set.

Insights from Dependencies

A route found in Dependencies can be kept as an insight with Save as insight. Its trail is the route, as it stood when you saved it. It counts as one you wrote: it is approved on arrival, belongs to no batch, and can be edited. To ask the same question of the boards as they stand now, select Ask this again in the header of the open insight.

The Insights Bar

The Insights Bar lists a board's own insights, most urgent first, and counts how many more sit below it in the tree. On the root hub, the Insights card rolls up insights across the whole tree, newest analysis first.

Expand

1. 1

   Search and category

   Search matches every word you type; the category picker narrows the list to one skill, Ad-hoc analysis or Hand-authored.

2. 2

   Skill

   Each row names the skill that produced the insight.

The list loads more insights as you scroll. While a search or a category is set, the count of insights below this board in the tree is hidden, because those insights aren't searched.

Reading an insight

Each row in the Insights Bar names the skill that produced the insight. An insight whose trail only passes through this board names the board it comes from, and at equal priority it sits below the ones that start here.

An insight can also carry suggested graph changes: structural proposals with their reasoning attached.

To post an open insight to a Slack channel, click the Slack icon in its header; you can add a note. See Share to Slack.

From an insight to a work item

When you agree with an insight, open it and select Create work item in its header. A developer can then pull the work item into the repo with the analysis attached.

Under Which apps does this change?, the app the insight sits in is already ticked. The apps its trail passes through are listed beside it. Add another app… finds any other app in the workspace. Each app you tick gets its own work item, because each repository pulls only its own work. With more than one app ticked, the work items share an Epic: a new one named after the insight, or one you choose. The first new draft opens when you select Create work item.

If the insight already has work items, they are listed under Already linked, and the button reads Create another. An insight on the root board that no app contains has nothing ticked: choose the app where the change happens.

You can also ask in chat to turn insights into work items. ProvenMap drafts them and asks for your approval before creating them.

Review status

Each insight carries its own review status, independent of the rest of its batch: Draft, Ready, In Review, Approved, then Published or Archived. Insight Skills explains what each state means.

A Slack automation with High-priority insights ticked posts to its channel when an analysis finds critical or high-priority insights. See Automations.

Where to go next