Read-only review brief for one Statuspage incident. It reads the page, incident, and component catalog through recued-core.statuspage, then asks the AI summarizer for customer impact, current status, affected components, update history, and next steps. It never creates or updates incidents, edits components, sends notifications, publishes postmortems, deletes records, or calls arbitrary Statuspage APIs.

How it works 13 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (13 steps)

■ page_id trim

Trim whitespace from setting page id

■ incident_id trim

Trim whitespace from setting incident id

■ page ?

■ incident ?

■ components_raw ?

■ components default

Apply default

■ updates default

Apply default

■ component_count count

Count items in components

■ update_count count

Count items in updates

■ summarize ?

■ update_rows slice

Take a subset of

■ update_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the Statuspage incident for customer impact, current status, affected components, update history, open questions, and concrete next steps. Do not invent facts outside the Statuspage data.

page id setting =

row limit setting = 10

max length setting = 900

statuspage setting =

incident id setting =