ZeqTriage

911 dispatch, triage, ambulance, disaster, SAR.

• Protocol ID — zeq-triage
• Category — Emergency
• Endpoint — POST /api/emergency/triage
• Auth — api-key
• Rate limit — 30/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Mass casualty triage using START/JumpSTART with HulyaPulse scoring. Automated color classification (black/red/yellow/green) with Zeqond timestamps per assessment.

Signature

Request

POST /api/emergency/triage

Param	Type	Required	Default	Description
patients	array	✓	—	[{ respiration, pulse, mentalStatus, canWalk }]
protocol	string		"START"	'START', 'JumpSTART', 'SALT', 'SMART'.

Response

{ triageResults: [{ patientId, color, priority, zeqond }], summary }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "patients": [],
  "protocol": "START"
}' \
  "https://api.zeq.dev/api/emergency/triage"

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/emergency/triage in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqTriage alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqTriage 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.