ZeqTrajectory — Multi-Body Optimization

Orbital mechanics, trajectory, radiation, life support.

• Protocol ID — zeq-trajectory
• Category — Space
• Endpoint — POST /api/space/trajectory/optimize
• Auth — api-key
• Rate limit — 10/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Multi-body trajectory optimization using RK4 solver with gravitational operator coupling. Compute optimal transfer orbits between planets.

Signature

Request

POST /api/space/trajectory/optimize

Param	Type	Required	Default	Description
origin	string	✓	—	Departure body.
destination	string	✓	—	Target body.
departureWindow	number		365	Search window in days. Default: 365.
payloadKg	number		1000	Payload mass.

Response

{ optimalLaunchDate, totalDeltaV, flightTimeDays, trajectory: [{ t, x, y, z }], fuelMassKg }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "origin": "<value>",
  "destination": "<value>",
  "departureWindow": 365,
  "payloadKg": 1000
}' \
  "https://api.zeq.dev/api/space/trajectory/optimize"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/space/trajectory/optimize in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqTrajectory — Multi-Body Optimization alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqTrajectory — Multi-Body Optimization as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.