Follow-ups and decisions

A finding is one thing on one agent that needs a decision from your team: a change nobody has explained yet, for example. A decision is the next step your team chose for it, who owns it, and when to look again. Morse keeps both, with the numbers as they stood when the finding opened and what the numbers showed since.

This is a team record, not an automation. Recording a decision runs nothing. Morse does not change your agent, redeploy it or roll anything back. And only a person confirms a decision.

What you see

Follow-ups on Home

In Home’s collapsed Follow-ups and portfolio detail section, the Follow-ups panel lists your open findings, overdue first. Each row shows the finding, the next step, where it stands, the owner and the revisit date.

• Open and Closed switch between current and finished findings. The Open count is beside the label.
• Search matches the agent name or the finding title.
• Awaiting your confirmation appears only when something is waiting for you. It stays hidden when the count is zero.
• The row’s link reads Decide when the revisit date has passed, Choose when no next step has been recorded yet, and Open otherwise.
• When a finding has an earlier attempt on the same agent, the row says so.
• When a measure other than the one named also got worse, the row adds it, for example Also worse: Error rate +2.7 pts. A measure the decision does not track reads Also worse, not tracked. It never changes the decision’s own result.
• A finding whose next step was Roll back and whose change was rolled back reads Rolled back with the date, for example Rolled back Oct 24, instead of a pending step and revisit date.

With no findings yet, the panel reads No follow-ups yet and links to your agents.

The Finding Sheet

Open a finding to see its sheet. It reads top to bottom as issue → decision → owner and date → result; everything else is folded away until you open it.

1. The issue. The finding’s title, for its agent, and any suggestion Morse has for it.
2. Decision. The next step and its why, or the form to record one. The panel’s caption names the owner and date — for example “Watch, confirmed by Dana Lee on Oct 28” — and says when it is overdue. The conditions it waits on since you decided are listed here too.
3. Result, at the bottom of the Decision panel: the measured result, or No result recorded yet., and a prompt to link the change it measures.

Three collapsed groups follow. Each starts closed and opens only when you open it:

• Result details — each measure on its own (with any other measure that got worse named under it, Also worse), where the evidence came from — the values pinned when the finding opened, labelled as observed, not a result — and What Morse is assuming.
• Waiting on and linked work — what the decision waits on, linked changes and reviews. A condition that reads Condition met says what kind it is: “Linked-work event (a pull request merged or an issue closed), not a measured result. It doesn’t show the change worked.”, or “Measured result: a result became final. Read what it shows; met does not mean improved.”
• History — what was tried before, earlier and later findings on the same agent, the timeline (committed events only, in order) and replies from your team.

The footer has Close without a next step and Record decision, with “Records the team’s plan. Nothing is executed.”

History on the agent page

Every agent page has a History section that lists that agent’s findings. Filter by window (all time, 30, 90 or 365 days), by open or closed, and by next step. Changes linked to a finding are listed inside its row. A change that was rolled back shows as rolled back with a date, on the same change.

Full history is kept on every plan.

Below History, Unexplained changes lists detected changes nobody has explained. Choose Add why on one to open a new finding for it. The panel is hidden when there are none.

The five next steps

Every decision picks one next step.

Each form states it plainly: Records the plan. Morse does not roll anything back. The step is your team’s intent. Morse does not do it for you.

You can add a Why (up to 2,000 characters) and pick an Owner: you, a teammate or Unassigned. If the owner later leaves the team, the finding shows Former member instead of a name.

Revisit dates

Morse fills in the default revisit date from the table and tells you it is the default. You can change the date, or clear it for no reminder. The date you set wins.

A revisit date is a reminder to look again. It is not a forecast of when a result will arrive.

Replacing a decision

Recording a new next step replaces the current plan. The earlier one stays in the timeline as replaced. If a teammate changed the plan before you saved, your choice is not saved. Morse shows what changed and keeps your text, and you record yours again if it still applies.

Close without a next step closes the finding and stops its reminders. It is a housekeeping action, not a finding that the problem went away. If the same subject needs attention later, Morse opens a new finding and links it to the earlier one.

Results per measure

A finding that is tied to a change shows one result for each measure the change engine compares: cost per run, typical response time (p50), slow-end response time (p95), error rate and success rate. They are never combined into one score. See Change Verdicts for how each is computed.

