Ballistic Intercept Window

NM21 (F=G·m₁m₂/r²) + NM28 (L=r×p): tracking → window_open as closing range crosses the intercept envelope, → committed when intercept confidence clears threshold. A trajectory-gated decision machine — every state change is proof-stamped on the entangled state.

Category	Aerospace & Defense
Template ID	ballistic-intercept-window
Definition	ballistic_intercept_window v1.0
States	4 (initial: tracking; terminal: logged)
Transitions	4
Operators composed	NM21, NM28, KO42
Audit clock	on · tick rate 1

What it's for

• Intercept decision support
• Range-safety abort gating
• Constellation conjunction screening

States

State	Role
tracking	initial
window_open	intermediate
committed	intermediate
logged	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
tracking	window_open	NM21	input.closing_range_km < input.intercept_range_km	required	—
window_open	tracking	NM28	input.closing_range_km >= input.intercept_range_km	required	—
window_open	committed	NM21	input.intercept_confidence > input.commit_threshold	required	—
committed	logged	KO42	input.engagement_logged == true	no	—

Operators it composes

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

• NM21
• NM28
• 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/ballistic-intercept-window

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

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.