Re-entry Corridor Guard

Holds a capsule's entry angle inside the survivable corridor: nominal → shallow/steep warnings → abort-to-orbit if the flight-path angle leaves bounds.

Category	Aerospace
Template ID	reentry-corridor-guard
Definition	reentry_corridor_guard v1.0
States	4 (initial: nominal; terminal: abort, landed)
Transitions	4
Operators composed	ORBIT_VELOCITY, ORBIT_ENERGY, KO42
Audit clock	on · tick rate 1

What it's for

• Crew capsule re-entry
• Sample-return safety
• Hypersonic test gating

States

State	Role
nominal	initial
off_nominal	intermediate
abort	terminal
landed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
nominal	off_nominal	ORBIT_VELOCITY	input.fpa_deg < input.fpa_min_deg || input.fpa_deg > input.fpa_max_deg	required	—
off_nominal	nominal	ORBIT_VELOCITY	input.fpa_deg >= input.fpa_min_deg && input.fpa_deg <= input.fpa_max_deg	required	—
off_nominal	abort	ORBIT_ENERGY	input.recoverable == false	required	—
nominal	landed	KO42	input.touchdown == true	required	—

Operators it composes

Each transition fires a registry operator through the master equation (compute → prove → verify). This template composes:

• ORBIT_VELOCITY
• ORBIT_ENERGY
• KO42

Browse the operators at /operators/; the building blocks a transition calls are the framework's protocols. KO42 is the always-on substrate operator; physics operators carry proof_required: true, so each fire runs the full compute → prove → verify path and lands a verifiable proof digest on your entangled state.

Deploy it

Inspect the full definition, then deploy it onto your state machine. Every fire is Zeqond-stamped onto your entangled state.

# 1. Inspect — the full definition (states, transitions, operators) as served
curl -sS https://zeqsdk.com/api/contracts/templates/reentry-corridor-guard

# 2. Deploy onto your machine (auth: session; body carries your machine slug)
curl -sS -X POST https://zeqsdk.com/api/contracts/templates/reentry-corridor-guard/deploy \
  -H "Content-Type: application/json" \
  -b "<your session cookie>" \
  -d '{"slug":"<your-machine>"}'
# → 201 { "ok": true, "contract": { "id": "…", "currentState": "nominal", … },
#         "template_id": "reentry-corridor-guard" }

The deploy path runs the same two-stage validation as the canonical create route (ContractDefinitionSchema.parse + validateContractDefinition against the live registry), writes the creation row onto your entangled state, and schedules the first fire. From there, drive transitions with POST /api/chain/<your-machine>/contracts/<id>/transition or let any triggers fire them autonomously.

Next

• Contract IDE — author, preview, and deploy contracts (this template is in the Templates tab).
• State Contracts — the full contract model: conditions, triggers, pre/post actions, lifecycle.
• Templates Library — every ready-to-deploy contract, grouped by category.
• Protocols — the named building blocks a transition composes.