Skip to main content
A recommendation is a concrete, AI-generated fix for a recurring pattern. Recommendations close the loop: Causeloop not only tells you what is broken and why, it tells you what to do — and then tracks whether the fix held. Recommendations are generated automatically when a pattern reaches sufficient confidence, and are ranked by the number of loops they are expected to prevent.

​
The Recommendations list

Navigate to Recommendations in the left sidebar to open the ranked list.

​
Summary header

Three KPI tiles appear at the top:
TileDescription
OpenRecommendations in pending or in_progress status
Loops preventableSum of expected_loops_prevented across open recommendations
Exposure addressedEstimated dollar value of loops preventable (at a default rate per loop incident)

​
Ranked rows

Each row shows:
  • Rank — the AI’s priority ordering (rank 1 = highest priority)
  • Title — the recommended action
  • Type chip — code_fix, config, process, or monitoring
  • Impact pill — high, medium, or quick_win
  • Effort chip — EFFORT LOW, EFFORT MED, or EFFORT HIGH
  • Status pill — pending, in progress, implemented, or dismissed
  • Expected loops prevented — the AI’s estimate of how many future loops this fix prevents

​
Filtering and sorting

Use the filter bar to narrow by:
ParameterOptions
typecode_fix, config_change, process, monitoring
statuspending, in_progress, implemented, dismissed (comma-separate for OR)
impacthigh, medium, quick_win
sortrank (default), -rank, -created_at, -expected_loops_prevented, -updated_at

​
Recommendation detail

Click any row to open the recommendation detail page at /recommendations/{id}. The header shows:
  • Eyebrow — RANK #{n} · {type} · CREATED {date}
  • Title — the full recommendation title
  • Impact pill and status pill
  • Pattern chip — the source pattern this recommendation addresses
Top-bar actions: Push to tracker, Mark implemented.

​
Overview (left column)

The Overview card contains a plain-language summary of what the fix does and why it prevents the loop from recurring.

​
Implementation plan (left column)

Below the overview, the Implementation plan card lists the AI-generated steps needed to apply the fix. Each step has a title, a description, and a completion checkbox. As you complete steps, check them off — the progress is saved per step.

​
Source pattern (right rail)

The Source pattern rail card shows the pattern this recommendation was generated from: name, pattern ID, issue count, and risk score. Click Open pattern → to navigate to the pattern detail page.

​
Addresses N issues (right rail)

This card lists the specific issues that this recommendation, once applied, will address. Each row shows the external ID and a risk score.

​
On implementation (right rail)

A note card explains what happens after you mark this recommendation implemented:
The pattern enters its 90-day hold window. If no recurrence, status flips to Held and a regulator-ready attestation is generated.

​
Acting on a recommendation

​
Pushing to your issue tracker

Before starting implementation, push the recommendation to your team’s issue tracker to create a trackable ticket.
1

Open the recommendation detail

Navigate to the recommendation you want to act on.
2

Click Push to tracker

A dialog appears with fields for the target tracker and project key.
3

Choose your tracker and project

Supported trackers: Jira, Linear, GitHub, ServiceNow. Enter the project key (e.g. ENG).
4

Confirm

A ticket is created asynchronously. The recommendation detail page updates immediately with the external ticket link.
The push is handled by POST /v1/recommendations/{id}/push. The external_ticket field on the recommendation is populated with the tracker name, ticket ID, external URL, and the timestamp and user who initiated the push.

​
Marking implemented

Once you have applied the fix, mark the recommendation as implemented.
1

Click Mark implemented

The button is in the top bar of the recommendation detail page.
2

Confirm

The recommendation status changes to implemented. The linked pattern enters the 90-day hold window immediately.
You can also use PATCH /v1/recommendations/{id} with status: "implemented". The analyst role is required.

​
Attesting the fix held

After 90 days without recurrence, the pattern’s attestation_ready flag is set to true. At that point you can formally attest that the fix held.
1

Navigate to the recommendation detail

The detail page shows an attestation prompt when attestation_ready is true.
2

Click Attest

Enter attestation notes and optional evidence URLs (links to PRs, run logs, or audit records).
3

Submit

An attestation record is created with attested_by, attested_at, notes, and evidence_urls. This record is available for audit and compliance exports.
The attestation is stored via POST /v1/recommendations/{id}/attest. Retrieve the attestation record at any time with GET /v1/recommendations/{id}/attestation.
Attesting a dismissed recommendation requires you to re-open it first (move status back to pending or in_progress).

​
Dismissing a recommendation

If a recommendation is not applicable to your context, dismiss it with a reason: 
PATCH /v1/recommendations/{id}
{
  "status": "dismissed",
  "dismissal_reason": "Third-party service handles this — not in scope."
}
dismissal_reason is required when setting status to dismissed.

​
Status transitions

FromAllowed transitions
pendingin_progress, dismissed
in_progressimplemented, pending, dismissed
implemented— (terminal; use attestation flow)
dismissedpending

​
API reference

EndpointDescription
GET /v1/recommendationsList recommendations with filters
GET /v1/recommendations/{id}Get recommendation detail
PATCH /v1/recommendations/{id}Update status, impact, or dismiss
POST /v1/recommendations/{id}/pushPush to an issue tracker
GET /v1/recommendations/{id}/planGet the structured implementation plan
POST /v1/recommendations/{id}/attestAttest that the fix held
GET /v1/recommendations/{id}/attestationRetrieve the attestation record
GET /v1/recommendations/statsAggregate stats across the workspace

Patterns

See the pattern a recommendation is addressing.

Predictions

Understand the recurrence risk driving each recommendation.

Issues

See the issues a recommendation addresses.

Reports

Include recommendation coverage in an executive report.