Exoplanet Transit Detector

Light-curve dip detection: baseline → candidate-transit → confirmed as periodic dimming clears depth and periodicity thresholds. Survey-pipeline triage, proven on-chain.

Category	Astrophysics
Template ID	exoplanet-transit-detector
Definition	exoplanet_transit_detector v1.0
States	4 (initial: baseline; terminal: archived)
Transitions	4
Operators composed	APX1, APX2, KO42
Audit clock	on · tick rate 1

What it's for

• Transit-survey triage
• Citizen-science verification
• Followup scheduling

States

State	Role
baseline	initial
candidate	intermediate
confirmed	intermediate
archived	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
baseline	candidate	APX1	input.flux_dip_pct > input.detection_dip_pct	required	—
candidate	confirmed	APX2	input.transit_count >= input.min_transits && input.period_snr > input.snr_threshold	required	—
candidate	baseline	APX1	input.false_positive == true	required	—
confirmed	archived	KO42	input.catalogued == true	required	—

Operators it composes

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

• APX1
• APX2
• 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/exoplanet-transit-detector

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

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.