Neon branch readiness brief
Read-only Neon branch readiness brief for one project branch. It reads project, branch, endpoint, database, role, and operation context through recued-core.neon, then asks the AI summarizer for readiness risks and next steps. It never creates branches or databases, starts or suspends compute, reveals passwords, retrieves connection URIs, deletes or restores resources, mutates auth, or calls arbitrary Neon APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (24 steps)
normalized_project_id
trim
Trim whitespace from setting project id
normalized_branch_id
trim
Trim whitespace from setting branch id
project
?
branch
?
endpoints_raw
?
databases_raw
?
roles_raw
?
operations_raw
?
endpoints
default
Apply default
databases
default
Apply default
roles
default
Apply default
operations
default
Apply default
endpoint_count
count
Count items in endpoints
database_count
count
Count items in databases
role_count
count
Count items in roles
operation_count
count
Count items in operations
summarize
?
endpoint_rows
slice
Take a subset of
database_rows
slice
Take a subset of
operation_rows
slice
Take a subset of
endpoint_table
to_table
Format results as a data table
database_table
to_table
Format results as a data table
operation_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
neon
setting
=
focus
setting
=
Summarize this Neon branch's current state, compute endpoint health, databases, roles, recent operations, readiness risks, and concrete next steps. Do not invent facts outside the Neon data.
branch id
setting
=
row limit
setting
=
20
max length
setting
=
900
project id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.