Declare both sides
Name the source event, expected target input, declared authentication boundary, method, route, format, target limits and intended outcome. Avoid describing a connection only in prose.
Guide 01 // Agent Preflight
CHECK THE CONNECTION BEFORE THE AGENT ACTS.
This Agent Preflight check separates whether two systems fit from whether either system has permission to do work. It is not webhook delivery or route operation.
Check the contract
Compare required fields, types, meaning and limits through a read-only compatibility check that does not contact live endpoints or use credentials. A mismatch should return a corrective explanation before any downstream action is considered.
Keep authority separate
A compatible draft is not approval to run work. Review scope, destination and data boundary separately; compatibility is not authority.
What this prevents
It catches format drift, missing inputs and unsafe assumptions while the change is still cheap to correct. It does not make a connection safe by itself, and it does not grant an agent secrets, deployment access or execution authority.
Diagnostic notes to record
For each proposed connection, record the source event name, target input schema, required fields, allowed types, size or rate limits, and the boundary where authentication would begin. A useful finding names the exact field or limit that differs and points to one bounded correction. Keep payload examples synthetic or redacted; never paste credentials or sensitive production data into a preflight request.
Re-run the check after the draft changes. A passing result means the declared shapes are compatible at review time. It does not test endpoint availability, promise delivery, or authorise a send.