ZeqDigitalForensics

Evidence chain, audio/video authenticity, HF suite.

• Protocol ID — zeq-digital-forensics
• Category — Forensics
• Endpoint — POST /api/forensics/digital
• Auth — api-key
• Rate limit — 10/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Digital forensics evidence acquisition. Disk imaging with Zeqond hash chains, file carving, timeline reconstruction, chain-of-custody logging.

Signature

Request

POST /api/forensics/digital

Param	Type	Required	Default	Description
evidenceSource	object	✓	—	{ type: 'disk'
analysis	string		"timeline"	'acquisition', 'carving', 'timeline', 'keyword'.

Response

{ artifacts, timeline, hashChain, chainOfCustody, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "evidenceSource": {},
  "analysis": "timeline"
}' \
  "https://api.zeq.dev/api/forensics/digital"

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