ZeqTrial — Clinical Data Integrity

Biosignals, pharmacokinetics, diagnostics, genomics — all 1.287 Hz pulse-coherent.

• Protocol ID — zeq-trial
• Category — Healthcare
• Endpoint — POST /api/health/trial/record
• Auth — api-key
• Rate limit — 60/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Clinical trial data integrity with ZeqProof-chained observations. Every data point carries a cryptographic proof binding it to the exact Zeqond it was recorded — tamper-evident by design.

Signature

Request

POST /api/health/trial/record

Param	Type	Required	Default	Description
trialId	string	✓	—	Clinical trial identifier.
observation	object	✓	—	Observation data payload.
subjectId	string	✓	—	Subject identifier (hashed).

Response

{ recordId, zeqProof, zeqond, chainPosition, previousProof, integrity }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "trialId": "<value>",
  "observation": {},
  "subjectId": "<value>"
}' \
  "https://api.zeq.dev/api/health/trial/record"

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/health/trial/record in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqTrial — Clinical Data Integrity alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqTrial — Clinical Data Integrity 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.