A measure counts as worse as soon as its comparison reaches Worsened, before the window closes. Morse names every such measure, tracked by the decision or not, in the Also worse line on Home, the sheet, History and the weekly brief, and it keeps the agent off Healthy (see Agent health).

Final results come from a snapshot taken when the change engine finished the comparison, with the engine version shown. If a result is missing, the sheet says No result recorded since a date. That is not the same as nothing having happened.

A result is not proof of cause

A result compares runs before and after. It does not show that the change caused it, and it does not show that your decision caused it. Prompt edits, model updates upstream, traffic shifts and busy weeks can move a measure at the same time. Treat a result as evidence for your next decision. See What a verdict does not say.

Agent health

A change that made a measure worse also shows on the agent itself. While a linked or tracked change has a measure at Worsened inside the verdict window, the agent reads Worth watching, not Healthy, on Home, the Agents list, the agent page and the weekly brief. The reason names the measure and the change, for example Error rate worse after cancel-v6 (+4 pts). It says “after”, not “because”.

On the agent page, the Operating Summary card for that measure (Cost, Quality or Reliability) says the same thing instead of Healthy. An agent with a budget sign-off waiting gets an amber Cost card, for example Over its monthly budget and waiting for sign-off: $68.37 of a $54.70 plan. Red stays for firing alerts, open incidents and breached service targets.

The signal clears when the change is rolled back, or when a newer change on the same agent and environment brings that measure back to Improved. A change that was dismissed, or only detected and never tracked, does not count.

Decision follow-up

Morse tells a decision’s owner when there is something to read. When every tracked measure of a confirmed decision becomes final before its window ends (“The results are in for a decision you own.”), or when the review window ends — the revisit date passes, or a linked change reaches its 28-day horizon still inconclusive (“The review window ended for a decision you own.”) — the owner gets an email and an in-app notification, following their notification preferences.

• It goes to the decision’s owner, or, with no owner, to whoever confirmed it, if they are still a member. With neither, nothing is sent.
• The subject reads [Morse] Decision follow-up: {headline}, where the headline is the result (“Result: …”), “Still unknown: {measure}, {reason}”, or “No result to report”. One line per measure follows, then one Next step — for example “Open the decision and close it, or keep watching” — and Open the decision.
• It repeats the same caveat as the sheet: “This compares before and after. It does not show that the change was the cause.”
• Morse checks hourly. If both happen at once, one message is sent, and the same result is never sent twice.

The in-app notification’s type is Decision follow-up; its title is the headline and its body is the next step. See Notifications.

Replies

Anyone in your organization can reply on a finding, including viewers. A reply holds up to 2,000 characters. You can edit your own replies. You and organization owners and admins can delete a reply, and deleting erases its text everywhere, including the timeline.

In the weekly brief

The Weekly Summary screen always has a Decisions and results panel: each decision a person confirmed in the window, the change it led to, and the result or Still unknown. See Weekly Summary. It also carries two short sections when there is something to say. Neither appears empty.

• Follow-ups due. Confirmed decisions whose revisit date has passed, or whose comparison window ended without a conclusion. Up to five lines, new ones first, then and N more. Each line opens the finding.
• What we still don’t know. Open decisions with a measure that is Not checked yet or Inconclusive, so far, not final.

The brief’s Last week’s changes section lists changes from the last seven days by the date each one shipped, shown on every row. A change that was rolled back reads Rolled back with its date, instead of Confirmed or Not confirmed.

Suggestions and closed or replaced decisions are never listed. A date only makes a decision due. It never confirms anything or changes a result.

How to use it

1. On an agent’s Changes tab, find a change under Unexplained changes and choose Add why.
2. Pick a next step, add a short why, and check the revisit date and owner.
3. Choose Record decision. Nothing is saved until you do, and cancelling leaves no empty finding.
4. When the revisit date comes, open the finding from Home or the weekly brief, read the result, and record the next step: keep it, replace it or close it.
5. Agents with Morse’s MCP server can read these findings first. See get_decisions.

Members and admins record decisions. Viewers can read findings and reply. In demo mode you can open findings but not change them. See Demo mode.

Before you have data

With no findings, Home shows No follow-ups yet and the agent History shows No history yet. If a finding’s evidence is removed under your data retention setting, the sheet says Evidence removed. The decision and its result are kept.

Related

• Change Verdicts — the before and after comparison behind each result.
• Home dashboard — the brief and the Follow-ups panel.
• Agent detail — History and Unexplained changes, on the Changes tab.
• MCP — get_decisions for your own coding agents.