Read-only Vercel deployment investigation brief. It reads one deployment, bounded deployment events, and assigned aliases through recued-core.vercel, then asks the AI summarizer for failure signals, readiness state, routing impact, and next actions. It never cancels, promotes, rolls back, deletes deployments, reads deployment file contents, mutates project settings, or calls arbitrary Vercel APIs.

How it works 14 steps

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

Process (14 steps)

■ deployment_id_or_url_trim trim

Trim whitespace from setting deployment id or url

■ team_id_trim trim

Trim whitespace from setting team id

■ team_slug_trim trim

Trim whitespace from setting team slug

■ deployment ?

■ events_raw ?

■ aliases_raw ?

■ events default

Apply default

■ aliases default

Apply default

■ event_count count

Count items in events

■ alias_count count

Count items in aliases

■ summarize ?

■ event_table to_table

Format results as a data table

■ alias_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 7 configurable

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

focus setting = Summarize deployment state, build or runtime failure indicators, aliases affected, checks state, error codes/messages, and recommended next actions.

vercel setting =

team id setting =

team slug setting =

max length setting = 1000

event limit setting = 100

deployment id or url setting =