Gear gstd API Map Goal Keep design work API-first: start from , then drop to or only when you need to confirm limits, gas shape, or low-level behavior. Inputs - — execution model and block lifecycle - — message flow and reply semantics - — gas reservations and waitlist - — full API surface and syscall mapping Route Here When - a spec or architecture note needs to know whether a Gear program can send, await replies, self-schedule, reserve gas, or create child programs - a builder is choosing between typed payloads, raw bytes, staged push-plus-commit, or input-forwarding APIs - a design depends…